Trouble with Bell PPPoE
-
@stephenw10 I just made sure it was set to WAN and did not change anything else. Any/Any for Address/Protocol. Nothing else set. I verified with the ISP that the PPPoE login was correct and they tested it ok.
-
So literally 0 packets on vmx0? I would expect to see something there even if it wasn't trying to connect over PPPoE.
-
@stephenw10 So would I. The fact that this happens on a VM and on a physical server is very weird. The Packet Capture interface selector only shows WAN, LAN & localhost but not VLAN35. I assume this is normal? Regardless I would still expect to see some kind of traffic on the WAN. I don't really understand the internals of PPPoE. Does it use an APIPA address to talk to the headend to get its IP address, gateway, mask etc? If you have 5 minutes, I would be interested to see if this behaviour happens for you as well:
- Create vlan 35, prio 0
- Assign WAN to the vlan
- Set WAN for PPPoE
- Fill in some bogus creds
- Do a pcap and see if you get traffic
-
Ah, yeah you need to assign/enable vmx0 as an interface to pcap from it in the gui.
You can do it from the command line though.
PPPoE is not IP in the initial connection. You should still see packets though.
Steve
-
@stephenw10 Finally got it figured out.
-
When pfSense has gateway set to automatic, I still needed to force it to use the PPoE gateway even though it's the only gateway.
-
When your ISP tells you need to pass the traffic via vlan 35 on WAN, they're lying. No vlan configuration required.
-
When you ask your ISP to validate the credentials, check twice. First guy gave them to us initially, second guy said they were fine when I called to confirm them, I called again to validate and the third guy said the first letter is supposed to be a capital so I had the wrong creds the whole time.
Two days of my life wasted getting this working.
-
-
Urgh. Well glad you got up and running.
It's not unusual to see the PPPoE "modem" doing the VLAN tagging. That's exactly how my own WAN in setup here.
Steve
-
@stephenw10 I suspect that the modem is doing the vlan transparently so I just needed to configure the PPPoE login. Their support people didn't know that and were advising me to use vlan 35. Others also using Bell mentioned vlan 35, but I now know that's only in the context of connecting directly to the ONT via SPF with the modem totally out of the loop.
One pfSense glitch I noticed was that when I had Dial on Demand enabled (part of my patented Try Anything Panic-Mode Troubleshooting), you have to fill in an idle time. When every time you revisit that page thereafter, the idle time is blank and you can't save the page until you enter it again.
-
Hmm, I can't replicate that. In 22.05?
-
@stephenw10 No, 2.6.0
-
Mmm, can't replicate it there either.
When we see things like that it's almost always a browser plugin or auto-fill entering or removing values. Do you see it across different browsers?Steve
-
@stephenw10 Don't worry about it. It was Firefox with an adblocker but I hadn't seen that behaviour before with any other pfSense field. I'm not touching the pppoe config now that it's working.
