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

    WAN DCHP issue (2.1)

    General pfSense Questions
    7
    11
    2.3k
    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.
    • A
      atamido
      last edited by

      I recently went from 2.0.1 to 2.1, and have been experiencing issues where the WAN interface will lose its IP.  Or at least an IP is not shown in the dashboard/interface status for the WAN.  In the interface status page I can hit the release button, and then hit renew, and the IP is shown again and internet access seems to work again.

      It doesn't happen every day, but it can happen multiple times per day.  I have one of those crappy U-Verse modems, so it could certainly do strange things.  But there is this in the logs that seems to indicate that after a reconnect that it can't update the IP on the WAN for some reason.  I suspect that I could just set the IP to be static, but I really wanted it to be able to automatically update in case my dynamic IP ever changed.  In these logs, my WAN IP should be 78.18.17.250 and the gateway should be 78.18.17.1.

      50:50 	php: rc.newwanip: pfSense package system has detected an ip change 78.18.17.250 -> 78.18.17.250 ... Restarting packages.
50:48 	php: rc.newwanip: Creating rrd update script
50:48 	php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
50:43 	php: rc.newwanip: ROUTING: setting default route to 78.18.17.1
50:43 	php: rc.newwanip: rc.newwanip: on (IP address: 78.18.17.250) (interface: wan) (real interface: ue0).
50:43 	php: rc.newwanip: rc.newwanip: Informational is starting ue0.
50:41 	check_reload_status: rc.newwanip starting ue0
50:40 	php: /status_interfaces.php: The command '/sbin/ifconfig 'ue0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
50:14 	php: /status_interfaces.php: Successful login for user 'admin' from: 192.168.10.223
50:14 	php: /status_interfaces.php: Successful login for user 'admin' from: 192.168.10.223
32:30 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:29 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:28 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:28 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:18 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:17 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:16 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:16 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:12 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:11 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:10 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:10 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:10 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:09 	php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
32:08 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:07 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:07 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:06 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
32:05 	check_reload_status: Reloading filter
32:05 	check_reload_status: Restarting OpenVPN tunnels/interfaces
32:05 	check_reload_status: Restarting ipsec tunnels
32:05 	check_reload_status: updating dyndns WAN_DHCP
31:58 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:54 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:52 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:49 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:49 	php: rc.interfaces_wan_configure: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output 2> /tmp/ue0_error_output' returned exit code '1', the output was ''
31:49 	php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 'ue0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
31:48 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:48 	check_reload_status: updating dyndns wan
31:46 	check_reload_status: Configuring interface wan
31:46 	php: rc.newwanip: rc.newwanip: Failed to update wan IP, restarting...
31:46 	php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: wan) (real interface: ue0).
31:46 	php: rc.newwanip: rc.newwanip: Informational is starting ue0.
31:45 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:44 	php: rc.linkup: Clearing states to old gateway 78.18.17.1.
31:43 	php: rc.linkup: ROUTING: setting default route to 78.18.17.1
31:43 	check_reload_status: rc.newwanip starting ue0
31:43 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:43 	kernel: arpresolve: can't allocate llinfo for 78.18.17.1
31:43 	php: rc.linkup: The command '/sbin/ifconfig 'ue0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
31:43 	php: rc.linkup: HOTPLUG: Configuring interface wan
31:43 	php: rc.linkup: DEVD Ethernet detached event for wan
31:43 	php: rc.linkup: DEVD Ethernet attached event for wan
31:40 	check_reload_status: Linkup starting ue0
31:40 	kernel: ue0: link state changed to UP
31:40 	kernel: ue0: link state changed to DOWN
31:40 	check_reload_status: Linkup starting ue0
      1 Reply Last reply Reply Quote 0
      • S
        shaqan
        last edited by

        having exactly the same issue. And it is annoying since I have no problems when putting the same WAN cable directly behind PC:(

        Nov 6 14:47:37 	php: rc.start_packages: Restarting/Starting all packages.
Nov 6 14:47:34 	check_reload_status: Reloading filter
Nov 6 14:47:34 	check_reload_status: Starting packages
Nov 6 14:47:34 	php: rc.newwanip: pfSense package system has detected an ip change 195.50.200.xxx -> 195.50.200.xxx ... Restarting packages.
Nov 6 14:47:32 	php: rc.newwanip: Creating rrd update script
Nov 6 14:47:32 	php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
        1 Reply Last reply Reply Quote 0
        • R
          rilles
          last edited by

          I've noticed the same thing with 2.1 with a dual WAN. The default interface seems to lose its ability to renew its IP and goes offline or sometimes goes weird (non-responsive but appears good in the gui).
          Same type of log messages as above. Did not have these issues in 2.0.3

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            I have only noticed this on a test system that had its WAN connected to a switch, and the switch power-cycled quickly (actually we had low/marginal voltage and the switch would go off and come back quickly). It was sometimes reproducible by quickly power-cycling the switch. So I presume that there was some issue processing the interface-up event when the interface-down had not finished processing?
            Release/renew in Status:Interfaces would usually bring it back.
            Do you have potentially flakey devices on the other end of the WAN cable?

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • A
              atamido
              last edited by

              @phil.davis:

              Do you have potentially flakey devices on the other end of the WAN cable?

              I would say yes, it's an AT&T U-verse modem.  The device itself isn't going to win any awards for stability, and AT&T can push an update and reboot the thing whenever.  So it's very possible that the port could go down and back up quickly.

              1 Reply Last reply Reply Quote 0
              • P
                phil.davis
                last edited by

                I would say yes, it's an AT&T U-verse modem.  The device itself isn't going to win any awards for stability, and AT&T can push an update and reboot the thing whenever.  So it's very possible that the port could go down and back up quickly.

                For a test, you can put a switch in the middle between the U-verse and pfSense WAN. Then if the U-verse does something odd on its Ethernet interface signals, it doesn't get propagated to pfSense WAN.

                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                1 Reply Last reply Reply Quote 0
                • S
                  shaqan
                  last edited by

                  @phil.davis:

                  Do you have potentially flakey devices on the other end of the WAN cable?

                  No way to check as the other "end" of my WAN cable is in ISP's sealed metal box. No clue about what's in there, besides the connection being "100/20 fiber" in apartment building and cable length to "mystery box" being roughly 80m. Asked directly what's in there and Tech support was vague. Maybe they had no clue themselves?

                  1 Reply Last reply Reply Quote 0
                  • F
                    firbc
                    last edited by

                    Me to, having the same issue. Anyone found solution?

                    1 Reply Last reply Reply Quote 0
                    • R
                      rjkruit
                      last edited by

                      Same here UPC Netherlands. Once or twice a week I wake up and there's no internet. I'm not sure if it has to do with UPC updating the firmware and/or rebooting the modem remotely but it always seem to happen over night. I think I'll just place an old switch in between so the interface on the pfsense box doesn't go down and see what happens.

                      1 Reply Last reply Reply Quote 0
                      • C
                        cslinuxboy
                        last edited by

                        Same problem here.  The only thing that's changed is my upgrade to pfSense 2.1.  Now my WAN connection drops all the time and is sporadic.  Can't wait for a fix.  May have to resort back to 2.0.

                        Mike

                        1 Reply Last reply Reply Quote 0
                        • C
                          cslinuxboy
                          last edited by

                          So to make sure it's nothing to do with my Arris cable modem, I put a unmanaged switch between my modem and wan pfSense port.  Same problem.  Less than 24 hours my WAN interface drops its IP and fails to renew.  Like previously stated, no issues until I upgraded to 2.1

                          Mike

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post