PPPoE troubles



  • Hello.
    I have a Westell E90-610015 ADSL+ modem/NAT router that I can use successfully in bridge mode with my computer.  Because this modem is meant for Verizon and I can only get ATT, I cannot use it as a NAT router, only a modem. 
    I want to use it along with a DHCP ethernet WAN connection in a multi-WAN setup configuration with pfsense.  I have not been able to make this work so far.  Here are the relevant entries from system.log:
    Oct 11 01:55:22 pfsense mpd: mpd: pid 24467, version 3.18 (root@freebsd6.geekgod.com 12:32  6-Jan-2008)
    Oct 11 01:55:22 pfsense mpd: [pppoe] ppp node is "mpd24467-pppoe"
    Oct 11 01:55:22 pfsense mpd: [pppoe] exec: /sbin/ifconfig dc0 up
    Oct 11 01:55:22 pfsense mpd: [pppoe] using interface ng0
    Oct 11 01:55:22 pfsense mpd: [pppoe] IPCP: peer address cannot be zero
    Oct 11 01:55:22 pfsense mpd: [pppoe] IFACE: Open event
    Oct 11 01:55:22 pfsense mpd: [pppoe] IPCP: Open event
    Oct 11 01:55:22 pfsense mpd: [pppoe] IPCP: state change Initial –> Starting
    Oct 11 01:55:22 pfsense mpd: [pppoe] IPCP: LayerStart
    Oct 11 01:55:22 pfsense mpd: [pppoe] bundle: OPEN event in state CLOSED
    Oct 11 01:55:22 pfsense mpd: [pppoe] opening link "pppoe"…
    Oct 11 01:55:22 pfsense mpd: [pppoe] link: OPEN event
    Oct 11 01:55:22 pfsense mpd: [pppoe] LCP: Open event
    Oct 11 01:55:22 pfsense mpd: [pppoe] LCP: state change Initial –> Starting
    Oct 11 01:55:22 pfsense mpd: [pppoe] LCP: LayerStart
    Oct 11 01:55:22 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:22 pfsense mpd: [pppoe] device is now in state OPENING
    Oct 11 01:55:31 pfsense mpd: [pppoe] PPPoE connection timeout after 9 seconds
    Oct 11 01:55:31 pfsense mpd: [pppoe] device: DOWN event in state OPENING
    Oct 11 01:55:31 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:31 pfsense mpd: [pppoe] link: DOWN event
    Oct 11 01:55:31 pfsense mpd: [pppoe] LCP: Down event
    Oct 11 01:55:31 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:31 pfsense mpd: [pppoe] pausing 4 seconds before open
    Oct 11 01:55:31 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:35 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:35 pfsense mpd: [pppoe] pausing 1 seconds before open
    Oct 11 01:55:35 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:36 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:36 pfsense mpd: [pppoe] device is now in state OPENING
    Oct 11 01:55:45 pfsense mpd: [pppoe] PPPoE connection timeout after 9 seconds
    Oct 11 01:55:45 pfsense mpd: [pppoe] device: DOWN event in state OPENING
    Oct 11 01:55:45 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:45 pfsense mpd: [pppoe] link: DOWN event
    Oct 11 01:55:45 pfsense mpd: [pppoe] LCP: Down event
    Oct 11 01:55:45 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:45 pfsense mpd: [pppoe] pausing 4 seconds before open
    Oct 11 01:55:45 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:49 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:49 pfsense mpd: [pppoe] pausing 1 seconds before open
    Oct 11 01:55:49 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:50 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:50 pfsense mpd: [pppoe] device is now in state OPENING
    Oct 11 01:55:59 pfsense mpd: [pppoe] PPPoE connection timeout after 9 seconds
    Oct 11 01:55:59 pfsense mpd: [pppoe] device: DOWN event in state OPENING
    Oct 11 01:55:59 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:55:59 pfsense mpd: [pppoe] link: DOWN event
    Oct 11 01:55:59 pfsense mpd: [pppoe] LCP: Down event
    Oct 11 01:55:59 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:55:59 pfsense mpd: [pppoe] pausing 4 seconds before open
    Oct 11 01:55:59 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:56:03 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:56:03 pfsense mpd: [pppoe] pausing 1 seconds before open
    Oct 11 01:56:03 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:56:04 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:56:04 pfsense mpd: [pppoe] device is now in state OPENING
    Oct 11 01:56:13 pfsense mpd: [pppoe] PPPoE connection timeout after 9 seconds
    Oct 11 01:56:13 pfsense mpd: [pppoe] device: DOWN event in state OPENING
    Oct 11 01:56:13 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:56:13 pfsense mpd: [pppoe] link: DOWN event
    Oct 11 01:56:13 pfsense mpd: [pppoe] LCP: Down event
    Oct 11 01:56:13 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:56:13 pfsense mpd: [pppoe] pausing 4 seconds before open
    Oct 11 01:56:13 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:56:17 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:56:17 pfsense mpd: [pppoe] pausing 1 seconds before open
    Oct 11 01:56:17 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:56:18 pfsense mpd: mpd: caught fatal signal term
    Oct 11 01:56:18 pfsense mpd: [pppoe] IPCP: Down event
    Oct 11 01:56:18 pfsense mpd: [pppoe] IFACE: Close event
    Oct 11 01:56:18 pfsense mpd: [pppoe] IPCP: Close event
    Oct 11 01:56:18 pfsense mpd: [pppoe] IPCP: state change Starting –> Initial
    Oct 11 01:56:18 pfsense mpd: [pppoe] IPCP: LayerFinish
    Oct 11 01:56:18 pfsense mpd: [pppoe] bundle: CLOSE event in state OPENED
    Oct 11 01:56:18 pfsense mpd: [pppoe] closing link "pppoe"…
    Oct 11 01:56:18 pfsense mpd: [pppoe] device: OPEN event in state DOWN
    Oct 11 01:56:18 pfsense mpd: [pppoe] device is now in state OPENING
    Oct 11 01:56:18 pfsense mpd: [pppoe] link: CLOSE event
    Oct 11 01:56:18 pfsense mpd: [pppoe] LCP: Close event
    Oct 11 01:56:18 pfsense mpd: [pppoe] LCP: state change Starting –> Initial
    Oct 11 01:56:18 pfsense mpd: [pppoe] LCP: LayerFinish
    Oct 11 01:56:18 pfsense mpd: [pppoe] device: CLOSE event in state OPENING
    Oct 11 01:56:18 pfsense mpd: [pppoe] device is now in state CLOSING
    Oct 11 01:56:18 pfsense mpd: [pppoe] device: DOWN event in state CLOSING
    Oct 11 01:56:18 pfsense mpd: [pppoe] device is now in state DOWN
    Oct 11 01:56:18 pfsense mpd: [pppoe] link: DOWN event
    Oct 11 01:56:18 pfsense mpd: [pppoe] LCP: Down event
    Oct 11 01:56:20 pfsense mpd: mpd: process 24467 terminated

    I have set up the WAN interface for a PPPoE connection and entered in my username and password for the connection.  However, as you can see above, it will not connect properly.
    I have been able to get this to work with a smoothwall router using the modem in bridged mode with the PPPoE authentication done on the router, but smoothwall does not support multiple wan connections.
    I would really like to get this to work.  Possibly make use of FreeBSDs ppp.conf to set it up?  However I don't know how to get the webConfigurator to still work, ie use the NAT and firewall screens, without having it also set up the authentication.

    Any help is appreciated so thanks in advance.



  • Seems like your interafce(wan), where the modem is connected, is flapping up and down or you have a mismatch on duplex.



  • Well, I can rule out a duplex mismatch.  I pointed out in my first post that the modem worked fine with a smoothwall router and the same NIC was moved to my pfsense box so that there would be no problems with the modem.
    I can see how you would think that it is flapping.  But how can I get to not be flapping?



  • I found a possible workaround at http://lists.freebsd.org/pipermail/freebsd-ports/2004-October/016617.html
    Will this work and if so how I might implement this?



  • Don't know why but after an upgrade to 1.2.1-RC1 everything just started working.
    Currently I would say that the problem has been solved.



  • Hi

    It seems because the config had regenerated while upgrading to 1.2.1 then some "glitch" went away. Yeah, it happens to me several times and I don't care as far as my box is running fine  ;D

    Cheers,

    @cwoelkers:

    Don't know why but after an upgrade to 1.2.1-RC1 everything just started working.
    Currently I would say that the problem has been solved.


Log in to reply