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

    Cannot communicate off-LAN after upgrade to 24.03

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 197 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.
    • K
      kj32
      last edited by

      This category was my best guess; moderators should feel free to redirect.

      I have an SG3100 configured as a filtering bridge. Perhaps a little unusual, but it has worked well for us.

      WAN/mvneta2 and OPT1/mvneta0 are the bridge ports. LAN/mvneta1 is connected to the local network as the management port. There is a router connected to the local network. Before this upgrade, the SG3100 could access the pfSense servers to download new software. Now, the SG3100 cannot access any system that is off the local network. However, as far as I can tell, the filtering bridge functions are working correctly.

      A simple test is to try to use Diagnostics | Ping to reach some remote system. This fails. I have tried doing this while running Packet Capture on ICMP packets. I see the echo requests sent on the local network, and received on the local network side of the bridge, but not being sent on the upstream side of the bridge (where the router is).

      On the other hand, if I use ping from another system on the local network to a remote system, I see echo request and reply packets on the local network side of the bridge, and on the upstream side of the bridge.

      I have not changed the bridge or filtering configuration to the best of my knowledge.

      The one other thing I noticed was that after the upgrade, I could not access the web configurator until I set the IP address on the LAN interface from the serial port. During that process the existing IP address appeared to be correct before I set it again.

      I would be pleased to receive suggestions on further investigation that would improve my insight into this problem.

      Thanks,

      K

      K 1 Reply Last reply Reply Quote 0
      • K
        kj32 @kj32
        last edited by

        @kj32

        User error. I found some old notes that included this observation:

        "Lan gateway should be defined under System | Routing, not interface."

        Removed the spurious definition under interface, and now it works again.

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