Interfaces randomly stop working
-
Because of max Text-length, here the 2nd part of post:
It looks like if only em0 and em1 is not working anymore. Both are exact same card (Intel Pro 1000). LAN which doesn't have any problem is an onboard chip (Realtek?).
cu Floh
-
Could be that your WAN is failing an and your modem is handing you an IP in 192.168.1.x and a gateway of 192.168.1.1. If your LAN is still 192.168.1.x I would expect that to blow up quite badly.
Given the messages in the log it does appear that your WAN interface is going up/down.
See if you can get into your CPE and make sure it's LAN subnet is not also 192.168.1.x, even in half-bridge or pass-thru mode devices like that will still conflict if they lose sync.
My cable modem is bad about this if it loses signal from the carrier, it flips to 192.168.100.x until the cable link comes back up.
-
Hi, thank you for your reply.
LAN is of course not 192.168.1.X (would be bad in my case) but 192.168.0.X.
What do you mean by CPE?
cu Floh
-
CPE = Customer Premises Equipment, meaning your DSL or Cable modem. Whatever the first device is to which the wire from your ISP connects.
-
I can access my modem by using 192.168.100.1 so its subet is 192.168.100.0.
Could it be a problem if both modems are using same ip-Address 192.168.100.1 (but they're physically separated!)?
cu Floh
-
Could it be a problem if both modems are using same ip-Address 192.168.100.1 (but they're physically separated!)?
Yes, which modem is 192.168.100.1? (Both is not an acceptable answer! Unless you take special care with your configuration each computer on your network needs to have a unique IP address.)
Please provide the output of pfSense shell commands netstat -r -n and ifconfig -a
Your question says that you have a broken configuration but doesn't say how badly it is broken. -
Sorry, but both modem have 192.168.100.1. I don't have access to settings of these modem.
To make more clear I made a picture. Please see attached picture. In pfSense WAN1 and WAN2 are grouped and I use that group as gateway (see 2nd picture).
As you asked I entered the command you wished:
[2.0.1-RELEASE][admin@r2d2.verbavoice.local]/root(1): netstat -r -n Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 178.26.47.254 UGS 0 422 em0 8.8.4.4 11:aa:bb:cc:dd:ee UHS 0 328 em1 8.8.8.8 192.168.1.1 UGHS 0 1091 em1 83.169.184.161 00:aa:bb:cc:dd:ee UHS 0 328 em0 83.169.184.225 00:aa:bb:cc:dd:ee UHS 0 328 em0 127.0.0.1 link#8 UH 0 31 lo0 178.26.40.0/21 link#1 U 0 1103 em0 178.26.41.70 link#1 UHS 0 0 lo0 192.168.0.0/24 link#3 U 0 21839 re0 192.168.0.1 link#3 UHS 0 0 lo0 192.168.1.0/24 link#2 U 0 4 em1 192.168.1.2 link#2 UHS 0 0 lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%em0/64 link#1 U em0 fe80::21b:21ff:febb:3527%em0 link#1 UHS lo0 fe80::%em1/64 link#2 U em1 fe80::21b:21ff:febb:342a%em1 link#2 UHS lo0 fe80::%re0/64 link#3 U re0 fe80::230:67ff:fe2c:1c32%re0 link#3 UHS lo0 fe80::%lo0/64 link#8 U lo0 fe80::1%lo0 link#8 UHS lo0 ff01:1::/32 fe80::21b:21ff:febb:3527%em0 U em0 ff01:2::/32 fe80::21b:21ff:febb:342a%em1 U em1 ff01:3::/32 fe80::230:67ff:fe2c:1c32%re0 U re0 ff01:8::/32 ::1 U lo0 ff02::%em0/32 fe80::21b:21ff:febb:3527%em0 U em0 ff02::%em1/32 fe80::21b:21ff:febb:342a%em1 U em1 ff02::%re0/32 fe80::230:67ff:fe2c:1c32%re0 U re0 ff02::%lo0/32 ::1 U lo0 [2.0.1-RELEASE][admin@r2d2.verbavoice.local]/root(2): ifconfig -a em0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 00:aa:bb:cc:dd:ee inet6 fe80::21b:21ff:febb:3527%em0 prefixlen 64 scopeid 0x1 inet 178.26.41.70 netmask 0xfffff800 broadcast 178.26.47.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active em1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic>ether 11:aa:bb:cc:dd:ee inet6 fe80::21b:21ff:febb:342a%em1 prefixlen 64 scopeid 0x2 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active re0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=389b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic>ether 33:aa:bb:cc:dd:ee inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::230:67ff:fe2c:1c32%re0 prefixlen 64 scopeid 0x3 nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active plip0: flags=8810 <pointopoint,simplex,multicast>metric 0 mtu 1500 pflog0: flags=100 <promisc>metric 0 mtu 33664 pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 enc0: flags=0<> metric 0 mtu 1536 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 0x8 nd6 options=3<performnud,accept_rtadv></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></pointopoint,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic></up,broadcast,running,simplex,multicast>cu Floh
-
OK, NAT will work to hide replicated IP addresses.
Looking back at the syslog extract you posted I see only em1 reported going down then up. There seems to be some intermittent blockage on em0 but of a different nature to that on em1. I would suspect the link down on em1 due to it losing carrier perhaps due to the NAT router restarting its LAN interface. Do the systems upstream of pfSense record any log information? Are the circuits upstream of the modems in good state? I have had my home ADSL service misbehave when the phone service developed a noticeable crackle which was rectified by something the phone company did.
-
Hi,
I'm suspecting that the LAN-cable of the building has poor quality. Now I'm using different WLAN-Router (for NAT) at different place (better Cable-quality).Let see some days then I'll report if it helped.
cu Floh -
Unfortunatelly I have still same problem. This time WAN1 went down and I have to reboot Firewall.
I cannot post log about WAN1 failure because this happened at weekend and when I was in office logs about WAN1 failure was already "flooded away" by dhpc- & arping-logs.
Some idea?
cu Floh
