NIC issues and advise

swansense

@stephenw10 said in NIC issues and advise:

Just saving that page would likely have brought it back by re-applying the default gateway. It should be set to PPPoE_GW though to avoid it trying to default to one of the VPNs.

Same thing happened again last night.

your right just saving the routing page brought the connection back up.

Im going to have to figure out some way of automatically saving the routing page for me a minute or so after the PPPOE connection goes down hopefully that will save me doing it manually.

stephenw10

OK, then firstly check Diag > Routes when this next happens. Is there a valid default route shown?

If not check the system and routing logs for what happened when the PPPoE went down (and when it came back up).

swansense

@stephenw10 said in NIC issues and advise:

OK, then firstly check Diag > Routes when this next happens. Is there a valid default route shown?

If not check the system and routing logs for what happened when the PPPoE went down (and when it came back up).

Thank you. You were correct so when the connection went down the other night i checked Diag > Routes like you mentioned and it looked like there was a default route on the lan interface for some reason. by re-applying the default gateway the connection was brought back up.

Diag > Routes when No lan internet connectivity before re-applying the default gateway

Diag > Routes when everything working as expected.

Looking at the IP it was my wan address before and i had a script run at boot to set that IP as Pfsense would not allow me use a /32 as a wan address. The script was disabled long ago so im not sure why that address is popping up as a route.

Here is the script with the route commented out. I can remember how i ran this at boot to be honest so just commented out the route in the script when i changed ISPs a few years back.

cat configure-route.sh
#
#
#

#route add -net 62.210.109.1/32 -IFACE em1
#route add default 62.210.109.1
#

I can actually see that route listed but it is disabled and has been since i changed ISP. I just deleted it there now so hopefully that will resolve the issue unless you have any other suggestions?

stephenw10

Ah, some custom script!

Well I would try to find where that is run from and remove it if you can. There is no reason to have that present still.

swansense

@stephenw10

I checked /usr/local/etc/rc.d/ and its not in there.

I must of deleted it so it no longer runs at boot. I deleted the route instead of just disabled it from system default gateway so hopefully that will do the trick. Also the script had all the commands commented out so even if it does run it doesnt actually add the route.

Hopefully this will resolve it but ill find out soon enough i suppose.

swansense

it happened again and the 62.210 route was in dia > status even though it was deleted from system > routing.

i am greping through the file system to see where i can find the script that runs adding the route but i am certain that script only exists in one location and the route commands are commented out. im also nearly certain this script only runs at boot so not sure why it pops up after connection goes down.

other than /usr/local/etc/rc.d/ can you think of anywhere else a script/command can be ran at boot?

stephenw10

It could be in a shellcmd:
https://docs.netgate.com/pfsense/en/latest/development/boot-commands.html?highlight=shellcmd#shellcmd-option

swansense

@stephenw10 said in NIC issues and advise:

It could be in a shellcmd:
https://docs.netgate.com/pfsense/en/latest/development/boot-commands.html?highlight=shellcmd#shellcmd-option

thanks i managed to find it and remove it.

issue has not happened in a week or so now.

Next step is to figure out the realtek nic issue.