PPPoE network connection loss. Restart required
-
Hi all,
I'm having an issue where the network will drop at random times throughout the day and it requires the router to be reset in order to pick up a connection again.
This has been an ongoing issue for quite some time now and I haven't found a fix online just yet.
Prior to PFSENSE I was using Kong DD-WRT on an old router and hadn't experienced anything like this.
Any help is appreciated!
Kind regards,
Tom -
Has it always done that since you installed pfSense or something changed sometime afterwards?
What actually fails when it 'drops'? You can still access the webgui?
The PPP link fails? What do the logs show?
Are you running 2.5.2?
Steve
-
@stephenw10 Hi Stephen, appreicate the reply.
It's always done this ever since we managed to get a connection to the internet. When it drops I can still access the GUI - it shows as Offline - Packetloss on the gateway.
I only assume it's PPPoE related after a few Google searches and people mentioning it, but the fixes for turning off (on?) the gateway monitoring didn't work.
Currently on 2.5.1 too.
Not particularly great at navigating the PFSENSE menu, would you mind letting me know where I can find these logs and I can post them once the internet drops out which I would imagine to be soon.
Cheers,
Tom -
Check the PPPoE status when it fails in Status > Interfaces.
You can also try disconnecting and/or reconnecting the PPPoE session there and see if that brings it back.
The logs are in Status > System Logs. The main system log there will probably show what happened. The PPP logs tab may have more detail if it's something odd in the PPPoE session.
Steve
-
@stephenw10 Hi Steve, sorry for the delay.
It's only just conked out and I've managed to get the logs in the meantime.
General log entries.txt
System logs - PPP.txtKind regards,
Tom -
Ok, this is nothing to do with the PPPoE connection it's the Realtek NIC giving up:
Oct 21 08:21:52 kernel re0: watchdog timeout Oct 21 08:21:52 kernel re0: link state changed to DOWN Oct 21 08:21:52 check_reload_status 386 Linkup starting re0Are all the NICs on that box reX?
Do you have any spare interfaces you could swap in for that?
Steve
-
@stephenw10 Ah, that's a shame!
Unfortunately I don't - had ordered this NIC through eBay on recommendation.
Is a replacement the only solution? Presumably driver updates won't resolve this /can't be installed?
Kind regards,
Tom -
You can try the alternative Realtek driver. In 2.5.2 do this: https://forum.netgate.com/post/962889
Steve
-
@stephenw10 I think I've managed to do that via 'Diagnostics' > 'Command Prompt'. Then I executed the 2 lines of code and rebooted as mentioned, although nothing really happened after this was put through: echo 'if_re_load="YES"' >> /boot/loader.conf.local
I've then gone onto the Boot Logs and these are the only Realtek related options on there. Assuming it's on Status > System Logs > OS Boot
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xe000-0xe0ff mem 0xfea04000-0xfea04fff,0xfea00000-0xfea03fff irq 36 at device 0.0 on pci2
hdacc1: <Realtek ALC221 HDA CODEC> at cad 0 on hdac1
hdaa1: <Realtek ALC221 Audio Function Group> at nid 1 on hdacc1
pcm4: <Realtek ALC221 (Analog 2.0+HP/2.0)> at nid 20,33 and 24,27 on hdaa1
pcm5: <Realtek ALC221 (Front Analog Headphones)> at nid 26 on hdaa1Kind regards,
Tom -
Mmm, I would definitely run those are the command line so you can see all the output.
You should see the driver version reported in the logs if it loaded. You might see an error if it didn't load for some reason.
Check the line is correctly in the file: /boot/loader.conf.local
Steve
-
@stephenw10 Hi Steve,
Apologies, where is /boot/loader.conf.local located? I'm not very clued up.
If it's not listing the driver version in there, where's the correct place to run the commands you mentioned in the other thread?
Much appreciated,
Tom -
/boot/loader.conf.local is the location.
Ok you need to access the command line interface. That means either using the console dircetly and connecting to the firewall via SSH.
https://docs.netgate.com/pfsense/en/latest/hardware/connect-to-console.html
When you connect you will see the console menu:
https://docs.netgate.com/pfsense/en/latest/config/console-menu.htmlYou choose option 8 to access the shell where you can run commands dircetly.
For example:[21.05.1-RELEASE][root@pfSense.home.arpa]/root: cat /boot/loader.conf.local cat: /boot/loader.conf.local: No such file or directoryOn that box there is no .local file because I don't need to have any custom loader values set.
You can runcat /boot/loader.conf.localfrom Diag > Command Prompt in the gui safely since it's a single command with a fixed output.Steve
-
@stephenw10 Belter! It's now currently on re0: version:1.96.04 so hopefully that alleviates it.
In regard to a replacement should this not work (Dell Intel i350-T4), do you have any suggestions? I wasn't able to fully utilise the ports as I couldn't get network connections to them. I wanted to run a 2nd access point that'd be used as a VPN initally but it seems a bit too technical thus far.
I really appreciate the help you've provided on this, and my previous post from a few months ago. I'm extremely grateful.
Kind regards,
Tom -
Cool. Yes an i350-T4 should work. Is that still in the box? Run
ifconfigand make sure all 4 interfaces show up.Steve
-
@stephenw10 The -350-T4 is the one I installed initially on recommendation! I have no backup option currently
I've attached the notepad with the details, all of them seem to show up and I'm hoping this now stays up without requiring a reboot. If that's the case, then I'll probably start work on trying to get that 2nd access point going (and inevitably end up back here)
Kind regards,
Tom
ifconfig.txt -
That output looks fine for the igb NICs. You might want to disable hardware checksum offloading in Sys > Adv > Networking. That will apply it globally. It should be fine on the Intel NICs but has been known to give problems on other hardware, like the Realtek.
You appear to have bridged igb2 and igb3 they have IP addresses in different subnets which looks wrong.
Steve
