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

    pfsense breaks with Factorio client

    Scheduled Pinned Locked Moved
    Gaming
    2
    3
    617
    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.
    • J
      Jon8RFC
      last edited by Jon8RFC

      Who can I privately send logs to (please give me the specific location of the logs you want), because I have no idea how to begin troubleshooting this.

      I never had a problem with 2.5.2, and I played Factorio for about an hour without a problem, but I left the server, tried connecting to another, and pfsense kind of goes kaput. I can ping the router, but no internet access, no gui access. I'm keeping Factorio open so that if it has to do with Factorio somehow causing a problem, I can keep it in the state it's in; I can reboot pfsense and reproducibly cause it to become unresponsive and, for all intents and purposes, effectively crash just by attempting to join an online server through Factorio.

      Feb 17 10:43:02 kernel re1: watchdog timeout

      Feb 17 10:43:02 kernel re1: link state changed to DOWN

      Feb 17 10:43:02 kernel re1.1: link state changed to DOWN

      Feb 17 10:43:02 check_reload_status 308 Linkup starting re1

      Feb 17 10:43:02 check_reload_status 308 Linkup starting re1.1

      Feb 17 10:43:03 php-fpm 552 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.x.x.x )

      Feb 17 10:43:03 check_reload_status 308 Reloading filter

      Feb 17 10:43:03 check_reload_status 308 Reloading filter

      Feb 17 10:43:06 check_reload_status 308 Linkup starting re1

      Feb 17 10:43:06 kernel re1: link state changed to UP

      Feb 17 10:43:06 kernel re1.1: link state changed to UP

      Feb 17 10:43:06 check_reload_status 308 Linkup starting re1.1

      Feb 17 10:43:07 php-fpm 270 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.x.x.x )

      Feb 17 10:43:07 check_reload_status 308 Reloading filter

      Feb 17 10:43:08 check_reload_status 308 rc.newwanip starting re1

      Feb 17 10:43:09 php-fpm 12808 /rc.newwanip: rc.newwanip: Info: starting on re1.

      Feb 17 10:43:09 php-fpm 12808 /rc.newwanip: rc.newwanip: on (IP address: 192.x.x.x) (interface: LAN[lan]) (real interface: re1).

      Feb 17 10:43:20 check_reload_status 308 Linkup starting re0

      Feb 17 10:43:20 kernel re0: watchdog timeout

      Feb 17 10:43:20 kernel re0: link state changed to DOWN

      Feb 17 10:43:21 php-fpm 270 /rc.linkup: DEVD Ethernet detached event for wan

      Feb 17 10:43:22 check_reload_status 308 Reloading filter

      Feb 17 10:43:24 check_reload_status 308 Linkup starting re0

      Feb 17 10:43:24 kernel re0: link state changed to UP

      Feb 17 10:43:25 php-fpm 269 /rc.linkup: DEVD Ethernet attached event for wan

      Feb 17 10:43:25 php-fpm 269 /rc.linkup: HOTPLUG: Configuring interface wan

      Feb 17 10:43:25 check_reload_status 308 rc.newwanip starting re0

      Feb 17 10:43:25 php-fpm 269 /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''

      Feb 17 10:43:25 check_reload_status 308 Restarting IPsec tunnels

      Feb 17 10:43:26 php-fpm 12808 /rc.newwanip: rc.newwanip: Info: starting on re0.

      Feb 17 10:43:26 php-fpm 12808 /rc.newwanip: rc.newwanip: on (IP address: x.x.x.x) (interface: WAN[wan]) (real interface: re0).

      Feb 17 10:43:26 check_reload_status 308 Reloading filter

      Feb 17 10:43:26 dhcpleases 55096 Could not deliver signal HUP to process 62613: No such process.

      Feb 17 10:43:27 dhcpleases 59053 Could not deliver signal HUP to process 62613: No such process.

      Feb 17 10:43:29 check_reload_status 308 updating dyndns wan

      Feb 17 10:43:29 check_reload_status 308 Reloading filter

      Feb 17 10:43:31 rc.gateway_alarm 5357 >>> Gateway alarm: WAN_DHCP (Addr:x.x.x.x Alarm:1 RTT:20.103ms RTTsd:43.819ms Loss:21%)

      Feb 17 10:43:31 check_reload_status 308 updating dyndns WAN_DHCP

      Feb 17 10:43:31 check_reload_status 308 Restarting IPsec tunnels

      Feb 17 10:43:31 check_reload_status 308 Restarting OpenVPN tunnels/interfaces

      Feb 17 10:43:31 check_reload_status 308 Reloading filter

      Feb 17 10:43:32 php-fpm 552 /rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'

      Feb 17 10:43:32 php-fpm 552 /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. ''

      Feb 17 10:43:32 php-fpm 552 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.

      Feb 17 10:43:38 kernel re0: watchdog timeout

      Feb 17 10:43:38 kernel re0: link state changed to DOWN

      Feb 17 10:43:38 check_reload_status 308 Linkup starting re0

      Feb 17 10:43:39 php-fpm 12808 /rc.linkup: DEVD Ethernet detached event for wan

      Feb 17 10:43:40 check_reload_status 308 Reloading filter

      Feb 17 10:43:42 check_reload_status 308 Linkup starting re0

      Feb 17 10:43:42 kernel re0: link state changed to UP

      Feb 17 10:43:43 php-fpm 269 /rc.linkup: DEVD Ethernet attached event for wan

      Feb 17 10:43:43 php-fpm 269 /rc.linkup: HOTPLUG: Configuring interface wan

      Feb 17 10:43:47 kernel re0: watchdog timeout

      Feb 17 10:43:47 kernel re0: link state changed to DOWN

      Feb 17 10:43:47 check_reload_status 308 Linkup starting re0

      Feb 17 10:43:51 kernel re0: link state changed to UP

      Feb 17 10:43:51 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:06 kernel re0: watchdog timeout

      Feb 17 10:44:06 kernel re0: link state changed to DOWN

      Feb 17 10:44:06 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:10 kernel re0: link state changed to UP

      Feb 17 10:44:10 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:21 kernel re0: watchdog timeout

      Feb 17 10:44:21 kernel re0: link state changed to DOWN

      Feb 17 10:44:21 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:25 kernel re0: link state changed to UP

      Feb 17 10:44:25 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:36 kernel re0: watchdog timeout

      Feb 17 10:44:36 kernel re0: link state changed to DOWN

      Feb 17 10:44:36 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:40 kernel re0: link state changed to UP

      Feb 17 10:44:40 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:48 kernel re0: watchdog timeout

      Feb 17 10:44:48 kernel re0: link state changed to DOWN

      Feb 17 10:44:48 check_reload_status 308 Linkup starting re0

      Feb 17 10:44:53 kernel re0: link state changed to UP

      Feb 17 10:44:53 check_reload_status 308 Linkup starting re0

      Feb 17 10:45:05 kernel re0: watchdog timeout

      Feb 17 10:45:05 kernel re0: link state changed to DOWN

      Feb 17 10:45:05 check_reload_status 308 Linkup starting re0

      Feb 17 10:45:09 kernel re0: link state changed to UP

      Feb 17 10:45:09 check_reload_status 308 Linkup starting re0

      Feb 17 10:45:36 kernel re0: watchdog timeout

      Feb 17 10:45:36 kernel re0: link state changed to DOWN

      Feb 17 10:45:36 check_reload_status 308 Linkup starting re0

      Feb 17 10:45:40 kernel re0: link state changed to UP

      Feb 17 10:45:40 check_reload_status 308 Linkup starting re0

      Feb 17 10:45:54 kernel re0: watchdog timeout

      Feb 17 10:45:54 kernel re0: link state changed to DOWN

      Feb 17 10:45:54 check_reload_status 308 Linkup starting re0

      Feb 17 10:45:58 kernel re0: link state changed to UP

      Feb 17 10:45:58 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:07 kernel re0: watchdog timeout

      Feb 17 10:46:07 kernel re0: link state changed to DOWN

      Feb 17 10:46:07 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:11 kernel re0: link state changed to UP

      Feb 17 10:46:11 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:17 kernel re0: watchdog timeout

      Feb 17 10:46:17 kernel re0: link state changed to DOWN

      Feb 17 10:46:17 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:22 kernel re0: link state changed to UP

      Feb 17 10:46:22 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:35 kernel re0: watchdog timeout

      Feb 17 10:46:35 kernel re0: link state changed to DOWN

      Feb 17 10:46:35 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:39 kernel re0: link state changed to UP

      Feb 17 10:46:39 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:52 kernel re0: watchdog timeout

      Feb 17 10:46:52 kernel re0: link state changed to DOWN

      Feb 17 10:46:52 check_reload_status 308 Linkup starting re0

      Feb 17 10:46:56 kernel re0: link state changed to UP

      Feb 17 10:46:56 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:08 kernel re0: watchdog timeout

      Feb 17 10:47:08 kernel re0: link state changed to DOWN

      Feb 17 10:47:08 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:12 kernel re0: link state changed to UP

      Feb 17 10:47:12 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:18 kernel re0: watchdog timeout

      Feb 17 10:47:18 kernel re0: link state changed to DOWN

      Feb 17 10:47:18 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:22 kernel re0: link state changed to UP

      Feb 17 10:47:22 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:33 kernel re0: watchdog timeout

      Feb 17 10:47:33 kernel re0: link state changed to DOWN

      Feb 17 10:47:33 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:37 kernel re0: link state changed to UP

      Feb 17 10:47:37 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:47 kernel re0: watchdog timeout

      Feb 17 10:47:47 kernel re0: link state changed to DOWN

      Feb 17 10:47:47 check_reload_status 308 Linkup starting re0

      Feb 17 10:47:51 kernel re0: link state changed to UP

      Feb 17 10:47:51 check_reload_status 308 Linkup starting re0

      Feb 17 10:48:01 kernel re0: watchdog timeout

      Feb 17 10:48:01 kernel re0: link state changed to DOWN

      Feb 17 10:48:01 check_reload_status 308 Linkup starting re0

      Feb 17 10:48:05 kernel re0: link state changed to UP

      Feb 17 10:48:05 check_reload_status 308 Linkup starting re0

      Feb 17 10:48:16 kernel re0: watchdog timeout

      Feb 17 10:48:16 kernel re0: link state changed to DOWN

      Feb 17 10:48:16 check_reload_status 308 Linkup starting re0

      Feb 17 10:48:20 kernel re0: link state changed to UP

      Feb 17 10:48:20 check_reload_status 308 Linkup starting re0

      Feb 17 10:48:26 syslogd exiting on signal 15

      Feb 17 10:49:31 syslogd kernel boot file is /boot/kernel/kernel

      Feb 17 10:49:31 kernel ---<<BOOT>>--

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That isn't likely to be a problem with the software, but the hardware/drivers. The realtek interface re0 is having a problem.

        There are other threads with methods of installing different drivers, you might give that a try, but those errors are definitely from the hardware.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        J 1 Reply Last reply Reply Quote 1
        • J
          Jon8RFC @jimp
          last edited by Jon8RFC

          @jimp Yes, thank you, that's probably exactly it. It's been so long since I've upgraded that I completely forgot to reinstall updated drivers as I've done in the past.

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