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

    Having an issue losing internet access randomly after 2.5 update. Log inside.

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 668 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.
    • R
      rodger_dodger
      last edited by

      So I'm not sure what's causing the issue, but this is happening nearly every morning when I get up, the internet is out. No issues with previous 2.4x. Happened the night I updated to the latest 2.5 stable release.

      I upgraded Feb. 21 around 16:00.

      Feb 21 20:09:50    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:50    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:51    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:51    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:52    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:52    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:52    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:52    kernel        re0: link state changed to UP
Feb 21 20:09:52    kernel        re0.99: link state changed to UP
Feb 21 20:09:52    kernel        re0.10: link state changed to UP
Feb 21 20:09:52    check_reload_status    377    Linkup starting re0
Feb 21 20:09:52    check_reload_status    377    Linkup starting re0.99
Feb 21 20:09:52    check_reload_status    377    Linkup starting re0.10
Feb 21 20:09:53    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:53    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:53    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:53    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:54    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:54    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:55    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:55    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:55    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:56    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:56    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:57    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:57    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:57    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:58    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:58    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:58    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:59    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:59    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:09:59    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:00    php-fpm    340    /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1613956200] unbound[45301:0] error: bind: address already in use [1613956200] unbound[45301:0] fatal error: could not open ports'
Feb 21 20:10:00    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:00    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:01    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:01    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:01    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:02    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:02    check_reload_status    377    updating dyndns lan
Feb 21 20:10:02    check_reload_status    377    Reloading filter
Feb 21 20:10:02    php-fpm    16727    /rc.linkup: DEVD Ethernet detached event for lan
Feb 21 20:10:02    check_reload_status    377    Reloading filter
Feb 21 20:10:02    php-fpm    339    /rc.linkup: DEVD Ethernet attached event for lan
Feb 21 20:10:02    php-fpm    339    /rc.linkup: HOTPLUG: Configuring interface lan
Feb 21 20:10:02    php-fpm    339    /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 21 20:10:02    php-fpm    339    /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 21 20:10:02    check_reload_status    377    Restarting ipsec tunnels
Feb 21 20:10:02    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:03    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:03    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:04    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:04    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:04    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:04    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:05    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:05    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:05    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:05    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:06    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:06    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:06    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:07    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:07    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:07    kernel        re0: watchdog timeout
Feb 21 20:10:07    kernel        re0: link state changed to DOWN
Feb 21 20:10:07    kernel        re0.99: link state changed to DOWN
Feb 21 20:10:07    kernel        re0.10: link state changed to DOWN
Feb 21 20:10:07    check_reload_status    377    Linkup starting re0
Feb 21 20:10:07    check_reload_status    377    Linkup starting re0.99
Feb 21 20:10:07    check_reload_status    377    Linkup starting re0.10
Feb 21 20:10:07    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:07    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:08    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:09    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:10    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:10    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:11    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:11    kernel        re0: link state changed to UP
Feb 21 20:10:11    kernel        re0.99: link state changed to UP
Feb 21 20:10:11    kernel        re0.10: link state changed to UP
Feb 21 20:10:11    check_reload_status    377    Linkup starting re0
Feb 21 20:10:11    check_reload_status    377    Linkup starting re0.99
Feb 21 20:10:11    check_reload_status    377    Linkup starting re0.10
Feb 21 20:10:11    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:12    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:12    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:13    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:13    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:14    kernel        arpresolve: can't allocate llinfo for x.x.x.x on re0.99
Feb 21 20:10:14    kernel        ovpnc3: link state changed to DOWN
Feb 21 20:10:14    check_reload_status    377    Reloading filter
Feb 21 20:10:16    check_reload_status    377    updating dyndns lan
Feb 21 20:10:17    check_reload_status    377    Reloading filter
Feb 21 20:10:17    php-fpm    10122    /rc.linkup: DEVD Ethernet detached event for lan
Feb 21 20:10:17    php-fpm    30690    /rc.linkup: DEVD Ethernet attached event for lan
Feb 21 20:10:17    php-fpm    30690    /rc.linkup: HOTPLUG: Configuring interface lan
Feb 21 20:10:17    php-fpm    30690    /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 21 20:10:17    php-fpm    30690    /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 21 20:10:17    check_reload_status    377    Restarting ipsec tunnels
Feb 21 20:10:21    check_reload_status    377    updating dyndns lan
Feb 21 20:10:21    check_reload_status    377    Reloading filter
Feb 21 20:10:21    php-fpm    16727    /rc.linkup: DEVD Ethernet detached event for lan
Feb 21 20:10:21    php-fpm    10122    /rc.linkup: DEVD Ethernet attached event for lan
Feb 21 20:10:21    php-fpm    10122    /rc.linkup: HOTPLUG: Configuring interface lan
Feb 21 20:10:21    php-fpm    10122    /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 21 20:10:21    php-fpm    10122    /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 21 20:10:21    check_reload_status    377    Restarting ipsec tunnels
Feb 21 20:10:25    check_reload_status    377    updating dyndns lan
Feb 21 20:10:25    php-fpm    16727    /rc.linkup: DEVD Ethernet detached event for lan
Feb 21 20:10:25    php-fpm    16727    /rc.linkup: DEVD Ethernet attached event for lan
Feb 21 20:10:25    php-fpm    16727    /rc.linkup: HOTPLUG: Configuring interface lan
Feb 21 20:10:25    php-fpm    16727    /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 21 20:10:25    php-fpm    16727    /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 21 20:10:25    check_reload_status    377    Restarting ipsec tunnels
Feb 21 20:10:30    check_reload_status    377    Reloading filter
Feb 21 20:10:39    kernel        re0: watchdog timeout
Feb 21 20:10:39    kernel        re0: link state changed to DOWN
Feb 21 20:10:39    kernel        re0.99: link state changed to DOWN
Feb 21 20:10:39    kernel        re0.10: link state changed to DOWN
Feb 21 20:10:39    check_reload_status    377    Linkup starting re0
Feb 21 20:10:39    check_reload_status    377    Linkup starting re0.99
Feb 21 20:10:39    check_reload_status    377    Linkup starting re0.10
Feb 21 20:10:40    check_reload_status    377    Reloading filter
Feb 21 20:10:43    kernel        re0: link state changed to UP
Feb 21 20:10:43    kernel        re0.99: link state changed to UP
Feb 21 20:10:43    kernel        re0.10: link state changed to UP
Feb 21 20:10:43    check_reload_status    377    Linkup starting re0
Feb 21 20:10:43    check_reload_status    377    Linkup starting re0.99
Feb 21 20:10:43    check_reload_status    377    Linkup starting re0.10
Feb 21 20:10:54    kernel        re0: watchdog timeout
Feb 21 20:10:54    kernel        re0: link state changed to DOWN
Feb 21 20:10:54    kernel        re0.99: link state changed to DOWN
Feb 21 20:10:54    kernel        re0.10: link state changed to DOWN
Feb 21 20:10:54    check_reload_status    377    Linkup starting re0
Feb 21 20:10:54    check_reload_status    377    Linkup starting re0.99
Feb 21 20:10:54    check_reload_status    377    Linkup starting re0.10
Feb 21 20:10:59    kernel        re0: link state changed to UP
Feb 21 20:10:59    kernel        re0.99: link state changed to UP
Feb 21 20:10:59    kernel        re0.10: link state changed to UP
Feb 21 20:10:59    check_reload_status    377    Linkup starting re0
Feb 21 20:10:59    check_reload_status    377    Linkup starting re0.99
Feb 21 20:10:59    check_reload_status    377    Linkup starting re0.10
Feb 21 20:11:10    kernel        re0: watchdog timeout
Feb 21 20:11:10    kernel        re0: link state changed to DOWN
Feb 21 20:11:10    kernel        re0.99: link state changed to DOWN
Feb 21 20:11:10    kernel        re0.10: link state changed to DOWN
Feb 21 20:11:10    check_reload_status    377    Linkup starting re0
Feb 21 20:11:10    check_reload_status    377    Linkup starting re0.99
Feb 21 20:11:10    check_reload_status    377    Linkup starting re0.10
Feb 21 20:11:14    kernel        re0: link state changed to UP
Feb 21 20:11:14    kernel        re0.99: link state changed to UP
Feb 21 20:11:14    kernel        re0.10: link state changed to UP
Feb 21 20:11:14    check_reload_status    377    Linkup starting re0
Feb 21 20:11:14    check_reload_status    377    Linkup starting re0.99
Feb 21 20:11:14    check_reload_status    377    Linkup starting re0.10
Feb 21 20:11:20    kernel        re0: watchdog timeout
Feb 21 20:11:20    kernel        re0: link state changed to DOWN
Feb 21 20:11:20    kernel        re0.99: link state changed to DOWN
Feb 21 20:11:20    kernel        re0.10: link state changed to DOWN
Feb 21 20:11:20    check_reload_status    377    Linkup starting re0
Feb 21 20:11:20    check_reload_status    377    Linkup starting re0.99
Feb 21 20:11:20    check_reload_status    377    Linkup starting re0.10
Feb 21 20:11:24    kernel        re0: link state changed to UP
Feb 21 20:11:24    kernel        re0.99: link state changed to UP
Feb 21 20:11:24    kernel        re0.10: link state changed to UP
Feb 21 20:11:24    check_reload_status    377    Linkup starting re0
Feb 21 20:11:24    check_reload_status    377    Linkup starting re0.99
Feb 21 20:11:24    check_reload_status    377    Linkup starting re0.10
Feb 21 20:11:56    kernel        re0: watchdog timeout
Feb 21 20:11:56    kernel        re0: link state changed to DOWN
Feb 21 20:11:56    kernel        re0.99: link state changed to DOWN
Feb 21 20:11:56    kernel        re0.10: link state changed to DOWN
Feb 21 20:11:56    check_reload_status    377    Linkup starting re0
Feb 21 20:11:56    check_reload_status    377    Linkup starting re0.99
Feb 21 20:11:56    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:00    kernel        re0: link state changed to UP
Feb 21 20:12:00    kernel        re0.99: link state changed to UP
Feb 21 20:12:00    kernel        re0.10: link state changed to UP
Feb 21 20:12:00    check_reload_status    377    Linkup starting re0
Feb 21 20:12:00    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:00    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:13    kernel        re0: watchdog timeout
Feb 21 20:12:13    kernel        re0: link state changed to DOWN
Feb 21 20:12:13    kernel        re0.99: link state changed to DOWN
Feb 21 20:12:13    kernel        re0.10: link state changed to DOWN
Feb 21 20:12:13    check_reload_status    377    Linkup starting re0
Feb 21 20:12:13    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:13    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:17    kernel        re0: link state changed to UP
Feb 21 20:12:17    kernel        re0.99: link state changed to UP
Feb 21 20:12:17    kernel        re0.10: link state changed to UP
Feb 21 20:12:17    check_reload_status    377    Linkup starting re0
Feb 21 20:12:17    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:17    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:27    kernel        re0: watchdog timeout
Feb 21 20:12:27    kernel        re0: link state changed to DOWN
Feb 21 20:12:27    kernel        re0.99: link state changed to DOWN
Feb 21 20:12:27    kernel        re0.10: link state changed to DOWN
Feb 21 20:12:27    check_reload_status    377    Linkup starting re0
Feb 21 20:12:27    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:27    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:31    kernel        re0: link state changed to UP
Feb 21 20:12:31    kernel        re0.99: link state changed to UP
Feb 21 20:12:31    kernel        re0.10: link state changed to UP
Feb 21 20:12:31    check_reload_status    377    Linkup starting re0
Feb 21 20:12:31    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:31    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:42    kernel        re0: watchdog timeout
Feb 21 20:12:42    kernel        re0: link state changed to DOWN
Feb 21 20:12:42    kernel        re0.99: link state changed to DOWN
Feb 21 20:12:42    kernel        re0.10: link state changed to DOWN
Feb 21 20:12:42    check_reload_status    377    Linkup starting re0
Feb 21 20:12:42    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:42    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:46    kernel        re0: link state changed to UP
Feb 21 20:12:46    kernel        re0.99: link state changed to UP
Feb 21 20:12:46    kernel        re0.10: link state changed to UP
Feb 21 20:12:46    check_reload_status    377    Linkup starting re0
Feb 21 20:12:46    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:46    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:55    kernel        re0: watchdog timeout
Feb 21 20:12:55    kernel        re0: link state changed to DOWN
Feb 21 20:12:55    kernel        re0.99: link state changed to DOWN
Feb 21 20:12:55    kernel        re0.10: link state changed to DOWN
Feb 21 20:12:55    check_reload_status    377    Linkup starting re0
Feb 21 20:12:55    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:55    check_reload_status    377    Linkup starting re0.10
Feb 21 20:12:59    kernel        re0: link state changed to UP
Feb 21 20:12:59    kernel        re0.99: link state changed to UP
Feb 21 20:12:59    kernel        re0.10: link state changed to UP
Feb 21 20:12:59    check_reload_status    377    Linkup starting re0
Feb 21 20:12:59    check_reload_status    377    Linkup starting re0.99
Feb 21 20:12:59    check_reload_status    377    Linkup starting re0.10
Feb 21 20:13:08    kernel        re0: watchdog timeout
Feb 21 20:13:08    kernel        re0: link state changed to DOWN
Feb 21 20:13:08    kernel        re0.99: link state changed to DOWN
Feb 21 20:13:08    kernel        re0.10: link state changed to DOWN
Feb 21 20:13:08    check_reload_status    377    Linkup starting re0
Feb 21 20:13:08    check_reload_status    377    Linkup starting re0.99
Feb 21 20:13:08    check_reload_status    377    Linkup starting re0.10
Feb 21 20:13:12    kernel        re0: link state changed to UP
Feb 21 20:13:12    kernel        re0.99: link state changed to UP
Feb 21 20:13:12    kernel        re0.10: link state changed to UP
Feb 21 20:13:12    check_reload_status    377    Linkup starting re0
Feb 21 20:13:12    check_reload_status    377    Linkup starting re0.99
Feb 21 20:13:12    check_reload_status    377    Linkup starting re0.10
Feb 21 20:13:19    kernel        re0: watchdog timeout
Feb 21 20:13:19    kernel        re0: link state changed to DOWN
Feb 21 20:13:19    kernel        re0.99: link state changed to DOWN
Feb 21 20:13:19    kernel        re0.10: link state changed to DOWN
Feb 21 20:13:19    check_reload_status    377    Linkup starting re0
Feb 21 20:13:19    check_reload_status    377    Linkup starting re0.99
Feb 21 20:13:19    check_reload_status    377    Linkup starting re0.10
Feb 21 20:13:23    kernel        re0: link state changed to UP
Feb 21 20:13:23    kernel        re0.99: link state changed to UP
Feb 21 20:13:23    kernel        re0.10: link state changed to UP
Feb 21 20:14:28    syslogd        kernel boot file is /boot/kernel/kernel
      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        All of your problems seem related to your physical NIC. See all those re0 messages in there? That's a Realtek NIC. Those are known to be a bit flaky sometimes on FreeBSD. The new pfSense 2.5.0 version is based on an updated FreeBSD operating system (12.2/STABLE whereas the previous 2.4.5 version was FreeBSD-11.3/STABLE). There were several NIC driver related changes in the bump from FreeBSD-11 to FreeBSD-12. One big one was the move to the iflib wrapper for NIC drivers.

        It's possible your Realtek NIC is not happy with the new FreeBSD-12 driver. Is your NIC replaceable? Is it a card you could replace with say an Intel NIC, or is there an empty card slot in the box where you could install an Intel NIC and use it instead? The Intel devices, especially the older ones, are well supported in FreeBSD.

        1 Reply Last reply Reply Quote 1
        • R
          rodger_dodger
          last edited by

          @bmeeks

          Thank you so much for taking time out of your day to help. That makes perfect sense to me.
          One question. I'm moving my Pfsense box off to a VM in Unraid on a R710 with 4 gigabit intel nics. Would it be safe to say this config should still be good to export, and import into the new 2.5 pfsense on the new rig as a jumping off point?

          bmeeksB 1 Reply Last reply Reply Quote 0
          • bmeeksB
            bmeeks @rodger_dodger
            last edited by bmeeks

            @rodger_dodger said in Having an issue losing internet access randomly after 2.5 update. Log inside.:

            @bmeeks

            Thank you so much for taking time out of your day to help. That makes perfect sense to me.
            One question. I'm moving my Pfsense box off to a VM in Unraid on a R710 with 4 gigabit intel nics. Would it be safe to say this config should still be good to export, and import into the new 2.5 pfsense on the new rig as a jumping off point?

            Virtualizing pfSense is a good choice. Your configuration will import, but you will have to reassign which physical NIC is WAN, LAN, etc. But pfSense will prompt you for that during initial setup because it will see the physical NIC interface names are changed.

            R 1 Reply Last reply Reply Quote 1
            • R
              rodger_dodger @bmeeks
              last edited by

              @bmeeks

              That's what I figured! Thanks again!

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