No route to host
-
2.0-RC1 (i386) built on Mon Mar 7 12:03:17 EST 2011
2 LAN:
- LAN: 192.168.1.0/24
- VOIP: 192.168.5.0/24
From time to time, pfSense gateway is no longer able to find route to VOIP network (192.168.5.0/24). It still can reach itself (192.168.5.1) I can see the route into the routing table. No problems with LAN. Other devices on VOIP lan can still talk to gateway. It continues to deliver DHCP leases, etc. Yesterday, I had to restart the gateway to correct the problem. Last time it occurred, the problem solved by itself few minutes after. Any idea what it could be?
Charles.
-
Look at the output of "ifconfig -a" and "netstat -rn" at a time when it works and when it doesn't, see if there are any changes.
-
No, I don't see any noticeable difference.
ifconfig -a gives identical results in both cases.
The only difference I see in routing tables is one DNS server from ISP that changed, but I don't think it's related to my problem. Here are the results (I just masked my WAN address)xl0 is my WAN interface (3COM PCI 100 Mbits/sec)
em0 is my LAN interface (HP, on board, 1000 Mbits/sec)
sk0 is my second LAN interface (VOIP) (DLink (Marvell) PCI 1000 Mbits/sec).[2.0-RC1][admin@gateway.fmjs]/root(2): ifconfig -a xl0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=80009 <rxcsum,vlan_mtu,linkstate>ether 00:10:5a:a9:81:37 inet6 fe80::210:5aff:fea9:8137%xl0 prefixlen 64 scopeid 0x1 inet 74.58.###.### netmask 0xffffff00 broadcast 255.255.255.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active sk0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=8000b <rxcsum,txcsum,vlan_mtu,linkstate>ether 1c:bd:b9:7f:ab:8e inet6 fe80::1ebd:b9ff:fe7f:ab8e%sk0 prefixlen 64 scopeid 0x2 inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active fwe0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500 options=8 <vlan_mtu>ether 12:cf:fd:11:be:10 ch 1 dma -1 fwip0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500 lladdr 10.cf.fd.0.0.11.be.10.a.2.ff.fe.0.0.0.0 em0: flags=108843 <up,broadcast,running,simplex,multicast,ipfw_filter>metric 0 mtu 1500 options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:0d:9d:ff:d5:2f inet6 fe80::20d:9dff:feff:d52f%em0 prefixlen 64 scopeid 0x5 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active plip0: flags=8810 <pointopoint,simplex,multicast>metric 0 mtu 1500 lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384 options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 nd6 options=3 <performnud,accept_rtadv>pflog0: flags=100 <promisc>metric 0 mtu 33200 pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 enc0: flags=0<> metric 0 mtu 1536 em0_vlan30: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=3 <rxcsum,txcsum>ether 00:0d:9d:ff:d5:2f inet6 fe80::210:5aff:fea9:8137%em0_vlan30 prefixlen 64 scopeid 0xb nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active vlan: 30 parent interface: em0 sk0_vlan20: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 1c:bd:b9:7f:ab:8e inet6 fe80::210:5aff:fea9:8137%sk0_vlan20 prefixlen 64 scopeid 0xc nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active vlan: 20 parent interface: sk0 ovpns1: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500 options=80000 <linkstate>inet6 fe80::210:5aff:fea9:8137%ovpns1 prefixlen 64 scopeid 0xd inet 10.8.0.1 --> 10.8.0.2 netmask 0xffffffff nd6 options=3 <performnud,accept_rtadv>Opened by PID 6510 ipfw0: flags=8801 <up,simplex,multicast>metric 0 mtu 65536 [2.0-RC1][admin@gateway.fmjs]/root(6): netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 74.58.###.1 UGS 0 12005734 xl0 10.8.0.0/24 10.8.0.2 UGS 0 388 ovpns1 10.8.0.1 link#13 UHS 0 0 lo0 10.8.0.2 link#13 UH 0 0 ovpns1 24.200.241.37 00:10:5a:a9:81:37 UHS 0 86 xl0 24.200.243.189 00:10:5a:a9:81:37 UHS 0 193 xl0 24.201.245.77 00:10:5a:a9:81:37 UHS 0 225 xl0 74.58.###.0/24 link#1 U 0 192481 xl0 74.58.###.### link#1 UHS 0 556 lo0 127.0.0.1 link#7 UH 0 203653 lo0 192.168.1.0/24 link#5 U 0 10159419 em0 192.168.1.1 link#5 UHS 0 572897 lo0 192.168.5.0/24 link#2 U 0 177672 sk0 192.168.5.1 link#2 UHS 0 0 lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%xl0/64 link#1 U xl0 fe80::210:5aff:fea9:8137%xl0 link#1 UHS lo0 fe80::%sk0/64 link#2 U sk0 fe80::1ebd:b9ff:fe7f:ab8e%sk0 link#2 UHS lo0 fe80::%em0/64 link#5 U em0 fe80::20d:9dff:feff:d52f%em0 link#5 UHS lo0 fe80::%lo0/64 link#7 U lo0 fe80::1%lo0 link#7 UHS lo0 fe80::%em0_vlan30/64 link#11 U em0_vlan fe80::210:5aff:fea9:8137%em0_vlan30 link#11 UHS lo0 fe80::%sk0_vlan20/64 link#12 U sk0_vlan fe80::210:5aff:fea9:8137%sk0_vlan20 link#12 UHS lo0 fe80::210:5aff:fea9:8137%ovpns1 link#13 UHS lo0 ff01:1::/32 fe80::210:5aff:fea9:8137%xl0 U xl0 ff01:2::/32 fe80::1ebd:b9ff:fe7f:ab8e%sk0 U sk0 ff01:5::/32 fe80::20d:9dff:feff:d52f%em0 U em0 ff01:7::/32 ::1 U lo0 ff01:b::/32 fe80::210:5aff:fea9:8137%em0_vlan30 U em0_vlan ff01:c::/32 fe80::210:5aff:fea9:8137%sk0_vlan20 U sk0_vlan ff01:d::/32 fe80::210:5aff:fea9:8137%ovpns1 U ovpns1 ff02::%xl0/32 fe80::210:5aff:fea9:8137%xl0 U xl0 ff02::%sk0/32 fe80::1ebd:b9ff:fe7f:ab8e%sk0 U sk0 ff02::%em0/32 fe80::20d:9dff:feff:d52f%em0 U em0 ff02::%lo0/32 ::1 U lo0 ff02::%em0_vlan30/32 fe80::210:5aff:fea9:8137%em0_vlan30 U em0_vlan ff02::%sk0_vlan20/32 fe80::210:5aff:fea9:8137%sk0_vlan20 U sk0_vlan ff02::%ovpns1/32 fe80::210:5aff:fea9:8137%ovpns1 U ovpns1</up,simplex,multicast></performnud,accept_rtadv></linkstate></up,pointopoint,running,multicast></full-duplex></performnud,accept_rtadv></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></promisc></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></pointopoint,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast,ipfw_filter></broadcast,simplex,multicast></vlan_mtu></broadcast,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,linkstate></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,vlan_mtu,linkstate></up,broadcast,running,simplex,multicast>Could it be a hardware or a driver problem?
Charles
-
I'm not too familiar with the sk(4) devices from Marvell, but some others on the forums have had issues with them. Do you have another network card you could try in place of that NIC?
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.