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

    [solved] New errors with WAN (sk0) with upgrade to 2.2.2

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    19 Posts 3 Posters 3.6k 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.
    • S
      stefanfa
      last edited by

      Also from what i can tell the number of times it taked the interface up/down and restarts the services seems to increase by 1 each time it does it.

      My DHCP lease is 2 hours and these events seem to on the DHCP expiration or just before.

      Either something is really off with my setup (even though i did a clean 2.2.2 install) or there is some bug in 2.2.2 that involves dhcpclient or renewing lease / wan scripts or such.

      Last time it brought the interface up and down 4 times and got all the errors 4 times aswell. 3 times the time before that.

      So this will be interesting.

      Will probably try a 2.2.1 reinstall tomorrow and expecting downtime during the night tonight just like last night due to these errors.

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

        Nah i had the same errors on 2.2.1 aswell.

        1 Reply Last reply Reply Quote 0
        • T
          TieT
          last edited by

          Have you checked this post ?
          Also check your cables before diving in the deep  ;)

          https://forum.pfsense.org/index.php?topic=88068.0

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

            Cables are checked and yes I have checked that post =)

            This however is not an upgrade problem like i first thought.

            It's very annoying though.

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

              Could someone explain to me what is actually happening here ?

              This seems to be the trigger:

              Apr 20 14:11:26 check_reload_status: Linkup starting sk0
              Apr 20 14:11:26 kernel: sk0: link state changed to DOWN
              Apr 20 14:11:26 kernel: sk0: link state changed to UP

              What actually triggers "check_reload_status: Linkup starting sk0" to begin with ?

              Gateway monitoring ? physical disconnection of the interface ?

              Thanks.

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

                @stefanfa:

                This seems to be the trigger:

                Apr 20 14:11:26 check_reload_status: Linkup starting sk0
                Apr 20 14:11:26 kernel: sk0: link state changed to DOWN
                Apr 20 14:11:26 kernel: sk0: link state changed to UP

                What actually triggers "check_reload_status: Linkup starting sk0" to begin with ?

                Loss of Ethernet link on the interface. Most often because of a cabling or hardware issue with the NIC or what it's plugged into, or occasionally driver issues, though that's usually much more unusual I wouldn't discount it as quickly with sk NICs. Though nothing in that driver changed from pre-2.2.0 release through 2.2.2.

                1 Reply Last reply Reply Quote 0
                • T
                  TieT
                  last edited by

                  Loss of Ethernet link on the interface. Most often because of a cabling or hardware issue with the NIC or what it's plugged into, or occasionally driver issues

                  Yep,

                  Do you have more of the log , in most cases there is an issue before the link going down, check gateway monitoring and again the cables and ports  ;)

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

                    This is a few lines from my system.log

                    Apr 21 09:17:19 pfSense check_reload_status: Starting packages
                    Apr 21 09:17:19 pfSense snmpd[28038]: disk_OS_get_disks: adding device 'ada0' to device list
                    Apr 21 09:17:20 pfSense php-fpm[93007]: /rc.start_packages: Restarting/Starting all packages.
                    Apr 21 09:34:54 pfSense check_reload_status: Linkup starting sk0
                    Apr 21 09:34:54 pfSense kernel: sk0: link state changed to DOWN
                    Apr 21 09:34:54 pfSense kernel: sk0: link state changed to UP
                    Apr 21 09:34:54 pfSense check_reload_status: Linkup starting sk0
                    Apr 21 09:34:55 pfSense php-fpm[45856]: /rc.linkup: DEVD Ethernet detached event for wan
                    Apr 21 09:34:56 pfSense php-fpm[53984]: /rc.linkup: DEVD Ethernet attached event for wan
                    Apr 21 09:34:56 pfSense php-fpm[53984]: /rc.linkup: HOTPLUG: Configuring interface wan
                    Apr 21 09:34:56 pfSense check_reload_status: rc.newwanip starting sk0

                    Normally it starts with "check_reload_status: Linkup starting sk0" and then it brings the interface down and up again.
                    Sometimes it's just once and sometimes it can repeat itself during the next couple of seconds. up to 4-5 times sometimes.

                    Should i check some other log for errors ?

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

                      Replaced old ethernet cable with a brand new one now just to verify it's not the cable.

                      Will report back the result.

                      1 Reply Last reply Reply Quote 0
                      • T
                        TieT
                        last edited by

                        @stefanfa:

                        This is a few lines from my system.log

                        Apr 21 09:17:19 pfSense check_reload_status: Starting packages
                        Apr 21 09:17:19 pfSense snmpd[28038]: disk_OS_get_disks: adding device 'ada0' to device list
                        Apr 21 09:17:20 pfSense php-fpm[93007]: /rc.start_packages: Restarting/Starting all packages.
                        Apr 21 09:34:54 pfSense check_reload_status: Linkup starting sk0
                        Apr 21 09:34:54 pfSense kernel: sk0: link state changed to DOWN
                        Apr 21 09:34:54 pfSense kernel: sk0: link state changed to UP
                        Apr 21 09:34:54 pfSense check_reload_status: Linkup starting sk0
                        Apr 21 09:34:55 pfSense php-fpm[45856]: /rc.linkup: DEVD Ethernet detached event for wan
                        Apr 21 09:34:56 pfSense php-fpm[53984]: /rc.linkup: DEVD Ethernet attached event for wan
                        Apr 21 09:34:56 pfSense php-fpm[53984]: /rc.linkup: HOTPLUG: Configuring interface wan
                        Apr 21 09:34:56 pfSense check_reload_status: rc.newwanip starting sk0

                        Normally it starts with "check_reload_status: Linkup starting sk0" and then it brings the interface down and up again.
                        Sometimes it's just once and sometimes it can repeat itself during the next couple of seconds. up to 4-5 times sometimes.

                        Should i check some other log for errors ?

                        Stefan,

                        Yes post more lines of the system log (200) and also gateway log and dhcp log

                        P.S. i had a similar problem, cable seemed good in the tester, but when bending it a little in a certain way, there was a breach…

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

                          Still getting this problem even with a new cable.

                          Here's exactly what's happening in the logs at the time (the other entries in the logs aren't relevant and is atleast 30 minutes before the incident so didn't include them)

                          
system.log:
Apr 21 17:33:33 pfSense check_reload_status: Linkup starting sk0
Apr 21 17:33:33 pfSense kernel: sk0: link state changed to DOWN
Apr 21 17:33:33 pfSense kernel: sk0: link state changed to UP
Apr 21 17:33:33 pfSense check_reload_status: Linkup starting sk0
Apr 21 17:33:34 pfSense php-fpm[33475]: /rc.linkup: DEVD Ethernet detached event for wan
Apr 21 17:33:35 pfSense php-fpm[41031]: /rc.linkup: DEVD Ethernet attached event for wan
Apr 21 17:33:35 pfSense kernel: arpresolve: can't allocate llinfo for 80.245.x.x on sk0
Apr 21 17:33:35 pfSense kernel: arpresolve: can't allocate llinfo for 80.245.x.x on sk0
Apr 21 17:33:35 pfSense php-fpm[41031]: /rc.linkup: HOTPLUG: Configuring interface wan
Apr 21 17:33:35 pfSense check_reload_status: rc.newwanip starting sk0
Apr 21 17:33:35 pfSense php-fpm[41031]: /rc.linkup: ROUTING: setting default route to 80.245.x.x
Apr 21 17:33:35 pfSense check_reload_status: Restarting ipsec tunnels
Apr 21 17:33:36 pfSense php-fpm[33475]: /rc.newwanip: rc.newwanip: Info: starting on sk0.
Apr 21 17:33:36 pfSense php-fpm[33475]: /rc.newwanip: rc.newwanip: on (IP address: 80.245.x.x) (interface: WAN[wan]) (real interface: sk0).
Apr 21 17:33:36 pfSense php-fpm[33475]: /rc.newwanip: ROUTING: setting default route to 80.245.x.x
Apr 21 17:33:37 pfSense php-fpm[33475]: /rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1429630417] unbound[57772:0]
error: bind: address already in use [1429630417] unbound[57772:0] fatal error: could not open ports'
Apr 21 17:33:37 pfSense php-fpm[41031]: /rc.linkup: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em0' returned exi
t code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.6 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/soft
ware/dhcp/ Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 4 leases to leases file. Listening on BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24 Send
ing on   BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp
 or bootp in /etc/inetd.conf.   Also make sure you are not running HP JetAdmin software, which includes a bootp server.  If you did not get this software from ftp.isc.org, please get the late
st from ftp.isc.org and install that before requesting help.  If you did
Apr 21 17:33:37 pfSense check_reload_status: updating dyndns wan
Apr 21 17:33:38 pfSense php-fpm[33475]: /rc.newwanip: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em0' returned e
xit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.6 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/so
ftware/dhcp/ Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 4 leases to leases file. Listening on BPF/em0/b4:b5:2f:b4:xx:x/192.168.10.0/24 Se
nding on   BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dh
cp or bootp in /etc/inetd.conf.   Also make sure you are not running HP JetAdmin software, which includes a bootp server.  If you did not get this software from ftp.isc.org, please get the la
test from ftp.isc.org and install that before requesting help.  If you di
Apr 21 17:33:38 pfSense php-fpm[33475]: /rc.newwanip: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Apr 21 17:33:38 pfSense php-fpm[56955]: /rc.dyndns.update: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Apr 21 17:33:39 pfSense php-fpm[33475]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Apr 21 17:33:39 pfSense php-fpm[33475]: /rc.newwanip: Creating rrd update script
Apr 21 17:33:41 pfSense php-fpm[33475]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 80.245.xx.xx ->  80.245.xx.xx - Restarting packages.
Apr 21 17:33:41 pfSense check_reload_status: Starting packages
Apr 21 17:33:41 pfSense snmpd[80541]: disk_OS_get_disks: adding device 'ada0' to device list
Apr 21 17:33:42 pfSense php-fpm[63488]: /rc.start_packages: Restarting/Starting all packages.

 `gateways.log:
Apr 21 17:33:36 pfSense apinger: SIGHUP received, reloading configuration.` 

 `dhcpd.log
Apr 21 17:33:34 pfSense dhclient[3367]: connection closed
Apr 21 17:33:34 pfSense dhclient[3367]: exiting.
Apr 21 17:33:35 pfSense dhclient: PREINIT
Apr 21 17:33:35 pfSense dhclient[41779]: DHCPREQUEST on sk0 to 255.255.255.255 port 67
Apr 21 17:33:35 pfSense dhclient[41779]: DHCPACK from 80.245.xx.xx
Apr 21 17:33:35 pfSense dhclient: REBOOT
Apr 21 17:33:35 pfSense dhclient: Starting add_new_address()
Apr 21 17:33:35 pfSense dhclient: ifconfig sk0 inet 80.245.xx.xx netmask 255.255.255.0 broadcast 80.245.xx.xx
Apr 21 17:33:35 pfSense dhclient: New IP Address (sk0): 80.245.xx.xx
Apr 21 17:33:35 pfSense dhclient: New Subnet Mask (sk0): 255.255.255.0
Apr 21 17:33:35 pfSense dhclient: New Broadcast Address (sk0): 80.245.xx.xx
Apr 21 17:33:35 pfSense dhclient: New Routers (sk0): 80.245.xx.xx
Apr 21 17:33:35 pfSense dhclient: Adding new routes to interface: sk0
Apr 21 17:33:35 pfSense dhclient: /sbin/route add default 80.245.xx.xx
Apr 21 17:33:35 pfSense dhclient: Creating resolv.conf
Apr 21 17:33:35 pfSense dhclient[41779]: bound to 80.245.xx.xx -- renewal in 7200 seconds.
Apr 21 17:33:37 pfSense dhcpd: Internet Systems Consortium DHCP Server 4.2.6
Apr 21 17:33:37 pfSense dhcpd: Copyright 2004-2014 Internet Systems Consortium.
Apr 21 17:33:37 pfSense dhcpd: All rights reserved.
Apr 21 17:33:37 pfSense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Apr 21 17:33:37 pfSense dhcpd: Internet Systems Consortium DHCP Server 4.2.6
Apr 21 17:33:37 pfSense dhcpd: Copyright 2004-2014 Internet Systems Consortium.
Apr 21 17:33:37 pfSense dhcpd: All rights reserved.
Apr 21 17:33:37 pfSense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Apr 21 17:33:37 pfSense dhcpd: Wrote 0 deleted host decls to leases file.
Apr 21 17:33:37 pfSense dhcpd: Wrote 0 new dynamic host decls to leases file.
Apr 21 17:33:37 pfSense dhcpd: Wrote 4 leases to leases file.
Apr 21 17:33:37 pfSense dhcpd: Listening on BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24
Apr 21 17:33:37 pfSense dhcpd: Sending on   BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24
Apr 21 17:33:37 pfSense dhcpd: Can't bind to dhcp address: Address already in use
Apr 21 17:33:37 pfSense dhcpd: Please make sure there is no other dhcp server
Apr 21 17:33:37 pfSense dhcpd: running and that there's no entry for dhcp or
Apr 21 17:33:37 pfSense dhcpd: bootp in /etc/inetd.conf.   Also make sure you
Apr 21 17:33:37 pfSense dhcpd: are not running HP JetAdmin software, which
Apr 21 17:33:37 pfSense dhcpd: includes a bootp server.
Apr 21 17:33:37 pfSense dhcpd:
Apr 21 17:33:37 pfSense dhcpd: If you did not get this software from ftp.isc.org, please
Apr 21 17:33:37 pfSense dhcpd: get the latest from ftp.isc.org and install that before
Apr 21 17:33:37 pfSense dhcpd: requesting help.
Apr 21 17:33:37 pfSense dhcpd:
Apr 21 17:33:37 pfSense dhcpd: If you did get this software from ftp.isc.org and have not
Apr 21 17:33:37 pfSense dhcpd: yet read the README, please read it before requesting help.
Apr 21 17:33:37 pfSense dhcpd: If you intend to request help from the dhcp-bugs at isc.org
Apr 21 17:33:37 pfSense dhcpd: mailing list, please read the section on the README about
Apr 21 17:33:37 pfSense dhcpd: submitting bug reports and requests for help.
Apr 21 17:33:37 pfSense dhcpd:
Apr 21 17:33:37 pfSense dhcpd: Please do not under any circumstances send requests for
Apr 21 17:33:37 pfSense dhcpd: help directly to the authors of this software - please
Apr 21 17:33:37 pfSense dhcpd: send them to the appropriate mailing list as described in
Apr 21 17:33:37 pfSense dhcpd: the README file.
Apr 21 17:33:37 pfSense dhcpd:
Apr 21 17:33:37 pfSense dhcpd: exiting.
Apr 21 17:33:38 pfSense dhcpd: Internet Systems Consortium DHCP Server 4.2.6
Apr 21 17:33:38 pfSense dhcpd: Copyright 2004-2014 Internet Systems Consortium.
Apr 21 17:33:38 pfSense dhcpd: All rights reserved.
Apr 21 17:33:38 pfSense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Apr 21 17:33:38 pfSense dhcpd: Internet Systems Consortium DHCP Server 4.2.6
Apr 21 17:33:38 pfSense dhcpd: Copyright 2004-2014 Internet Systems Consortium.
Apr 21 17:33:38 pfSense dhcpd: All rights reserved.
Apr 21 17:33:38 pfSense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Apr 21 17:33:38 pfSense dhcpd: Wrote 0 deleted host decls to leases file.
Apr 21 17:33:38 pfSense dhcpd: Wrote 0 new dynamic host decls to leases file.
Apr 21 17:33:38 pfSense dhcpd: Wrote 4 leases to leases file.
Apr 21 17:33:38 pfSense dhcpd: Listening on BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24
Apr 21 17:33:38 pfSense dhcpd: Sending on   BPF/em0/b4:b5:2f:b4:xx:xx/192.168.10.0/24
Apr 21 17:33:38 pfSense dhcpd: Can't bind to dhcp address: Address already in use
Apr 21 17:33:38 pfSense dhcpd: Please make sure there is no other dhcp server
Apr 21 17:33:38 pfSense dhcpd: running and that there's no entry for dhcp or
Apr 21 17:33:38 pfSense dhcpd: bootp in /etc/inetd.conf.   Also make sure you
Apr 21 17:33:38 pfSense dhcpd: are not running HP JetAdmin software, which
Apr 21 17:33:38 pfSense dhcpd: includes a bootp server.
Apr 21 17:33:38 pfSense dhcpd:
Apr 21 17:33:38 pfSense dhcpd: If you did not get this software from ftp.isc.org, please
Apr 21 17:33:38 pfSense dhcpd: get the latest from ftp.isc.org and install that before
Apr 21 17:33:38 pfSense dhcpd: requesting help.
Apr 21 17:33:38 pfSense dhcpd:
Apr 21 17:33:38 pfSense dhcpd: If you did get this software from ftp.isc.org and have not
Apr 21 17:33:38 pfSense dhcpd: yet read the README, please read it before requesting help.
Apr 21 17:33:38 pfSense dhcpd: If you intend to request help from the dhcp-bugs at isc.org
Apr 21 17:33:38 pfSense dhcpd: mailing list, please read the section on the README about
Apr 21 17:33:38 pfSense dhcpd: submitting bug reports and requests for help.
Apr 21 17:33:38 pfSense dhcpd:
Apr 21 17:33:38 pfSense dhcpd: Please do not under any circumstances send requests for
Apr 21 17:33:38 pfSense dhcpd: help directly to the authors of this software - please
Apr 21 17:33:38 pfSense dhcpd: send them to the appropriate mailing list as described in
Apr 21 17:33:38 pfSense dhcpd: the README file.
Apr 21 17:33:38 pfSense dhcpd:
Apr 21 17:33:38 pfSense dhcpd: exiting.`
                          1 Reply Last reply Reply Quote 0
                          • S
                            stefanfa
                            last edited by

                            Tried switching the interfaces now to see if there's something with a NIC.

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

                              Yep it's my sk0 interface.

                              WAN is ok now and LAN is on static.

                              but sk0 still being reset but atleast now it's being ignored cause it's on static ip.

                              wonder if it's the driver or the card..

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

                                Might want to try swapping WAN and LAN assignments, see if it's just that NIC not playing nicely with your modem or whatever you have it plugged into. If the problem goes away, that's probably it. If the problem stays on your WAN, it's probably a modem issue. If the problem moves to LAN, probably a NIC issue.

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

                                  Ye that's just what i tried.

                                  problem moved to LAN when i switched.

                                  So question is then if it's a driver issue or a hardware issue.

                                  I'm considering getting a intel NIC instead.

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

                                    Funny story though.

                                    It's triggering rc.newwanip on my LAN interface ?

                                    Is it supposed to do that ?

                                    Apr 22 12:57:30 check_reload_status: rc.newwanip starting sk0
                                    Apr 22 12:57:31 php-fpm[87758]: /rc.newwanip: rc.newwanip: Info: starting on sk0.
                                    Apr 22 12:57:31 php-fpm[87758]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.10.254) (interface: LAN[lan]) (real interface: sk0).

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

                                      @stefanfa:

                                      It's triggering rc.newwanip on my LAN interface ?

                                      Is it supposed to do that ?

                                      Yes, that runs any time any interface gains link. It won't do much of anything when on a static IP LAN interface.

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

                                        Ah ok =)

                                        Anyway. This isn't really a problem anymore for me.

                                        I know what caused the issues now.

                                        Therefore i would like to take this opportunity to thank everyone who has been helping me out with this issue =)

                                        Thanks !

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