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

    Puzzled by entry in routing table

    Scheduled Pinned Locked Moved Routing and Multi WAN
    routing
    3 Posts 2 Posters 418 Views 2 Watching
    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.
    • gnitingG Offline
      gniting
      last edited by

      I recently switched my LTE modem (failover WAN) from routing to bridging mode. When it was in routing (default) mode, I had was accessing it via a 192.168.5.x scheme. Post switch to bridge mode, the IP of the modem is 10.42.x.x

      Everything is working fine but I am a bit baffled by this entry in the pfsense routing table:
      192.168.5.1 10.42.234.1 UGHS 0 1500 em2

      I should not have anything using/pointing to/referencing 192.168.5.x anymore. I've checked all rules, servers (openvpn, etc.) but can't locate anything. This is not causing any issues and everything is working as expected but I am still puzzled by the presence of this entry.

      Moreover, when I ping 192.168.5.1, I get a response but there's no host with that IP anywhere!

      PING 192.168.5.1 (192.168.5.1): 56 data bytes
      64 bytes from 192.168.5.1: icmp_seq=0 ttl=64 time=1.088 ms
      64 bytes from 192.168.5.1: icmp_seq=1 ttl=64 time=0.977 ms
      64 bytes from 192.168.5.1: icmp_seq=2 ttl=64 time=0.607 ms
      

      traceroute shows 1 hop:

      traceroute to 192.168.5.1 (192.168.5.1), 64 hops max, 40 byte packets
       1  192.168.5.1 (192.168.5.1)  1.141 ms  1.064 ms  0.498 ms
      

      UGHS suggests manually added entry, but from where?

      1 Reply Last reply Reply Quote 0
      • S Offline
        serbus
        last edited by

        Hello!

        My netgear lb1120 pushes that route to pfsense through dhcp when you put it in bridge mode. I think it is just a courtesy route to help get to the admin interface.

        Shell Output - clog /var/log/dhcpd.log | grep "192.168.5.1"

        Jun 12 23:13:43 pfSense dhclient: New Static Routes (mvneta0.4092): 192.168.5.1 100.101.128.1

        John

        Lex parsimoniae

        gnitingG 1 Reply Last reply Reply Quote 0
        • gnitingG Offline
          gniting @serbus
          last edited by

          @serbus said in Puzzled by entry in routing table:

          Hello!

          My netgear lb1120 pushes that route to pfsense through dhcp when you put it in bridge mode. I think it is just a courtesy route to help get to the admin interface.

          Shell Output - clog /var/log/dhcpd.log | grep "192.168.5.1"

          Jun 12 23:13:43 pfSense dhclient: New Static Routes (mvneta0.4092): 192.168.5.1 100.101.128.1

          John

          Thanks! Yeah, I arrived at the same conclusion after I did more research.

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