PPPoE not coming up after reboot.
ehoitinga last edited by
I'm fairly new at this forum, so I hope that I put my posting in the right sub-forum.
Recently I moved from SmoothWall to pfSense 1.2.3 on an 'ancient' Nokia IP330 router (AMD-K6 3D processor, 256MB RAM and
it's running quit nice. I found that pfSense is much more configurable than a SmoothWall. I'm very happy with it.
The 1.2.3 version was running perfectly on my appliance. Last week I decided to move to 2.0RC3. I did a console upgrade using the
pfsense 2.0 snapshot repository URL. The upgrade went well, the old configuration file was interpreted as I hoped and the PPPoE
connection to my provider was started immediately.
The only thing that bothers me was at start-up. When starting the Ethernet interfaces I got a message saying "The INVALID MAC
address (ff:ff:ff:ff:ff:ff) on interface fxp2 has been automatically replaced with 02:b7:fd:f8:8c:f3". I thought that network cards had
a MAC address of themselves?
When the appliance was finished booting, the PPPoE interface was not started. I tried restarting it manually, supplying fresh credentials
and save, reboot on modem, another reboot of pfSense. Nothing helped. The only way to get my WAN interface backup was to change
the type of the interface to none, save it, reset it to PPPoE, supplying the credentials, and save it again.
I did not see this problem on version 1.2.3, apart from the ff:ff:ff:ff:ff:ff MAC address message. Has anyone ran in to this also?
wallabybob last edited by
The IP3330 has a system ROM which supplies the base MAC address for all the NICs in the box: If running NOKIA software fxp0 gets base+0, fxp1 gets base+1 etc
There are a number of discussions of pppoe restart problems in the 2.0 forum: http://forum.pfsense.org/index.php/board,49.0.html Some people have pppoe restart problems, lots don't. (I don't.)
If you are using the "official" RC3 build of about a month ago it would probably be worthwhile upgrading to a recent snapshot build to see if there is an improvement in the pppoe behaviour.
ehoitinga last edited by
I upgraded to the latest 2.0 snapshot and the problem is still there. After a reboot I still have to set my WAN interface to 'none', save and then reset it to PPPoE with the proper credentials. After that the PPPoE connection comes up immediately.
Below an excerpt of my logfile:
Jul 30 19:34:29 ppp: [wan_link0] Link: reconnection attempt 42 in 4 seconds
Jul 30 19:34:29 ppp: [wan_link0] LCP: Down event
Jul 30 19:34:29 ppp: [wan_link0] Link: DOWN event
Jul 30 19:34:29 ppp: [wan_link0] can't remove hook mpd8424-0 from node ":": No such file or directory
Jul 30 19:34:29 ppp: [wan_link0] PPPoE: can't connect ":"->"mpd8424-0" and "[f]:"->"left": No such file or directory
Jul 30 19:34:29 ppp: [wan_link0] Link: reconnection attempt 41
I also compared the /cf/conf/config.xml from the appliance at my work and the appliance at home. They are running exactly the same version 2.0RC 3 Fri Jul 29 22:08:01 EDT 2011. The only differnce between the two installations is that the appliance at home is upgraded from 1.2.3 to 2.0 RC3 and the appliance at my work is a preinstalled 2.0 appliance updated to the latest 2.0 snapshot.
config WAN interface / pppoe home:
<wan><enable><if>pppoe0</if> <blockpriv><blockbogons><spoofmac>00:00:c0:7a:bc:47</spoofmac> <ipaddr>pppoe</ipaddr></blockbogons></blockpriv></enable></wan> <ppp><ptpid>0</ptpid> <type>pppoe</type> <if>pppoe0</if> <ports>fxp1</ports> <username>xxxxxx@yyyyyy</username> <password>hdgvcfdr</password></ppp>
config WAN interface / pppoe work:
<wan><if>pppoe0</if> <blockpriv><blockbogons><disableftpproxy><bandwidth>100</bandwidth> <bandwidthtype>Mb</bandwidthtype> <enable><spoofmac><ipaddr>pppoe</ipaddr></spoofmac></enable></disableftpproxy></blockbogons></blockpriv></wan> <ppp><ptpid>0</ptpid> <type>pppoe</type> <if>pppoe0</if> <ports>vr1</ports> <username>xxxxxx@yyyyyy</username> <password>ksdfghkkldjsf</password> <bandwidth></bandwidth></ppp>
Looks like on my device at home I'm missing some fields in the wan and ppp part of the XML config file. Can this be the cause of the PPPoE problems?