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

Unable to ping lan ip unless directly connected (no switch in between)

Scheduled Pinned Locked Moved L2/Switching/VLANs
3 Posts 2 Posters 464 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.
  • A
    Ahira
    last edited by Jul 24, 2018, 7:11 PM

    Hello all,

    First time installing pfSense. I've installed to ESXI 6.5 on a UCS 220 m4. Right after install, I assigned a WAN ip and was able to ping to the internet. LAN IP was set by default to 192.168.1.1. The VM LAN is connected to a lan vswitch with an uplink connected to a Cisco 3560-cx switch. I'm not able to ping the lan ip of 1.1. However, when plugged directly from the laptop to the lan of the pfsense, I can ping 1.1. Thinking something funky in my switch config, I completely wiped it. On reboot I created a SVI with ip of 192.168.1.253 and the switch still can't ping the directly connected pfsense.

    I've tried both e1000 and vmxnet3 adapters. I've reinstalled pfsense. I've triple-checked all the vswitch and uplink configuration. I"m at a complete loss here. Any help is greatly appreciated!

    1 Reply Last reply Reply Quote 0
    • J
      JKnott
      last edited by Jul 24, 2018, 8:00 PM

      There should be no difference between using a switch or not, other than needing a crossover cable when connecting between 10/100 Mb NICs. Do you have another switch to try?

      PfSense running on Qotom mini PC
      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
      UniFi AC-Lite access point

      I haven't lost my mind. It's around here...somewhere...

      1 Reply Last reply Reply Quote 0
      • A
        Ahira
        last edited by Jul 24, 2018, 10:40 PM

        Thanks for the reply. I figured this out. Not knowing the first thing about UCS servers, evidently, the ports I am using are "vNICs". I needed to configure both ends of the link as trunks. This still makes very little sense to me, but it worked.

        1 Reply Last reply Reply Quote 0
        1 out of 3
        • First post
          1/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received