BrianG Posted October 14, 2018 Share Posted October 14, 2018 Was alerted to a lack of network/internet access by unRAID. It seemed to have have happened soon after I installed pfSense as a VM but I didn't notice it for a few days. From the terminal I cannot ping the unraid hosted LAN ip's or WAN (also locally hosted). Everything is working as I would like it to except unRAID cannot access the web to download any OS or docker/plugin updates. My network layout is as follows: Cable Modem --> pfSense VM on unRAID(on passed through 4 port NIC) (Static 192.168.1.1) --> unmanaged switch --> unRAID using motherboard NIC port (Static 192.168.1.2) The rest of my network computers also sit behind this unmanaged switch. Because everything is sitting behind this switch, LAN traffic shouldn't be passing through the pfSense, right? What gives? The communication between 192.168.1.2 (unraid) and 192.168.1.1 (pfsense gateway) should bet taking place between NIC's through the switch. Thanks for your help and consideration. Here's my network config for your convenience: root@RackServer:~# ifconfig br0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.2 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::74c7:f1ff:feb4:9aab prefixlen 64 scopeid 0x20<link> inet6 2601:1c1:8101:b03d:329c:23ff:fe8c:a0 prefixlen 64 scopeid 0x0<global> ether 30:9c:23:8c:00:a0 txqueuelen 1000 (Ethernet) RX packets 45091 bytes 11679872 (11.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11747 bytes 4167642 (3.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@RackServer:~# ifconfig eth0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 30:9c:23:8c:00:a0 txqueuelen 1000 (Ethernet) RX packets 45289 bytes 12529068 (11.9 MiB) RX errors 0 dropped 7 overruns 0 frame 0 TX packets 13090 bytes 4314753 (4.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xdf800000-df820000 No broadcast address? Shouldn't that be 192.168.1.255? Why is it not set properly? rackserver-diagnostics-20181014-1011.zip Link to comment
BrianG Posted October 18, 2018 Author Share Posted October 18, 2018 Fixed by enabling DHCP. Weird, but I give up. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.