PPPoE WAN connection problem
-
Dunno, but Wan interface: DHCP seems pretty obviously incorrect for PPPoE
-
Wan interface: DHCP was before I tried to setup PPPoE.
Now it's Wan interface: PPPoE w/ username and password
Lan: 192.168.1.51
D link: bridge mode ONLY w/out any router function. -
Jul 25 21:02:44 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:46 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:49 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:53 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:56 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
I think PPPoE is trying to tell you something: probably it doesn't know what network interface to use. Did you specify a link interface when you created the PPPoE interface?
-
Jul 25 21:02:44 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:46 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:49 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:53 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
Jul 25 21:02:56 ppp: [wan_link0] PPPoE: Skipping link "wan_link0" with undefined interface
I think PPPoE is trying to tell you something: probably it doesn't know what network interface to use. Did you specify a link interface when you created the PPPoE interface?
Yes, I setup the Wan interface to use pppoe instead of DHCP as it was before…
-
Yes, I setup the Wan interface to use pppoe instead of DHCP as it was before…
Is it working properly now?
-
No it isn't, that's why I'm asking 4 your help :(
-
OK, please post a screenshot of Interfaces -> (assign), PPPs tab.
-
In your first post the D-Link modem/router appears to be in the wrong place. The pfSense LAN interface is in the same network segment as the D-Link LAN. ???
I would expect some thing more like:
Internet –- D-Link modem --- pfSense --- Client PCs
Steve
-
Yes, the setup is what you wrote, sorry about that.
The screenshot is attached.
BTW, now the LAN IP adress is in another subnet (192.168.2.xxx).
Thanks again guys!
-
I assume em0 is the correct NIC for the WAN connection?
Usually when you change your WAN type to PPPoE from DHCP you would loose your interface at 192.168.1.51. Is that happening?
What does Status: Interfaces: look like?
Steve
-
Yes, em0 is my WAN card let's say. Em1 is LAN.
When I get from DHCP to PPPoE on the bootup pfSense says: WAN –---------------- NONE (PPPoE)
LAN ------------------- 192.168.2.100That's the screen of the interfaces :
WAN now it's on DHCP so I can surf the net.
-
Hmm, weird. There are a few similar reports of this happening after upgrading from earlier pfSense versions, the config not translating correctly, but you have gone straight to 2.0.3. :-\
Maybe time to look at the config file directly to check the PPPoE binding to em0 is really there.
Steve
-
Have you restarted pfSense AFTER changing the WAN to PPPoE?
In pfSense configuration files for various services (including PPPoE) are generated at startup (and possibly other times as well) from the configuration file maintained by the GUI interface. PERHAPS the PPP configuration file wasn't regenerated before PPP started.I suggest you take these steps in the following order:
1. Set modem into bridge mode.
2. Set pfSense WAN interface to pppoe0 (in Interfaces -> (assign) page)
3. Check the details are correct on the Interfaces -> WAN page
4. Shutdown modem
5. Shutdown pfSense
6. Start modem
7. Start pfSenseIf you then see the same report in the PPP log (check the time stamps on the entries to ensure you are not looking on stale reports) then please post the contents of the PPP configuration file (/var/etc/mpd_wan.conf) after masking out the authentication details.
