[-] SmilinArtist@lemm.ee 1 points 1 year ago

ok I wil keep in mind to leave the vlan in the same network

[-] SmilinArtist@lemm.ee 2 points 1 year ago

yeah I should draw it out first. Right now traffic is routed trough a pihole on a raspberry

I think I will keep this route

[-] SmilinArtist@lemm.ee 1 points 1 year ago

Oh opnsense has this pihole filtering in it it self I did not know that I have to check that out

[-] SmilinArtist@lemm.ee 1 points 1 year ago

thank you I will have a look.

26
submitted 1 year ago* (last edited 11 months ago) by SmilinArtist@lemm.ee to c/selfhosted@lemmy.world

Hello everyone,

I hope you're all doing well. I'm reaching out for some guidance on a network project I've been working on.

Currently, my setup includes:

  • OPNsense Firewall: This is running smoothly and is the primary gateway for my network.
  • Proxmox Server: I'm in the process of integrating this. It has a single Ethernet port for network connectivity.

My primary goal is to deploy a Pi-hole instance on the Proxmox server. I'm still weighing whether to go with a Docker container or a standalone VM for this.

Here's the crux: My existing network devices operate in the 192.168.0.1xx IP range. I'd like the Pi-hole to be on a different subnet, specifically 192.168.33.xxx. This move is mainly for organization and segmentation purposes.

Considering the single Ethernet port on the Proxmox server and my intended setup, is this feasible? Moreover, are there specific challenges or configurations I should be aware of?

Any insights, advice, or shared experiences would be invaluable.

Thank you for your collective wisdom and time!

Uptate

so for all you people looking I managed to get it to work with this guide

Firewall Rules:

Allow Main LAN to Access the New Subnet:

Log into the OPNsense web interface. Go to Firewall > Rules > [LAN]. Click on the + button to add a new rule. Set the following:

Action: Pass
Interface: LAN
Protocol: Any (or you can specify TCP/UDP if needed)
Source: LAN net
Destination: Single host or alias and input 192.168.33.0/24.

Add a description (e.g., "Allow LAN to Access 192.168.33 Subnet"). Click Save.

Allow New Subnet to Reply (or initiate to the Main LAN):

  • Go to Firewall > Rules > [Your VLAN interface, e.g., VLAN33].
  • Click on the + button to add a new rule.
Set the following:
Action: Pass
Interface: [Your VLAN interface]
Protocol: Any (or you can specify TCP/UDP if needed)
Source: 192.168.33.0/24
Destination: LAN net
  • Add a description (e.g., "Allow 192.168.33 Subnet to Access LAN").
  • Click Save.

Apply Changes:

After creating the rules, click on Apply Changes to ensure the rules take effect.

[-] SmilinArtist@lemm.ee 1 points 1 year ago

thanks for the info. I would say that is the most likely explanation

[-] SmilinArtist@lemm.ee 1 points 1 year ago

thanks. let's see.

this is quite the noob questions. I checked the faq and I saw that there is a 100kb limit. I am just unsure what I should do

7
submitted 1 year ago* (last edited 1 year ago) by SmilinArtist@lemm.ee to c/support@lemm.ee

hey guys,

I am new here and wanted to add a avatar. but I keep getting the message

upload too large

i used png and jpg both with 350x350 and 100x100 resolution which were smaller than 100 kb. all four options failed

can somebody please enlighten me how I can upload an awesome picture of mine

the endpoint response of https://lemm.ee/pictrs/image returns response code 413 with


413 Request Entity Too Large

<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>


as far as I can tell is maybe the some headers are missing from my side I do not know what the backend does.

SmilinArtist

joined 1 year ago