Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    LAN Interface makes WAN not receive address from ISP

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 626 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      carobell
      last edited by carobell

      I seem to have been faster on the writing then on the searching. Seems to be the same problem then this :
      https://forum.netgate.com/topic/135920/pfsense-2-4-4-fails-all-pppoe-s-after-disabling-one/21

      I find myself in a very weird situation. Last week a tech from our ISP came in to take care of some things and we had to be disconnected for a while. One of the things was configure a static address (I don't see how that would be a problem but we never know).

      Since that disconnection, every time I change something on one of the LAN interface the WAN loses connection with the ISP.

      WAN is connected by PPPoE to the ISP, it receives a static (dynamic before that) IP address.
      LAN is just that, a LAN. I have 3 of these and, for now, only one seems to cause the problems. I have yet to test the other ones as this is in production and the one I habitually make tests with is the one causing trouble.

      To that test interface is connected another PFSense machine (the testing environment router) and since that day, when the ISP tech came, it does not connect to its WAN (the trouble interface) at all. I've tried it with DCHP and static and every time I make a change to the main router, general internet failure everywhere.

      So this is pretty much a two in one:
      Router #1 stops receiving internet from ISP if I play around with the "testing env" interface
      Router #2 does not receive internet from its WAN that is the "testing env" interface

      PFSENSE 2.4.4-RELEASE on Dell PowerEdge R610
      VLAN 35 for the WAN (Cannot change, it's how the ISP works)

      The fastest way to make the WAN work again is to change the LAN network port to another one and then back to what it was.

      Here are some logs when it did not work :

      Dec 17 09:09:44 	ppp 		[wan_link0] Link: reconnection attempt 73 in 4 seconds
      Dec 17 09:09:44 	ppp 		[wan_link0] LCP: Down event
      Dec 17 09:09:44 	ppp 		[wan_link0] Link: DOWN event
      Dec 17 09:09:44 	ppp 		[wan_link0] can't remove hook mpd32348-0 from node "[21e]:": No such file or directory
      Dec 17 09:09:44 	ppp 		[wan_link0] PPPoE: can't connect "[21e]:"->"mpd32348-0" and "[244]:"->"left": No such file or directory
      Dec 17 09:09:44 	ppp 		[wan_link0] Link: reconnection attempt 72
      Dec 17 09:09:41 	ppp 		[wan_link0] Link: reconnection attempt 72 in 3 seconds
      Dec 17 09:09:41 	ppp 		[wan_link0] LCP: Down event
      Dec 17 09:09:41 	ppp 		[wan_link0] Link: DOWN event
      Dec 17 09:09:41 	ppp 		[wan_link0] can't remove hook mpd32348-0 from node "[21e]:": No such file or directory
      Dec 17 09:09:41 	ppp 		[wan_link0] PPPoE: can't connect "[21e]:"->"mpd32348-0" and "[244]:"->"left": No such file or directory
      Dec 17 09:09:41 	ppp 		[wan_link0] Link: reconnection attempt 71
      Dec 17 09:09:40 	ppp 		[wan_link0] Link: reconnection attempt 71 in 1 seconds
      Dec 17 09:09:40 	ppp 		[wan_link0] LCP: Down event
      Dec 17 09:09:40 	ppp 		[wan_link0] Link: DOWN event
      Dec 17 09:09:40 	ppp 		[wan_link0] can't remove hook mpd32348-0 from node "[21e]:": No such file or directory
      Dec 17 09:09:40 	ppp 		[wan_link0] PPPoE: can't connect "[21e]:"->"mpd32348-0" and "[244]:"->"left": No such file or directory
      Dec 17 09:09:40 	ppp 		[wan_link0] Link: reconnection attempt 70
      Dec 17 09:09:38 	ppp 		[wan_link0] Link: reconnection attempt 70 in 2 seconds
      Dec 17 09:09:38 	ppp 		[wan_link0] LCP: Down event
      Dec 17 09:09:38 	ppp 		[wan_link0] Link: DOWN event 
      
      1 Reply Last reply Reply Quote 0
      • N
        netblues
        last edited by

        What version are you running?
        Do you have vlans?

        C 1 Reply Last reply Reply Quote 0
        • C
          carobell @netblues
          last edited by

          @netblues
          I edited OP to add that info, thank you!
          V. 2.4.4-RELEASE
          1 Vlan for the WAN.

          N 1 Reply Last reply Reply Quote 0
          • N
            netblues @carobell
            last edited by

            @carobell Known issue.
            This has been fixed as a patch and will be included next release.
            Please install this patch via system patches.
            https://github.com/pfsense/pfsense/commit/433a8e71f3b68c39634e11b62d8bf3d9e8ec878c.patch

            C 1 Reply Last reply Reply Quote 1
            • C
              carobell @netblues
              last edited by carobell

              @netblues Actually updated to 2.4.4_1 (or 2.4.4p1 as it says in your thread) and it took care of all of it. Thank you for that first reply you made my search 100% more successful :)

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.