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

    LAN/WAN never work at the same time

    Scheduled Pinned Locked Moved Virtualization
    11 Posts 2 Posters 4.9k 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.
    • R
      Randomzero
      last edited by

      Alright so after ton of configurations, I've only managed to get LAN or WAN working separately, never at the same time.

      I'm using VMware workstation 6.5 with pfSense 1.2.2

      I have Host Virtual Network Mapping set to:
      VMnet0 - Onboard NIC
      VMnet1 - LAC3 (VMnet1) - default
      VMnet2 - PCI NIC
      VMnet3 - Wireless NIC
      VMnet8 - LAC4 (VMnet8) - default

      In the connection properties, for the Onboard NIC, I only have VMware Bridge Protocol selected
      For the other connections, I have everything selected.

      So far, the most I've really been able to do is access the GUI when the pc is connected to the WAN port, and the WAN address is an address that would be assigned by LAN.
      I've gotten it to detect an actual WAN ip a couple times, but when it did and I tried to access any WAN settings in the GUI, it would stop loading until I went to a different page..

      I've got the windows firewall off on all networks.

      What could be wrong here?

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        It sounds like a VMWare configuration error.  Which VMWare network have you connected to your WAN and which to your LAN?  Have you configured VMWare to pass those to pfSense accordingly?

        1 Reply Last reply Reply Quote 0
        • R
          Randomzero
          last edited by

          My WAN is eth0, set as a Other (VMNet0). Eth0 should be the onboard nic, so that's what I have it connected to.
          The LAN is eth1, set as bridge.

          I think it might be an issue with the NIC's themselves or the router's having problems with them.
          I decided to try simply getting online on the PC using each of the NIC's.
          Originally, the onboard NIC worked. But when I switched the ethernet cord to the other NIC's, I kept getting 169.* ip's. Went back to the onboard NIC and got a 169.* ip as well..

          1 Reply Last reply Reply Quote 0
          • Cry HavokC
            Cry Havok
            last edited by

            What is the LAN interface bridged with - if it's bridged with the onboard NIC I'm not surprised you're having problems.

            1 Reply Last reply Reply Quote 0
            • R
              Randomzero
              last edited by

              I've tried every setting there is in VMWare and it still doesn't work properly.

              1 Reply Last reply Reply Quote 0
              • Cry HavokC
                Cry Havok
                last edited by

                You failed to answer my question.

                1 Reply Last reply Reply Quote 0
                • R
                  Randomzero
                  last edited by

                  Which bridge do you mean?

                  In pfSense, it's em1, which is currently set as NAT in VMWare.. But I've tried Bridge, and Custom with VMnet1 and 2 with the same results..

                  1 Reply Last reply Reply Quote 0
                  • Cry HavokC
                    Cry Havok
                    last edited by

                    Ok, let's do a little basic networking - does your VMWare host have 2 physical network interfaces?

                    1 Reply Last reply Reply Quote 0
                    • R
                      Randomzero
                      last edited by

                      Yes

                      1 Reply Last reply Reply Quote 0
                      • Cry HavokC
                        Cry Havok
                        last edited by

                        Is one connected to your WAN and one to your LAN.

                        Are your WAN and LAN physically separate networks with different IP ranges?

                        1 Reply Last reply Reply Quote 0
                        • R
                          Randomzero
                          last edited by

                          WAN is connected to my router (192.168.1.)
                          LAN is connected to a netbook I'm using for testing (192.168.2.
                          )

                          I've actually managed to get it working.
                          I was using 3 NIC's, but when I disabled one and set WAN to VMnet0 and LAN to VMnet4 (For some reason, I can't assign the PCIE NIC to anything in the Virtual Network Editor) and pfSense is reporting a valid IP from the router and I'm able to access the gui from the netbook, but I can't route further with it.

                          So I decided to test it going directly from the modem. And it failed to renew the IP. So I connected it back to the router, and it's once again assigning itself one of it's own LAN ips.

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