Upgrade from 12/13 to 12/18 -> PPPoE dead…

sullrich

A fix was introduced on the 28th which means you should be running a snap from the 29th or 30th. Can someone please test this… This is one of our last issues remaining before rc1.

grandrivers

mine is still acting up have to hit connect to make it connect

jimp

Just updated my home router from a late November snap to:

2.0-BETA5 (i386) built on Thu Dec 30 11:06:13 EST 2010

PPPoE connected fine at boot without intervention. No problems here.

EDIT: Note that this is an always-on connection so I do not have dial-on-demand checked. I have a blank idle timeout, and periodic reset is disabled.

sullrich

@grandrivers:

mine is still acting up have to hit connect to make it connect

dedicated or dial up? can you compare your settings with jim-p?

jlepthien

Updated to Thu Dec 30 21:38:56 EST 2010 right now. Still seeing the same behavior as before. Doesn't come up after reboot, mpd5 dies after some time, WebUI not accessable (500 - Internal Server Error) after the first connect so I need another reboot! After that I also need to click save on WAN interface again…

grandrivers

not had the web gui problem but do have to make it connect after boot my settings are the same as jims

jimp

@jlepthien:

Updated to Thu Dec 30 21:38:56 EST 2010 right now. Still seeing the same behavior as before. Doesn't come up after reboot, mpd5 dies after some time, WebUI not accessable (500 - Internal Server Error) after the first connect so I need another reboot! After that I also need to click save on WAN interface again…

The 500 error is due to package issues, but it could be related to this in some way I suppose.

jimp

What we really need to know from everyone having issues is at least:

Architecture (i386 or amd64)
Full install or NanoBSD
Packages installed
If it's WAN or an OPT on PPPoE (or both)
PPPoE settings on the interface page (dial on demand, idle timeout, periodic reset)
PPPoE connection logs from the system logs
Your mpd_*.conf files from /var/etc/ - make sure to remove or mask your login credentials

jeebsion

Hi all .. this could be off topic … but I wonder has anyone ever dialed two or more PPPOE simultaneously? like practically using the interface type as PPPOE on more than 1 interface to dial to ISPs?

Phobia

Hi there,

I don't have time to post all of the requested info now, but I think I may be experiencing this issue now too, though I don't believe it impacted me before. I updated from a Dec.26 snap to 2.0-BETA5 (i386)
built on Fri Dec 31 06:22:39 EST 2010.

I have 2 PPPoE interfaces. My WAN and OPT1 (renamed VDSL and DSL respectively) are the PPPoE interfaces. WAN/VDSL works, OPT1/DSL does not.

Anyway - I've tried Dial on demand and not. I set the idle timeout to 0, with no periodic reset enabled. Doesn't seem to allow my OPT1 to connect.

Snip from GUI PPP Log page :

Dec 31 17:25:32 ppp: [opt1_link0] Link: Shutdown
Dec 31 17:25:32 ppp: [opt1] Bundle: Shutdown
Dec 31 17:25:32 ppp: [opt1_link0] LCP: LayerFinish
Dec 31 17:25:32 ppp: [opt1_link0] LCP: state change Starting –> Initial
Dec 31 17:25:32 ppp: [opt1_link0] LCP: Close event
Dec 31 17:25:30 ppp: [opt1] IPCP: Close event
Dec 31 17:25:30 ppp: [opt1] IFACE: Close event
Dec 31 17:25:30 ppp: caught fatal signal term
Dec 31 17:25:30 ppp: [opt1_link0] Link: reconnection attempt 81 in 2 seconds
Dec 31 17:25:30 ppp: [opt1_link0] LCP: Down event
Dec 31 17:25:30 ppp: [opt1_link0] Link: DOWN event
Dec 31 17:25:30 ppp: [opt1_link0] can't remove hook mpd32090-0 from node "[bc]:": No such file or directory
Dec 31 17:25:30 ppp: [opt1_link0] PPPoE: can't connect "[bc]:"->"mpd32090-0" and "[ba]:"->"left": No such file or directory
Dec 31 17:25:30 ppp: [opt1_link0] Link: reconnection attempt 80
Dec 31 17:25:26 ppp: [opt1_link0] Link: reconnection attempt 80 in 4 seconds
Dec 31 17:25:26 ppp: [opt1_link0] LCP: Down event
Dec 31 17:25:26 ppp: [opt1_link0] Link: DOWN event
Dec 31 17:25:26 ppp: [opt1_link0] can't remove hook mpd32090-0 from node "[bc]:": No such file or directory
Dec 31 17:25:26 ppp: [opt1_link0] PPPoE: can't connect "[bc]:"->"mpd32090-0" and "[ba]:"->"left": No such file or directory
Dec 31 17:25:26 ppp: [opt1_link0] Link: reconnection attempt 79
Dec 31 17:25:23 ppp: [opt1_link0] Link: reconnection attempt 79 in 3 seconds
Dec 31 17:25:23 ppp: [opt1_link0] LCP: Down event
Dec 31 17:25:23 ppp: [opt1_link0] Link: DOWN event
Dec 31 17:25:23 ppp: [opt1_link0] can't remove hook mpd32090-0 from node "[bc]:": No such file or directory
Dec 31 17:25:23 ppp: [opt1_link0] PPPoE: can't connect "[bc]:"->"mpd32090-0" and "[ba]:"->"left": No such file or directory

Hope this is helpful,

– Phob

clarknova

Sorry, it's going to be a few days before I'm back in town to try an update.

Phobia

Hi again,

Just checked my packages screen - I only have the Open-VM-Tools installed at present.

– Phob

Phobia

Hrm - I disabled my OPT1 interface for a while to stop the constant PPPoE requests, and just re-enabled it to discover that it has negotiated another session.

Might be a carrier issue as I see some packet loss today in my graphs.

Anyway - if the issue resurfaces, I'll post again.

– Phob

Phobia

Hi again,

OK - further to my last, with dial on demand un-ticked, I have to manually start my PPPoE sessions from Status –> Interfaces on reboot.

Also, entering the down interface from Interfaces --> DSL or VDSL then clicking save also seems to get my PPPoE back online, but when I do that, I have to manually go into System --> Routing and delete the automatically created gateways which overwrite my working gateway setup. (the system creates GW_WAN and GW_OPT1 when I've already got gateways defined with different names (VDSL and DSL) that are in turn members of gateway groups for load balancing and failover)

Sorry to muddy the waters - I re-read this entire thread which I admit not to have done the first time I posted. I appear to have the same issue as others.

-- Phob

jlepthien

@jimp:

What we really need to know from everyone having issues is at least:

Architecture (i386 or amd64)

Full install or NanoBSD

Packages installed

If it's WAN or an OPT on PPPoE (or both)

PPPoE settings on the interface page (dial on demand, idle timeout, periodic reset)

PPPoE connection logs from the system logs

Your mpd_*.conf files from /var/etc/ - make sure to remove or mask your login credentials

i386
NanoBSD
Avahi, Backup, RRD Summary, Nmap, Unbound, Shellcmd
WAN (PPPoE)
Standard Settings, except periodic reset at midnight each day
For configs/logfiles see my previous posts

jlepthien

Same stuff happening now with snap built on Sat Jan 1 19:56:40 EST 2011…
Also pfsense.com seems to be down for packages installation now, so I spare one reboot because of the packages installation of avahi ;)

somm15

Copy from another thread:
http://forum.pfsense.org/index.php?topic=31316.new;topicseen#new

PPP Logs:
Jan 1 23:53:59 ppp: [wan_link0] PPPoE: Skipping ink "wan_link0" with undefined interface

It was impossible to connect. Click on the connect button caused:
Dec 21 17:22:17 php: /status_interfaces.php: Backtrace: Array
Dec 21 17:22:17 php: /status_interfaces.php: interfaces_bring_up() was called but no variable defined.

Details logged are available in the thread mentioned above.

Architecture: i386
NanoBSD / PC Engine Alix Board (pfSense-2.0-BETA5-4g-20101231-1506-nanobsd-upgrade.img.gz)
Packages installed : pfflowd (broken since beta)
Interface: WAN
PPPoE settings on the interface page:

MTU: 1492
Enable Dial-On-Demand mode
IDLE timeout: 1200 seconds
logs (see above)

I solved this problem by playing a lot with the option and it's now fixed.
I think what solved the problem was changing the WAN from vr0 to vr2 and then back to vr0 (to be complete, vr2 is now unassigned).

I upgraded today to pfSense-2.0-BETA5-4g-20110101-1956-nanobsd-upgrade.img and I cannot reproduce the problem (I tried to change option but it looks ok).

Should you need any more test/information, don't hesitate to contact me.

Phobia

Hi all,

Sorry for the delay, but some more info about my setup :

Architecture: i386
Full Install (2.0-BETA5 (i386) built on Fri Dec 31 14:08:23 EST 2010)
Packages installed : Open-VM-Tools
Interface: WAN & OPT1 (renamed VDSL and DSL)
PPPoE settings on the interface page :

MTU: <blank>- NO Dial-On-Demand mode
NO IDLE timeout: <blank>My setup is a VM running under VMWare (hence the Open-VM-Tools package).

– Phob</blank></blank>

grandrivers

I sorted out my problem I had created A Modem access (opt2) and that seemed to stop ppoe from working removed thta and all is fine

romainp

Ok I have the same problem:

Architecture : i386
Full install
Packages installed : Darkstat
WAN -> pppoe via em0 and opt (let's call it DSL) connected to em0
dial on demand: checked
idle timeout: 0
periodic reset : disabled
PPPoE connection logs from the system logs
see my post : http://forum.pfsense.org/index.php/topic,31409.0.html
mpd_wan.conf:

startup:
# configure the console
set console close
# configure the web server
set web close

default:
pppoeclient:
create bundle static wan
set iface name pppoe0
set iface route default
set iface enable on-demand
set iface idle 0
set iface addrs 10.10.1.1 10.10.1.2
set iface enable tcpmssfix
set iface up-script /usr/local/sbin/ppp-linkup
set iface down-script /usr/local/sbin/ppp-linkdown
set ipcp ranges 0.0.0.0/0 0.0.0.0/0
#log -bund -ccp -chat -iface -ipcp -lcp -link

create link static wan_link0 pppoe
set link action bundle wan
set link disable multilink
set link keep-alive 10 60
set link max-redial 0
set link disable chap pap
set link accept chap pap eap
set link disable incoming
set link mtu 1492
set auth authname "xxxxx"
set auth password xxxxx
set pppoe iface em0
open^M