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

    192.168.100.10 - loss of network suddenly

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 3 Posters 833 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.
    • P
      purduephotog
      last edited by

      Evening-

      Before I go trying to track down any rogue devices, I lost network a bit ago. I logged into the pfsense console and I saw my WAN IP was set to 192.168.100.10. Which was ... very odd, to say the least. Not too many of the devices I have have a .100 in their subnet.

      Is this a failover/fallback value that is in the code somewhere? Or did somehow my ARRIS modem 'promote' the 192.168.100.1 (that's the router 'login' config screen) and issue me an IP?

      Actually, it seems I have my answer-
      System Up Time 0 days 0h:6m:50s - that's from my Arris screen. So somehow it issued the pfsense firewall a bogus IP.

      I wonder what "Spectrum" is doing now.

      1 Reply Last reply Reply Quote 0
      • chpalmerC
        chpalmer
        last edited by chpalmer

        Cable modems are generally designed to give out an address to the device behind them an address when they can't connect to the ISP. It allows you to get into the modem for diagnostics without having to set an address to do so.

        What model Arris?

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        1 Reply Last reply Reply Quote 1
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          Interfaces > WAN

          0_1532890679068_Screen Shot 2018-07-29 at 11.57.25 AM.png

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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