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

    Setting Default Gateway on PPPoE makes the system stops

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    2 Posts 2 Posters 2.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.
    • J
      joyfulway
      last edited by

      Hi

      I'm using Soekris net5501 to run some test on 2.0 nanobsd version.

      I can't connect to the Internet using a PPPoE connexion type. Interface status keeps on being down (works perfectly whit 1.2RCx)
      When setting a default gateway on the WAN interface, the system hangs and reboot. I am then unable to restart pfsense and the following message is displayed at boot:

      10)  Filter Logs
      11)  Restart webConfigurator
      12)  pfSense Developer Shell
      13)  Upgrade from console
      14)  Disable Secure Shell (sshd)

      Enter an option:

      Fatal trap 12: page fault while in kernel mode
      fault virtual address  = 0x250
      fault code              = supervisor read, page not present
      instruction pointer    = 0x20:0xc04c88a7
      stack pointer          = 0x28:0xe6bda7cc
      frame pointer          = 0x28:0xe6bdaa14
      code segment            = base 0x0, limit 0xfffff, type 0x1b
                              = DPL 0, pres 1, def32 1, gran 1
      processor eflags        = interrupt enabled, resume, IOPL = 0
      current process        = 2327 (apinger)
      trap number            = 12
      panic: page fault
      Uptime: 43m35s
      Cannot dump. Device not defined or unavailable.
      Automatic reboot in 15 seconds - press a key on the console to abort
      Rebooting…
      fA

      Bastien

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

        This is probably related to a kernel patch that was causing problems and has been fixed since, try a new snapshot.

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