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

    Traffic between lan and lan2 (virtual ip) is only 1 way

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 534 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.
    • S Offline
      scotty562
      last edited by

      Hello all. I have my network on 192.168.1.0 /24. I'm branching part of it off into 192.168.2.0 /24. To do this I've added a virtual ip onto the lan interface in pfsense. The gateway for each is .31. So hosts from both subnets are able to ping .31 on both gateways, wooh. Here is where things go wrong. My hosts on the 2.0 network are able to ping hosts on the 1.1 network, but hosts on the 1.0 network are not able to ping hosts on the 2.0 network. My work around as of now was to add a 2.0 ip address onto the network adapter of the 1.0 hosts as needed. I've added all of the appropriate firewall rules as far as I can tell and the firewall logs don't show that they are blocking anything.

      Edit:
      One additional piece of information is that from the lan interface of 1.0 I am able to ping hosts on 2.0 so it's definitely a configuration setting somewhere.

      Edit2:
      A little more info. I'm getting a reply from my default gateway when pinging that the destination host is unreachable. So for some reason It's hitting the default gateway rather than routing properly.

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

        It's definitely a completely nasty way to configure two subnets.  You cannot expect every device you encounter to handle that in a sane fashion.  You need two interfaces.  Else put them all on the same subnet and all your problems will vanish.

        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 0
        • S Offline
          scotty562
          last edited by

          I figured if the feature was there I'd take advantage of it, but if it's that unreliable I'll figure something else out.

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