chrisb28

Solves! The problem caused by assign 2 Nics (eth0 and erh1) an IP-Axress in the same subnet (192.168.1.200 and 192.168.1.201). I removed the IP-Adress of eth1 by set the value of "IPv4 address assignment" to "none" Then it works as expected...

I have a Problem to reach unraid from different Subnet (VLAN). Unraid-Server has 5 NIC eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.200 netmask 255.255.255.0 broadcast 0.0.0.0 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.201 netmask 255.255.255.0 broadcast 0.0.0.0 eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.2.202 netmask 255.255.255.0 broadcast 0.0.0.0 eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.3.203 netmask 255.255.255.0 broadcast 0.0.0.0 eth4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 88:c9:b3:bf:24:d6 txqueuelen 1000 (Ethernet) Sophos Firewall (VM) is running with 2 NIC (eth4 exclusive to WAN, eth0 to LAN) LAN as Network 192.168.1.0/24 (Gateway 192.168.1.1) VLAN3 as Network 192.168.3.0/24 (Gateway 192.168.3.1) with DHCP LAN-to-LAN rule configured Netgear Managed Switch with configured VLAN-Ports to Unraid Docker-Container on eth1 in Subnet 192.168.1.0 VM's on eth0,1,3 in Subnet 192.168.1.0 Client should use VLAN3 in Subnet 192.168.3.0 (IP via DHCP pi.hole (IP 192.168.1.250) configured as primary DNS via DHCP sophos (Gateway-IP) configured as secondary DNS via DHCP Problem: Client from subnet 192.168.3.0 (IP via DHCP) are able to access Internet (WAN Interface) and able to reach all Docker (with static IPs) and VMs in Subnet 192.168.1.0. Only the Unraid-IP (192.168.1.200 are not reachable (ping, trace, http,..). From Subnet 192.168.1.0 everthing works fine. DNS-Lookup on sophos and clients works correct Has anyone an Idea? Sophos Logs show "allowed" from rule "LAN-to-LAN". Is there a configuration in Unraid Network that blocks access from different Network?