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

    Random Death, No crash File

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 1.2k 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.
    • T
      TheX1le
      last edited by

      Been running PF sense for years on a Tri Core AMD machine, with 4gigs of ram. Currently running 2.0.3. The system is overkill but its an old gaming box and what i had on hand.
      Every since 2.0.2 the system has been a tad unstable, used to be once every few weeks, it would just stop passing traffic and require a reboot. Now it seems to be every few days. I have checked /var/crash and its empty. Nothing is glaring in the system logs.
      The System uses two Intel(R) PRO/1000 Legacy Network Connection cards along with the em driver. I have read the page about the driver and tried upping the ram buf.
      Each one of these cards supports several vlans

      When things crash I am never around, and it seems that when i do discover it, its because my dhcp leases have expired.
      This lead me to check the dhcpd log.

      Here is an excerpt of when it wasn't working. It seems the clients don't want to hold their leases.
      Aug  5 12:38:43 pfsense dhcpd: DHCPDISCOVER from 18:2a:7b:5b:90:13 via em0_vlan100
      Aug  5 12:38:43 pfsense dhcpd: DHCPOFFER on 172.16.12.157 to 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100
      Aug  5 12:38:43 pfsense dhcpd: DHCPREQUEST for 172.16.12.157 (172.16.12.1) from 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100
      Aug  5 12:38:43 pfsense dhcpd: DHCPACK on 172.16.12.157 to 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100
      Aug  5 12:38:44 pfsense dhcpd: DHCPRELEASE of 172.16.12.157 from 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100 (found)
      Aug  5 12:39:15 pfsense dhcpd: DHCPDISCOVER from 18:2a:7b:5b:90:13 via em0_vlan100
      Aug  5 12:39:15 pfsense dhcpd: DHCPOFFER on 172.16.12.157 to 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100
      Aug  5 12:39:15 pfsense dhcpd: DHCPREQUEST for 172.16.12.157 (172.16.12.1) from 18:2a:7b:5b:90:13 (Nintendo 3DS) viaem0_vlan100
      Aug  5 12:39:15 pfsense dhcpd: DHCPACK on 172.16.12.157 to 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100
      Aug  5 12:39:15 pfsense dhcpd: DHCPRELEASE of 172.16.12.157 from 18:2a:7b:5b:90:13 (Nintendo 3DS) via em0_vlan100 (found)

      Any suggestions would be greatly appreciated

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

        Forgot to mention system is running 64 bit version which installed to hdd. I checked and there is plenty of free space.

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          The log extracts you posted show pfSense reporting the clients decided to release their DHCP leases. You will have to look to the clients for an explanation. I expect getting an explanation for that from a Nintendo might be a challenge - does it have an event log you can examine?

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