N4F 10.2.0.2.1814 (these problems were actually first noticed on the original v10 release)
Intel Xeon 3060
TYAN Computer Corporation S5197
(2) gigabit embedded NICs, Intel 82573, IP 192.168.x.x
-LAGG configured for failover
(1) PCI 10/100 NIC, Intel? I forget the chipset, IP 10.x.x.x
-configured to a different IP for a parallel network running surveillance equipment
First I noticed that Transmission was not connecting to trackers at all (could not ping any domain outside my network), then I found that I could not ping the open DNS servers 22.214.171.124 or 126.96.36.199. I defined a 188.8.131.52/24 static route pointing to my router, now I can ping it as well as *most* domains. I am still having issues with Transmission, so I upgraded to v10.2.0.2.1814 hoping to solve the problem.
but I have since also discovered weird things like a DDNS(?) web address is unpingable to the N4F box, but pingable just fine on Windows 7 and Ubuntu 14.04. domain in question is: john.bitsurge.net (184.108.40.206). I can ping the domain and the IP from my desktop/ubuntu box, but neither from N4F.
What seems like it might be weird.... if 0.0.0.0 is the default internal IP, it appears to be pointing to the wrong network?
Code: Select all
IPv4 Destination Gateway Flags Use Mtu Netif Expire 0.0.0.0/1 link#3 U 1302938 1500 fxp0 default 192.168.x.x UGS 4312243 1500 lagg0 220.127.116.11/24 192.168.x.x UGS 24 1500 lagg0 10.x.x.x link#3 UHS 0 16384 lo0 127.0.0.1 link#4 UH 219 16384 lo0 192.168.x.0/24 link#5 U 8767661 1500 lagg0 192.168.x.x link#5 UHS 177 16384 lo0