Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Servergeek

#1
So I tried that, but still can't ping a device from the serversVLAN to the LAN or from the LAN to the ServersVLAN.

The only thing that sorta worked was making a floating rule allowing traffic in any direction from all the LAN side interfaces. That allowed pinging devices on LAN network from ServersVLAN but not vise-versa.
#2
So basically I am trying to set up router-on-a stick between a few vlans to segment my network. I have 5 vlans, each is tagged and working through OPNSense. However, I cannot get the interfaces to communicate with eachother.

Basically I have 5 vlans:
VLAN 1 - Default, use for management basically
VLAN 2 - Servers VLAN, going to eventually have all my servers on it
VLAN 3 - Devices VLAN, basically all the normal computer systems on my network
VLAN 4 - IOT Vlan, for any other devices
VLAN 5 - WAP Vlan - going to be all my Wireless access points
VLAN 10 - WAN (Of course want to be separated through firewall)

I can probably do the routing with my switch (Procurve 6600-48g) but I would like to be able to set up firewall rules to block specific traffic between some of the VLANs. (Will eventually do that later)

Basically for right now I want them to all be able to communicate with each other, but no matter what I do I can't ping devices on different VLANs, but the VLANs have access to the internet. Do I need to set up rules to allow communication? I've tried a few different things, like passing out and in from the different interfaces but no matter what configuration I tried I can't get it to work.
#3
It could be the way I have it set up, it is fed from a wifi/router combo (I don't have access to configure it)

It's kinda weird because before I had a PFsense box going and had no issues.
#4
So apparently setting it to DNS forwarder worked. I had it set to the Cloudflare DNS servers before but it just wasn't working properly. It is no longer spamming the errors in the log.

How does operating as its own DNS server cause issues?
#5
So currently I'm having an issue where half the time trying to connect to a website results in "Webpage cannot be found" no matter what web browser I use. This happens no matter what setup I use, whether that be in Hyper-V or on Proxmox. For the life of me I cannot figure out what is causing it.

There is no real information in the logs other than spamming:
"unbound[22187]   [22187:3] error: udp connect failed: No route to host (IPV6 Address) Port 53"

And under reporting > health it shows a lot under inblock6 (400m). Not sure if this is an incompatibility with IPv6 or what, because even when I try disabling IPv6 I still get the errors and issues with webpages not being found.

Oddly enough, I have the same issues with PFSense, not sure why.