Internet Occasionally Drops for No Apparent Reason
-
You should be able to connect to it anyway without interrupting the PPPoE on VLAN 101. Just assign igb0 separately and put it in the same subnet as the modem. I do that here to access the HG612 I use with BT.
https://docs.netgate.com/pfsense/en/latest/recipes/modem-access.html -
@stephenw10 Cheers, I will give it a go
-
My WAN interface is:-
However, when I look at "available network ports" there is no igb0, because it is already assigned as :-
No idea why, but I seem to remember that last time I deleted it (thought it wasn't required), everything stopped working!!
It is set up as:-
-
Does it have a lease from the modem? Do you know what IP the modem interface is using? You can just set the interface statically to an IP in the modem subnet.
-
@stephenw10 If I remember right, it was set to default and just worked so I left well alone. If that is the case then the ip would be 192.168.1.1
No idea about the lease though
-
Check Status > Interfaces to see if it has a lease.
If not try setting it to something in the modem subnet, assuming you're not using 192.168.1.X on any other interface already.
-
@stephenw10 Doesn't look like it!
-
Try setting it statically then. Perhaps 192.168.1.10/24. See if the firewall itself can then ping 192.168.1.1.
Still assuming you're not using that subnet anywhere else!
Steve
-
@stephenw10 Assuming I am pinging correctly via "diagnostics / ping" with the hostname set as 192.168.1.1 then it isn't successful
-
That's after setting that interface to something in the same subnet?
Check Diag > Routes to make sure it sees that subnet on igb0.
If so perhaps the modem isnt using that IP any longer...
-
@stephenw10 yep, set to 192.168.1.10 and checked routes and that is ok too.
-
Found it by guessing in the end, the modem appears to be at 192.168.2.1 and can ping from the firewall with interface set as 192.168.2.10
-
Finally in to the modem, will now check the logs!
-
Nice. So you will probably need to add an outbound NAT rule on that interface to translate client traffic to 192.168.2.10 to allow the modem to reply.
That or add 192.168.2.1 as a gateway on that interface which will that create the outbound NAT automatically. If you do that though make sure to set the default IPv4 gateway as WAN_PPPoE rather than automatic. Otherwise the system may failover to the modem as default if PPPoE drops.
With one of those in place you should be able to reach the modem gui from a LAN client.
-
@stephenw10 Sorted NAT and can access the Vigor 130 GUI. However, there isn't an obvious way to see the Syslog when it is bridge mode so will have to look into that. I know it can be done via SysLog utility, just not managed to achieve it yet!
-
First thing I'd check is the uptime if you can see it. Make sure it's not rebooting when this happens.
-
-
Good to confirm. The speed it reconnected seemed unlikely the modem could boot that fast but good to know for sure.
-
@stephenw10 Looking like a cable then or possibly the BT socket as it is one of those rubbish MK4 ones!
-
I doubt it's anything upstream of the modem, like the BT master socket. pfSense shows it's actually losing link on the NIC which means it's an Ethernet problem between igb0 and the modem.
It could potentially be the modem dropping the link for some reason but I have no idea why it do that deliberately.
If it has any logs it might show that or at least show it also losing the link when pfSense does.One thing you could try here is putting a switch in between pfSense and the modem so that each side is only liked to the switch. It would have to be an unmanaged switch to pass the VLAN or have the VLAN configured on a managed switch.
Another thing would be to reassign the WAN to a different port to confirm it's not a failing NIC.
Steve
