Pppoe failing to connect on wan

aray · Aug 9, 2008, 11:11 AM

Hi All,

I replaced a Netgear modem router (was working) with a pfsense box. Same credentials, but pfsense can't connect (running 1.2). I plugged into my laptop (windows boot), connected no problems. I tried a different ISP with pfsense, and it worked.

I have had a hunt around, and I found a post commenting that if the ISP only hands out one DNS entry, then ppp will fail. I can't change ISP (under contract). Is there a known work around? My logs look like so (it connects, then straight away dies).

Any help greatly appreciated!

Jan 1 11:33:08 router mpd: [pppoe] PAP: using authname "myuser"
Jan 1 11:33:08 router mpd: [pppoe] PAP: sending REQUEST
Jan 1 11:33:08 router mpd: [pppoe] LCP: LayerUp
Jan 1 11:33:09 router mpd: [pppoe] PAP: rec'd ACK #1
Jan 1 11:33:09 router mpd: [pppoe] LCP: authorization successful
Jan 1 11:33:09 router mpd: [pppoe] LCP: phase shift AUTHENTICATE –> NETWORK
Jan 1 11:33:09 router mpd: [pppoe] setting interface ng0 MTU to 1492 bytes
Jan 1 11:33:09 router mpd: [pppoe] up: 1 link, total bandwidth 64000 bps
Jan 1 11:33:09 router mpd: [pppoe] IPCP: Up event
Jan 1 11:33:09 router mpd: [pppoe] IPCP: state change Starting –> Req-Sent
Jan 1 11:33:09 router mpd: [pppoe] IPCP: SendConfigReq #1
Jan 1 11:33:09 router mpd: IPADDR 0.0.0.0
Jan 1 11:33:09 router mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jan 1 11:33:09 router mpd: PRIDNS 0.0.0.0
Jan 1 11:33:09 router mpd: SECDNS 0.0.0.0
Jan 1 11:33:09 router mpd: [pppoe] error writing len 32 frame to bypass: Network is down
Jan 1 11:33:09 router mpd: [pppoe] IPCP: rec'd Configure Request #95 link 0 (Req-Sent)
Jan 1 11:33:09 router mpd: IPADDR 10.100.100.254
Jan 1 11:33:09 router mpd: 10.100.100.254 is OK
Jan 1 11:33:09 router mpd: [pppoe] IPCP: SendConfigAck #95
Jan 1 11:33:09 router mpd: IPADDR 10.100.100.254
Jan 1 11:33:09 router mpd: [pppoe] IPCP: state change Req-Sent –> Ack-Sent
Jan 1 11:33:11 router mpd: [pppoe] IPCP: SendConfigReq #2
Jan 1 11:33:11 router mpd: IPADDR 0.0.0.0
Jan 1 11:33:11 router mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jan 1 11:33:11 router mpd: PRIDNS 0.0.0.0
Jan 1 11:33:11 router mpd: SECDNS 0.0.0.0
Jan 1 11:33:11 router mpd: [pppoe] IPCP: rec'd Configure Reject #2 link 0 (Ack-Sent)
Jan 1 11:33:11 router mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jan 1 11:33:11 router mpd: PRIDNS 0.0.0.0
Jan 1 11:33:11 router mpd: SECDNS 0.0.0.0
Jan 1 11:33:11 router mpd: [pppoe] IPCP: SendConfigReq #3
Jan 1 11:33:11 router mpd: IPADDR 0.0.0.0
Jan 1 11:33:11 router mpd: [pppoe] IPCP: rec'd Configure Nak #3 link 0 (Ack-Sent)
Jan 1 11:33:11 router mpd: IPADDR 202.55.158.191
Jan 1 11:33:11 router mpd: 202.55.158.192 is OK
Jan 1 11:33:11 router mpd: [pppoe] IPCP: SendConfigReq #4
Jan 1 11:33:11 router mpd: [pppoe] IPCP: rec'd Configure Ack #4 link 0 (Ack-Sent)
Jan 1 11:33:11 router mpd: [pppoe] IPCP: state change Ack-Sent –> Opened
Jan 1 11:33:11 router mpd: [pppoe] IPCP: LayerUp
Jan 1 11:33:11 router mpd: 202.55.158.191 -> 10.100.100.254
Jan 1 11:33:11 router mpd: [pppoe] IFACE: Up event
Jan 1 11:33:11 router mpd: [pppoe] setting interface ng0 MTU to 1492 bytes
Jan 1 11:33:11 router mpd: [pppoe] exec: /sbin/ifconfig ng0 202.55.158.191 10.100.100.254 netmask 0xffffffff -link0
Jan 1 11:33:11 router mpd: [pppoe] exec: /sbin/route add 202.55.158.191 -iface lo0
Jan 1 11:33:11 router mpd: [pppoe] exec: /sbin/route add 0.0.0.0 10.100.100.254
Jan 1 11:33:11 router mpd: [pppoe] exec: /usr/local/sbin/ppp-linkup ng0 inet 202.55.158.191 10.100.100.254 myuser
Jan 1 11:33:11 router mpd: [pppoe] IFACE: Up event
Jan 1 11:33:11 router mpd: [pppoe] IPCP: rec'd Terminate Request #96 link 0 (Opened)
Jan 1 11:33:11 router mpd: [pppoe] IPCP: state change Opened –> Stopping
Jan 1 11:33:11 router mpd: [pppoe] IPCP: SendTerminateAck #5
Jan 1 11:33:11 router mpd: [pppoe] IPCP: LayerDown

aray · Aug 9, 2008, 11:09 AM

oooopps, topic should read "on WAN" (not lan)

eri-- · Aug 9, 2008, 12:10 PM

Can you verify that the same case exist with 1.2.1 or 1.3?

aray · Aug 9, 2008, 12:40 PM

@ermal:

Can you verify that the same case exist with 1.2.1 or 1.3?

1.2.1-RC1
built on Thu Aug 7 09:48:37 EDT 2008

I just found a related post with the "nodnssec" option…worked a treat.

http://forum.pfsense.org/index.php/topic,7248.msg41434.html#msg41434

Thank you for all those who read this.

I spent a few hours googling/searching to find a solution (before I posted).