Adding IPv4 address to pppoe0 failed
-
Hello guys, this is my first post here and I've been experimenting with PfSense for a few weeks. Until I set the WAN to DHCP everything goes smoothly but as soon as I try to make a PPPoe connection to my ISP unfortunately a series of problems arise and obviously I can't surf.
I didn't do any special configuration. I just setup the WAN with
IPV4 configuration type PPPoe
IPV6 none
username, passwordChecking the logs it seems that the authorization is granted and a public ip released...then pfSense tries to "assign" the ip to the first address on the LAN and everything gets compromised. The thing goes on like this indefinitely.
Thank you for any suggestion :)
P.S.
PfSense is positioned behind a classic modem/router provided by the ISP. Another small report...on the same machine, OpenWRT works perfectly without doing anything in particular.
I leave a part of the PPP connection log:
...
Dec 16 09:13:15 ppp 43007 [wan_link0] LCP: auth: peer wants PAP, I want nothing
Dec 16 09:13:15 ppp 43007 [wan_link0] PAP: using authname "XXXXXXXXX"
Dec 16 09:13:15 ppp 43007 [wan_link0] PAP: sending REQUEST #1 len: 23
Dec 16 09:13:15 ppp 43007 [wan_link0] LCP: LayerUp
Dec 16 09:13:15 ppp 43007 [wan_link0] PAP: rec'd ACK #1 len: 5
Dec 16 09:13:15 ppp 43007 [wan_link0] LCP: authorization successful
...
Dec 16 09:13:15 ppp 43007 [wan] IPADDR 95.xxx.xx.xxx
Dec 16 09:13:15 ppp 43007 [wan] 95.xxx.xx.xxx is OK
Dec 16 09:13:15 ppp 43007 [wan] IPCP: SendConfigReq #3
Dec 16 09:13:15 ppp 43007 [wan] IPADDR 95.xxx.xx.xxx
Dec 16 09:13:15 ppp 43007 [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Dec 16 09:13:15 ppp 43007 [wan] IPADDR 95.xxx.xx.xxx
Dec 16 09:13:15 ppp 43007 [wan] IPCP: state change Ack-Sent --> Opened
Dec 16 09:13:15 ppp 43007 [wan] IPCP: LayerUp
Dec 16 09:13:15 ppp 43007 [wan] 95.xxx.xx.xxx -> 192.168.100.1
Dec 16 09:13:15 ppp 43007 [wan] IFACE: Adding IPv4 address to pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): File exists
... -
@tom_anastasio You wouldn't use PPPOE if the ISP router is connected to the WAN interface unless its set to modem mode.
Dec 16 09:13:15 ppp 43007 [wan] 95.xxx.xx.xxx -> 192.168.100.1 << would lead me to to say the modem/router is still in router mode.
-
@nogbadthebad Thanks a lot for the reply. At the moment I haven't done anything in particular on the modem/router also because I don't think there is any option about it. Anyway 192.168.100.1 is not the ip of the router but the ip of the pfSense LAN...
-
The ISP device must be configured at least mostly correctly since you're seeing PPPoE responses from the upstream server.
@tom_anastasio said in Adding IPv4 address to pppoe0 failed:
Dec 16 09:13:15 ppp 43007 [wan] 95.xxx.xx.xxx -> 192.168.100.1
This indicates a PPP link between your public IP at 95.x.x.x and the gateway at 192.168.100.1.
It's common to see the ISP use a private IP for the gateway there and that's fine. However if that s conflicting with your LAN subnet that's a problem.Steve
-
@stephenw10 Many thanks for the reply. I think that's the point. In the routing section of pfSense I see an automatically created row where the gateway entry is set to dynamic and cannot be changed. Who chooses and on what basis is the gateway set up? Thanks to your answer it makes me think that the modem/router is still working as a "router" and not fully in bridge mode.
-
@tom_anastasio I think what stephen meant is: try another IP-range for your LAN, don't use 192.168.100.1 but 192.168.5.1 for example.
-
@bob-dig Uhm...I'll try, although I think that even if I have to use something else, pfSense will use it as a gateway :) Thanku so much!
-
The ISP chooses the client IP and the gateway IP. That's all defined by the PPPoE server at their end. The clients just asks it for values and that's what it's being passed.
Yes, choose a different LAN subnet so it doesn't conflict with your ISPs gateway IP.
Steve
-
Hi @stephenw10 , thank you so much for your support and sorry for the delay. Finally it works :)
1 - I fixed the ISP model/router by disabling everything I could.
2 - I changed the LAN IP
The famous 192.168.100.1 was assigned and I only had to change the "Monitor IP" in the gateway because it recorded 100% of the lost packets. I assigned it to the LAN IP, I don't know if it's correct, but it works...
Moral of the story...I need to learn more about the PPPoE protocol :)
Thank you all!
P.S.
In relation to the firewall ... do I have to create some particular rule or is its default behavior already fine?
-
@tom_anastasio said in Adding IPv4 address to pppoe0 failed:
Moral of the story...I need to learn more about the PPPoE protocol :)
You wouldn't normally need to if your ISP handed out a routable Internet address or a CGNAT address, it would just work
Handing out a 192.168.x.x address is just asking for trouble.
-
The ISP is handing the gateway as a private IP and that's common for a PPPoE link and not normally an issue. I have that here. But, yeah, using a 192.168.x.x address is far more likely to conflict.
However, exactly as I also see, that gateway does not respond to ping. You should set the monitor IP to something further upstream like 8.8.8.8 so you get real monitoring data for the link.Steve
