Upgrade from 12/13 to 12/18 -> PPPoE dead…
-
Hi there,
I just updated and now PPPoE doesn't seem to be working anymore. Curious thing is that it is also not working with my older snapshot anymore…
Here is what the logs say....
ppp.log
Jan 1 01:28:22 voldemort ppp: [wan_link0] Link: reconnection attempt 200 Jan 1 01:28:22 voldemort ppp: [wan_link0] PPPoE: can't connect "[11]:"->"mpd9518-0" and "[f]:"->"left": No such file or directory Jan 1 01:28:22 voldemort ppp: [wan_link0] can't remove hook mpd9518-0 from node "[11]:": No such file or directory Jan 1 01:28:22 voldemort ppp: [wan_link0] Link: DOWN event Jan 1 01:28:22 voldemort ppp: [wan_link0] LCP: Down event Jan 1 01:28:22 voldemort ppp: [wan_link0] Link: reconnection attempt 201 in 1 seconds Jan 1 01:28:23 voldemort ppp: [wan_link0] Link: reconnection attempt 201 Jan 1 01:28:23 voldemort ppp: [wan_link0] PPPoE: can't connect "[11]:"->"mpd9518-0" and "[f]:"->"left": No such file or directory Jan 1 01:28:23 voldemort ppp: [wan_link0] can't remove hook mpd9518-0 from node "[11]:": No such file or directory Jan 1 01:28:23 voldemort ppp: [wan_link0] Link: DOWN event Jan 1 01:28:23 voldemort ppp: [wan_link0] LCP: Down event Jan 1 01:28:23 voldemort ppp: [wan_link0] Link: reconnection attempt 202 in 4 secondsWhere should this mpdxxx file be? Is that probably the problem? I also ran the setup wizard again with no solution…
system.log
Jan 1 01:32:26 voldemort ppp: [wan_link0] Link: DOWN event Jan 1 01:32:26 voldemort ppp: [wan_link0] LCP: Down event Jan 1 01:32:26 voldemort ppp: [wan_link0] Link: reconnection attempt 298 in 3 seconds Jan 1 01:32:29 voldemort ppp: [wan_link0] Link: reconnection attempt 298 Jan 1 01:32:29 voldemort ppp: [wan_link0] PPPoE: can't connect "[11]:"->"mpd9518-0" and "[f]:"->"left": No such file or directory Jan 1 01:32:29 voldemort ppp: [wan_link0] can't remove hook mpd9518-0 from node "[11]:": No such file or directory Jan 1 01:32:29 voldemort ppp: [wan_link0] Link: DOWN event Jan 1 01:32:29 voldemort ppp: [wan_link0] LCP: Down event Jan 1 01:32:29 voldemort ppp: [wan_link0] Link: reconnection attempt 299 in 2 secondsAny hints?
-
Also when I try to manually start the session with '/usr/local/sbin/mpd5 -b -k -d /var/etc -f mpd_wan.conf -p /var/run/pppoe_wan.pid -s ppp pppoeclient' I get the following error:
/libexec/ld-elf.so.1: Shared object "libexpat.so.6" not found, required by "mpd5" -
Same problem here, just got it resolved.
Was fixed when I reverted my repo from 12/17 22:09 to 12/12. Not sure what it was that killed it but its something that appears on https://rcs.pfsense.org/projects/pfsense/repos/CustomDDNS/commits/31bfb9f40a0e5a34713455f4b9df1c432e1b4fc1. -
Ok. So I'll wait for the next snap then…
-
No I was just saying I got my box fixed (by reverting to 12/12).
I'd be willing to bet the problem is a result of the changes to etc/inc/vslb.inc, but I could be wrong… -
I'd be willing to bet the problem is a result of the changes to etc/inc/vslb.inc, but I could be wrong…
No I was definitely looking at the diff backwards (undoing changes messes with your head), not really sure where the issue is at the moment. More debugging is required.
-
You guys had me worried but at one of my locations Im still on-
2.0-BETA4 (i386)
built on Thu Dec 16 14:34:04 EST 2010pppoe working for me on this build. Guess Ill hold off updates for a bit.
-
Using 2.0-BETA4 (i386) built on Sat Dec 18 09:51:58 EST 2010 pppoe works fine
-
Using 2.0-BETA4 (i386) built on Sat Dec 18 09:51:58 EST 2010 pppoe works fine
Yeah but that seems to be a newer build…Will check that one....
-
Using 2.0-BETA4 (i386) built on Sat Dec 18 09:51:58 EST 2010 pppoe works fine
When I used the same build (with git update), it didn't work, so clearly it does not plague all PPPoE users.
Rafael, can you comment as to whether the PPPoE link is your primary WAN and any what type of link it actually is (DSL, etc).
Also, chpalmer, would you mind upgrading to see if the problem does effect you as well. The date might help narrow down exactly which commit caused the problem.
Sadly, I am on vacation and can't debug the problem myself. If anyone has an extra hour or two, might they revert to Monday's snapshot and apply each git commmit from there to see when the problem occurs?
Otherwise can a dev comment as to what might be causing this? -
Tried again with pfSense-2.0-BETA4-4g-20101218-1051-nanobsd-upgrade.img.gz snap but it didn't work. Also tried a firmware default and then just adding the PPPoE settings with no luck…
Will do just the same with pfSense-2.0-BETA4-4g-20101218-2216-nanobsd-upgrade.img.gz now. But the weird thing is that after my upgrade also my other slice with the before working config never worked again...
I hope I do not have to open my box again to do a full fresh install. Any hints on how I can do a really fresh install otherwise? By booting into the other slice? Is that possible? -
Weird. Did another reboot with my box on standard config with PPPoE and it works. Just wanted to boot up in order to update to latest snap. Will do so now and then restore my config. Will tell you guys if it works…
-
PPPoE was working for me in build Fri Dec 17 14:14:00 EST 2010. It stopped working (mpdxxxx errors in the PPP log) when I updated to build Fri Dec 17 23:56:27 EST 2010. My only WAN link is PPPoE with DSL, and I have reverted to the earlier (working) build.
-
Ok. Does not work for me when I restore my config then. Actually I also tried some older configs…
Here is what I get when booting. Some weird errors:
Warning: chown(): Unable to find uid for root in /etc/inc/config.lib.inc on line 833 done. Warning: chown(): Unable to find uid for admin in /etc/inc/auth.inc on line 411 Warning: chown(): Unable to find uid for admin in /etc/inc/auth.inc on line 422 Warning: chown(): Unable to find uid for nobody in /etc/inc/rrd.inc on line 686 Warning: chown(): Unable to find uid for jle in /etc/inc/auth.inc on line 411 done.Also saw a panic when it first booted with the restored config. Another reboot and it doesn't panic anymore but still the other errors occur and no PPPoE…
Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x4 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0a18c21 stack pointer = 0x28:0xe37a1a18 frame pointer = 0x28:0xe37a1a38 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 44539 (initial thread) trap number = 12 panic: page fault cpuid = 0 Uptime: 45s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort -
So there seems to be something really wrong with my config backups. That makes me quite afraid that there could be something wrong in the backup system. I will now update to the latest snap and then try to restore section per section of the config and see where it breaks.
I also have my graphs in my config…
-
Hmm. Tried to restore part of the config but nothing changed…I tried to restore interfaces first, rebooted but no change at all. Stays on default IP on LAN etc...
Tried to restore aliases and nothing....
-
Tried again with latest snap from 12/19. Blank config with just PPPoE enabled so that my internet connection works. Tried just restoring the aliases from my config files but they do not appear on aliases. Nothing there. Did a reboot then but still nothing. I can see that it was imported under Config History though…
-
BlueMatt, I'm using pppoe as the WAN interface, it is an ADSL actually did an update for version 1.2.3, but the initial boot camp the username and password were blank being filled to function normally again :)
-
Can anyone from the dev team try to import my config? Just to see if it will work?
Thanks…
-
Try this manually
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/92a1c8e6caca910ae1f8c54751bffebd45d87682or wait for a snapshot with the patch applied.