DSL PPPoe refuses to accept credentials
-
I've been battling this for about 2 weeks now, so I thought it was time to ask the experts for some help.
I have DSL internet through CenturyLink. I've bridged my modem, and have the credentials from the ISP.
When I put that info into the WAN interface of pfsense, it refuses to connect (or pull an IP on the WAN), and I have no internet. If I default it back to DHCP, it will connect (usually), and works okay, except that any time I lose power or reboot the pfsense box or modem, it loses the IP, and I have to do a song and dance at the console (not the GUI, the actual console), to get it to connect and pull a public IP again.
How can I get it to accept and connect with the PPPoE credentials?
My ISP has given me a user name, password, domain, and VLAN tagging. Of those, only the User and Password seem to be options in pfsense. Is this the issue? Are there just not fields to input all the proper parameters?
Someone please help me out here before I lose the remainder of my hair. ;) -
@elmojo said in DSL PPPoe refuses to accept credentials:
Of those, only the User and Password seem to be options in pfsense.
Install the latest pfSense.
Their is VLAN support :
Basicly, it goes like this :
Your pppoe uses a VLAN. This means you can't use the pppoe setting of the WAN interface, you have to set up a VLAN with the coorrect VLAN number first :
Now, create a pppoe interface that uses that VLAN :
@elmojo said in DSL PPPoe refuses to accept credentials:
How can I get it to accept and connect with the PPPoE credentials?
First thing to to would be : look at the ISP's support pages and other help sources. You are surely not the only one that want to bridge the ISP router, using it as a simple bridge device. Other have already done that, and document their work.
@elmojo said in DSL PPPoe refuses to accept credentials:
it loses the IP, and I have to do a song and dance at the console (not the GUI, the actual console), to get it to connect and pull a public IP again.
What commands do you use to make it work ??
Your talking about your router as a router, and pfsEnse using DHCP, obtaining an IP (RFC 1918) , mask gateway from your router's DHCP server, right ? -
Yup, that^. If your ISP requires a VLAN and your modem isn't tagging it then you must do that in pfSense for PPPoE server to even see your login requests.
A DHCP setup is usually very different to PPPoE so, yes, how are you switching between them.
Steve
-
EDIT: Hallelujah, it works! :) Can someone tell me why NONE of the various videos and guides I've watched/read over the past several weeks have said a THING about setting up a VLAN in pfsense?! Arrgh, so simple. Anyway, it's aliiiive!! Thanks so much!
Wow, thanks for the helpful replies, folks!
You've just told me how much I don't know about all this. :)To address this somewhat out of order...
I have absolutely searched for others doing the same thing using CenturyLink DSL and come up totally dry. My ISP acts like bridging is a foreign concept, and you should never want to use any device but their own. Their documentation is pretty much nonexistent. Also, they've changed hands a couple times in the past few years, and now all their support is offshore, meaning it's basically worthless. I've gone through the chat and phone support multiple times in the past few weeks, and gotten conflicting information about how to bridge, if it's possible, what device to use (had to buy a different modem) and even what my login credentials are. To say it's been an ordeal is a slight understatement.
At this point, I'm pretty much on my own, along with whatever help I can get here.As for the VLAN thing.... I'm lost.
They told me to use 8/35 as my tagging option. How or where would I put that into pfsense?
That doesn't look like a format that it will accept.
If I test this out, and set up the VLAN "on the side", will it kill my internet connection as soon as I assign the WAN interface to it? If so, that's gonna make troubleshooting a bit tricky, since I won't have a way to ask additional Qs.You asked also about what I had to do when I lost the IP.
It's...complicated. lol
I basically have to reboot both my modem and pfsense. Once they're back up, I have to use the console to "assign IP addresses" to the WAN port, tell it to use DHCP, then let it find it. That works about 60% of the time. If it doesn't, I'll reboot and try again. This is why I want to get it fixed, it's a mess. -
So for future Centrylink customers you just has to use VLAN 35?
-
@elmojo said in DSL PPPoe refuses to accept credentials:
I've watched/read over the past several weeks have said a THING about setting up a VLAN in pfsense?!
@stephenw10
Maybe a addendum in the Docs that describe how to get Online with pppoe and vlan would be useful for many people! IMHORegards,
fireodo -
Yes, that's not a bad idea. It is an advanced setting though. It's only a factor here because we are trying to use a bridge mode that is not the ISPs expected connection.
Both my WANs are PPPoE and both actually require a VLAN but the ISP modem does that by default since it is the expected connection method.Steve
-
@stephenw10 said in DSL PPPoe refuses to accept credentials:
So for future Centrylink customers you just has to use VLAN 35?
I guess so! I just plugged everything is exactly as shown in the super awesome mega helpful screenshots above, and it worked instantly.
And yes, a doc addendum about how to get DSL PPPoE working would have saved me literally weeks of headaches and wasted money. I even bought a different modem, since one tech thought my current modem wasn't bridging properly. It turns out it was, they just don't know how their own firmware works. This is the type of "support" I've been dealing with.
I should have started here to begin with. Oh well, now I know.
-
@stephenw10
Yeah, to be clear, I think this whole issue is mostly because my ISP suuuucks. lol
If they had better documentation, or actual support personnel who knew the difference between a modem and a router (I mean this literally), then this probably wouldn't have even come up.
