Cannot Get Bridged Modem to work with WAN PPPoE- what am I doing Wrong?
-
I just tried bridging mode on a third modem, a Dlink DSL2750b, with no luck, refer log and screenshot. Says it's connected but it's not.
Getting frustrated it must be something simple!
Actually… have a look at the last ppp log you posted.
Oct 11 15:51:17 ppp: [wan_link0] MRU 1492
Oct 11 15:51:17 ppp: [wan_link0] MAGICNUM 6bda01c0
Oct 11 15:51:17 ppp: [wan_link0] LCP: rec'd Configure Nak #22 (Ack-Sent)
Oct 11 15:51:17 ppp: [wan_link0] MRU 1500
Oct 11 15:51:17 ppp: [wan_link0] LCP: not converging
Oct 11 15:51:17 ppp: [wan_link0] LCP: parameter negotiation failed
Oct 11 15:51:17 ppp: [wan_link0] LCP: state change Ack-Sent –> Stopped
Oct 11 15:51:17 ppp: [wan_link0] LCP: LayerFinish
Oct 11 15:51:17 ppp: [wan_link0] PPPoE: connection closedYour bridged modem is now set up correctly. From the looks of that log there is communication happening between pfsense and your ISP (dodo). Congrats! you are now having the same issue as me with pppoe negotiation failing due to MTU. This only happens for me on pfsense. Every other firewall OS i try connects to pppoe fine.
-
you are now having the same issue as me with pppoe negotiation failing due to MTU. This only happens for me on pfsense.
Perhaps you could try a snapshot build of pfSense 2.1 whch includes a more up to date version of the PPP daemon (5.6) than is included in pfSense 8.1 (5.5).
-
Perhaps you could try a snapshot build of pfSense 2.1 whch includes a more up to date version of the PPP daemon (5.6) than is included in pfSense 8.1 (5.5).
Tried it just then and unfortunately the issue still exists. There must be an incompatibility with pppd and dodo's configuration on their end. I remember trying out pfsense back when i was on iinet and internode before that and pppoe worked perfectly fine.
-
Wonder if Dodo could do true bridged mode for you on their end.
I.E. no log in. Its basically an ethernet connection using a DSL modem.
-
Wonder if Dodo could do true bridged mode for you on their end.
I.E. no log in. Its basically an ethernet connection using a DSL modem.
Can't be done. All home ADSL connections here in Australia use PPPoA and PPPoE to my knowledge. It's just the way the network is set up here.
The above shouldn't have to be done anyway. If the Windows and Linux PPPoE clients can deal with dodo's configuration just fine then why can't pppd and pfsense or any other freebsd based routing OS? all that i've tried have the exact same issue.
-
I too could not get this issue resolved - getting PPPOE in PFsense to connect succesfully to Dodo. Installed IPFIRE and had it all running within an hour. Its a good alternative, pity couldn't resolve this.
-
Hi,
I don't know how different the NB6 is from my NB5 but I had a lot of problems using Netcomm's documentation on setting the NB5 into bridge mode.
I eventually found this on Whirlpool: http://forums.whirlpool.net.au/archive/483677. It solved the problem plus gave me a way to get into the modem (through the USB port) while in bridge mode. After that the pfSense part was easy.
May be of some help.
-
i m with clubtelco which runs on the dodo network, until the middle of this year pfsense worked, but now it doesn't i personally spend a long time trying to solve.
i have found no matter what the settings i use in web interface or command line to change the mtu to 1460, pfsense will not connect and the log always show that that it is attempting to connect at 1496 mtu
-
Update: noticed a bug fixed was mentioned, so Tried the latest version of PFsense, (v2/03) and stilling getting same error
It says in log files something about a value of 1500 MTU being "too high"
anyone else having any luck here with this issue?
-
Just wondering if this has been resolved in the new version released Sept 2013?
Anyone tried this?
-
not sure if this is relevant any longer, however it appears the pfsense / dodo isp problem has been resolved.
I'm running 2.1.3, however I suspect it might be dodo that sorted things out. Looks like they allow an MRU of 1492 now, pretty sure last time I tried this (a year or more ago) they were only accepting 1500 which was causing the problems. Anyway, I hope this may help someone if they are still having issues.
2.1.3-RELEASE (i386)
built on Thu May 01 15:52:17 EDT 2014
FreeBSD 8.3-RELEASE-p16
