5. WAN ppoe can't connect when physical interface already used by opt interface

WAN ppoe can't connect when physical interface already used by opt interface

  • R

    On :
    2.0-BETA4 (i386) built on Tue Dec 21 12:44:54 EST 2010
    My setup is like this:

    Internet –- DSL router --- (pppoe connection) ---- PFSENSE

    So my pf box do a pppoe connection instead of my dsl router. Unfortunatly, my dsl router seems to try to do some ping on my wan interface em0 as you can see below:

    Act     Time                    If       Source          Destination   Proto

    Block   Dec 22 20:30:00    em0   192.168.2.1    224.0.0.1     IGMP

    I have finally decided since I do not care about the traffix to use easy rule to block icmp request from the dsl router to my wan interface.
    As soon as I click on the add rule button, I have this error message:

    Status : EasyRule

    This is the Easy Rule status page, mainly used to display errors when adding rules. If you are seeing this, there apparently was not an error, and you navigated to the page directly without telling it what to do.

    This page is meant to be called from the block/pass buttons on the Firewall Logs page, Status > System Logs, Firewall Tab.

    But no error message is displayed or rule added.

    Any ideas?

    Thanks

    0
  • Rebel Alliance Developer Netgate

    You are probably using pppoe, so you do not have em0 assigned. Since em0 is not assigned, it's not a valid interface for rules.

    If you assign em0 as an opt interface, then you can add rules to it. It is safe to do that on 2.0 since pppoe actually makes its own separate interface, pppoe0, which is assigned as WAN. You can give the newly assigned OPT interface an IP in your modem's subnet (192.168.2.x) or set it to dhcp.

    0
  • R

    Hi,
    You are right on the spot as always :-)
    I was thinking about such a thing during the last days of Christime time.
    My dsl router gives dhcp addresses by default but I use a ppoe connection in pfsense instead of using the addresses from the router since I do not know how is really configured the dsl router. Anyway, I juste like the idea of the dsl router still gives dhcp addresses because if the pf box dies one day, at least I can quickly connect to the dsl router without too much configuration to have an access to the internet.

    I have created an opt interface assigned to em0 (the port connected to the router). Since I did that and at every reboot, the wan interface is down until I go the the ppp interface configuration, choose my pppoe connection, then reselect the link interface (em0) and save. Then the link is up. For an unknow reason, the pppoe interface does not seem to share nicely its interface with another interface.

    If you have any idea why, it will be greatly appreciated.

    Thinking about my post, I want to apology for my lasyness. Sometimes, it's more easy to post something and wait for a fix (from you guys that have much important things to do on Pfsense than reply to obscure questions) than try to investigate by yourself.
    So for 2011, I will try to post question but also some fix if I found some or some runbook or any how to that could help you or other users.

    Thanks again guys.

    0
  • Rebel Alliance Developer Netgate

    If you change that em0 interface to be static instead of DHCP, it may work. Just use the IP it gives you as the static IP and it should work.

    The router may be seeing that DHCP and think that you want it to sign on with PPPoE instead of the pfSense router. Give that a shot and see if it works.

    0
  • R

    Hi,
    I have given a static ip on my interface (called DSL) linked to the em0 interface.
    But after a reboot my wan interface is still down until I re select the em0 interface in the pppoe connection.

    If you have other ideas… I will test more soon.
    Thanks

    0
  • R

    Same thing with 2.0-BETA5 (i386) built on Wed Dec 29 05:36:23 EST 2010.

    Systen logs:

    php: : Could not find gateway for interface(wan).

    ppp logs:

    Dec 29 12:05:39 ppp: [wan_link0] Link: reconnection attempt 27 in 4 seconds
    Dec 29 12:05:39 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:39 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:39 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:39 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:39 ppp: [wan_link0] Link: reconnection attempt 26
    Dec 29 12:05:35 ppp: [wan_link0] Link: reconnection attempt 26 in 4 seconds
    Dec 29 12:05:35 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:35 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:35 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:35 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:35 ppp: [wan_link0] Link: reconnection attempt 25
    Dec 29 12:05:31 ppp: [wan_link0] Link: reconnection attempt 25 in 4 seconds
    Dec 29 12:05:31 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:31 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:31 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:31 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:31 ppp: [wan_link0] Link: reconnection attempt 24
    Dec 29 12:05:30 ppp: [wan_link0] Link: reconnection attempt 24 in 1 seconds
    Dec 29 12:05:30 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:30 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:30 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:30 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:30 ppp: [wan_link0] Link: reconnection attempt 23
    Dec 29 12:05:26 ppp: [wan_link0] Link: reconnection attempt 23 in 4 seconds
    Dec 29 12:05:26 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:26 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:26 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:26 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:26 ppp: [wan_link0] Link: reconnection attempt 22
    Dec 29 12:05:22 ppp: [wan_link0] Link: reconnection attempt 22 in 4 seconds
    Dec 29 12:05:22 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:22 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:22 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:22 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:22 ppp: [wan_link0] Link: reconnection attempt 21
    Dec 29 12:05:21 ppp: [wan_link0] Link: reconnection attempt 21 in 1 seconds
    Dec 29 12:05:21 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:21 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:21 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:21 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:21 ppp: [wan_link0] Link: reconnection attempt 20
    Dec 29 12:05:20 ppp: [wan_link0] Link: reconnection attempt 20 in 1 seconds
    Dec 29 12:05:20 ppp: [wan_link0] LCP: Down event
    Dec 29 12:05:20 ppp: [wan_link0] Link: DOWN event
    Dec 29 12:05:20 ppp: [wan_link0] can't remove hook mpd8030-0 from node "[14]:": No such file or directory
    Dec 29 12:05:20 ppp: [wan_link0] PPPoE: can't connect "[14]:"->"mpd8030-0" and "[12]:"->"left": No such file or directory
    Dec 29 12:05:20 ppp: [wan_link0] Link: reconnection attempt 19
    Dec 29 12:05:16 ppp: [wan_link0] Link: reconnection attempt 19 in 4 seconds
    Dec 29 12:05:16 ppp: [wan_link0] LCP: Down event

    After I manually reselect interface em0 for pppoe interface:

    Dec 29 12:06:55 ppp: [wan] IFACE: Up event
    Dec 29 12:06:54 ppp: [wan] 70.51.19.89 -> 64.230.197.76
    Dec 29 12:06:54 ppp: [wan] IPCP: LayerUp
    Dec 29 12:06:54 ppp: [wan] IPCP: state change Ack-Rcvd –> Opened
    Dec 29 12:06:54 ppp: [wan] IPADDR 64.230.197.76
    Dec 29 12:06:54 ppp: [wan] IPCP: SendConfigAck #72
    Dec 29 12:06:54 ppp: [wan] 64.230.197.76 is OK
    Dec 29 12:06:54 ppp: [wan] IPADDR 64.230.197.76
    Dec 29 12:06:54 ppp: [wan] IPCP: rec'd Configure Request #72 (Ack-Rcvd)
    Dec 29 12:06:54 ppp: [wan] IPCP: state change Req-Sent –> Ack-Rcvd
    Dec 29 12:06:54 ppp: [wan] SECDNS 207.164.234.193
    Dec 29 12:06:54 ppp: [wan] PRIDNS 207.164.234.129
    Dec 29 12:06:54 ppp: [wan] IPADDR 70.51.19.89
    Dec 29 12:06:54 ppp: [wan] IPCP: rec'd Configure Ack #3 (Req-Sent)
    Dec 29 12:06:54 ppp: [wan] SECDNS 207.164.234.193
    Dec 29 12:06:54 ppp: [wan] PRIDNS 207.164.234.129
    Dec 29 12:06:54 ppp: [wan] IPADDR 70.51.19.89
    Dec 29 12:06:54 ppp: [wan] IPCP: SendConfigReq #3
    Dec 29 12:06:54 ppp: [wan] SECDNS 207.164.234.193
    Dec 29 12:06:54 ppp: [wan] PRIDNS 207.164.234.129
    Dec 29 12:06:54 ppp: [wan] 70.51.19.89 is OK
    Dec 29 12:06:54 ppp: [wan] IPADDR 70.51.19.89
    Dec 29 12:06:54 ppp: [wan] IPCP: rec'd Configure Nak #2 (Req-Sent)
    Dec 29 12:06:54 ppp: [wan] SECDNS 0.0.0.0
    Dec 29 12:06:54 ppp: [wan] PRIDNS 0.0.0.0
    Dec 29 12:06:54 ppp: [wan] IPADDR 0.0.0.0
    Dec 29 12:06:54 ppp: [wan] IPCP: SendConfigReq #2
    Dec 29 12:06:54 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Dec 29 12:06:54 ppp: [wan] IPCP: rec'd Configure Reject #1 (Req-Sent)
    Dec 29 12:06:54 ppp: [wan] SECDNS 0.0.0.0
    Dec 29 12:06:54 ppp: [wan] PRIDNS 0.0.0.0
    Dec 29 12:06:54 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Dec 29 12:06:54 ppp: [wan] IPADDR 0.0.0.0
    Dec 29 12:06:54 ppp: [wan] IPCP: SendConfigReq #1
    Dec 29 12:06:54 ppp: [wan] IPCP: state change Starting –> Req-Sent
    Dec 29 12:06:54 ppp: [wan] IPCP: Up event
    Dec 29 12:06:54 ppp: [wan] IPCP: LayerStart
    Dec 29 12:06:54 ppp: [wan] IPCP: state change Initial –> Starting
    Dec 29 12:06:54 ppp: [wan] IPCP: Open event
    Dec 29 12:06:54 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
    Dec 29 12:06:54 ppp: [wan_link0] Link: Join bundle "wan"
    Dec 29 12:06:54 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
    Dec 29 12:06:54 ppp: [wan_link0] LCP: authorization successful
    Dec 29 12:06:54 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
    Dec 29 12:06:54 ppp: [wan_link0] LCP: LayerUp
    Dec 29 12:06:54 ppp: [wan_link0] PAP: sending REQUEST #1 len: 22
    Dec 29 12:06:54 ppp: [wan_link0] PAP: using authname "b1dihr88"
    Dec 29 12:06:54 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
    Dec 29 12:06:54 ppp: [wan_link0] LCP: state change Ack-Sent –> Opened
    Dec 29 12:06:54 ppp: [wan_link0] MAGICNUM 4edb46ab

    Strange thing is when the system starts up I can see on the console that the pppoe connection is started without any issue but the final status is still NONE util the manual reselection of the wan interface em0 in the pppoe connection settings.

    0
  • R

    Problem still there with 2.0-BETA5 (i386) built on Thu Dec 30 02:29:44 EST 2010.

    Maybe the problem is because pppoe connection is shutdown because DSL interface (the interface connected to em0 using ip addresses from the dhcp pool on the dsl router) is gringing up after pppoe connection?

    Also the pppoe connection seems always to loose its interface. Even if I check the setting in the pppoe connection and see that em0 is selected, if I it save an an error message says that I have to select an interface so I have to re select em0.

    Please note that the other settings for pppoe connection:

    • Enable Dial-on-Demand mode : on
    • Idle Timeout : 0

    For the Idle Timeout seeting, there is also a bug: it always displays nothing even after I put 0 in the field.

    Thanks

    0
  • R

    I have renamed the topic seems that the issue is more on the interfaces themselves than on the easy rule issue.
    Romain

    0
  • Rebel Alliance Developer Netgate

    Actually you may be hitting a general PPPoE problem as discussed here: http://forum.pfsense.org/index.php/topic,31247.0.html

    0
  • R

    Seems to be fixed with : 2.0-BETA5 (i386) built on Thu Dec 30 11:06:13 EST 2010
    Ye!
    Thanks again

    0
  • R

    Arg… problem seems back again with:

    2.0-BETA5 (i386) built on Thu Dec 30 20:41:42 EST 2010.

    That's very strnage because the upgrade to the release before this one have fixed my issue (meaning that after a reboot, my pppoe link was up)

    Romain

    0
Locked
 

Products

Applications

Support

Services

News

Resources

Company

Our Mission

As host of the pfSense open source firewall project, Netgate believes in enhancing network connectivity that maintains both security and privacy. We also believe everyone should be able to afford it.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© Copyright 2002 - 2019 Rubicon Communications, LLC | Privacy Policy