No logs of pppoe process
-
Yes, the logging needs to be tweaked. Currently the only logging you see are for unexpected events. Most of which are harmless, like:
Apr 21 20:54:38 kernel if_pppoe: pppoe0: pap failure Apr 21 20:54:38 kernel if_pppoe: pppoe: GENERIC ERROR (errortag 1) Apr 21 21:00:25 kernel if_pppoe: pppoe0: failed to set default route 17 ... -
And now logging works again :)
-
@netblues said in No logs of pppoe process:
And now logging works again :)
What?
Did you switch to old backend? -
@w0w Certainly not
May 18 11:26:20 ppp 44990 [wan] IFACE: Rename interface ng0 to pppoe0
May 18 11:26:20 ppp 44990 [wan] IFACE: Up event -
@netblues
This looks like something is broken — this is a typical mpd5 log when using Netgraph. ng0 is netgraph and this is not used in new backend -
Yup, ng0 should never exist if it's using if_pppoe.
You can check it using:
pppcfg pppoe0That will return nothing if it's not an if_pppoe interface.
-
The only way to get additional output from if_pppoe I'm aware of is to enable debug mode like:
ifconfig pppoe0 debugYou will then get a lot of output at the console and dmesg.
-
@stephenw10 So, this is another bug.
The state of the checkbox doesn't reflect the use of new kernel mode.
Most probably is set when you switch the interface, but if you restore the configuration
it is ignored..Steps to reproduce
Backup configuration on latest 25.03 beta, using kernel ppp
Install ce 2.7.2 clean.
restore 25.03 beta configuration to get system going
Run upgrades as requested to latest 25.03
And then restore configuration again, just in case something went missing and you end
with mpd5 logsI'll try to switch it off an on again and see if it behaves.
-
It's a loadable kernel module so it's only loaded at boot after the loader line has been added.
If you load the config into 2.7.2 (which isn't valid) that setting doesn't do anything. When you upgrade to 25.03 it reboots but the loader line still isn't present. So once it's in 25.03 the loader lin e will have been added but the module won't actually load until the next boot.
If you upgrade to 25.03 first then restore the config it should work as expected.
-
@stephenw10 Yes, but I must restore the configuration to make things work .
After switching config twice, I ended up into another corner situation
Last messages logged (at shutdown due to kernel mode ppp checked)
May 18 18:45:24 ppp 50090 process 50090 terminated
May 18 18:45:24 ppp 50090 [wan_link0] Link: Shutdown
May 18 18:45:24 ppp 50090 [wan] Bundle: Shutdownbut, after reboot
No more ppp logs BUT
pppcfg pppoe0
dev: vtnet0 state: session
sid: 0xafc8 PADI retries: 0 PADR retries: 0 time: 00:07:59
sppp: phase network authproto auto authname "xxxxx@xxx.com" peerproto auto
dns: 212.205.212.205 195.170.0.1
What am I running? How do we fix this?
-
@netblues said in No logs of pppoe process:
What am I running?
Now it is If_pppoe and pppoe session established successfully.
@netblues said in No logs of pppoe process:
How do we fix this?
What is wrong?
Post bug report on redmine, I think… -
@netblues said in No logs of pppoe process:
No more ppp logs BUT
pppcfg pppoe0
dev: vtnet0 state: session
sid: 0xafc8 PADI retries: 0 PADR retries: 0 time: 00:07:59
sppp: phase network authproto auto authname "xxxxx@xxx.com" peerproto auto
dns: 212.205.212.205 195.170.0.1That's the correct expected output with if_pppoe loaded and working. There is no problem there.
-
@stephenw10 said in No logs of pppoe process:
You can check it using: pppcfg pppoe0
That will return nothing if it's not an if_pppoe interface.
Based on that I misunderstood that still I should get nothing when running kernel too.
Thanks for clearing it up -
@stephenw10 In the PFSENSE 2.8 release, is it correct that PPP log entries in the GUI will show when the mpd5 module is used instead of the if_pppoe module?
-
Yes the logs will be shown there the same as previous versions if you don't enable if_pppoe.