• 0 Votes
    5 Posts
    803 Views
    U
    If it'll help, some further details about my setup, everything is connected by Unifi switches that are vlan capable, but not all of the ports are specifically configured to be on a vlan. I've been doing fping tests just to see what can be seen through a few different systems, and below is my findings. From a system that is connected to a port designated with vlan 3220 [10.32.2.0 network]: uquevedo@ubence-air-wired ~ % fping -ga 10.32.40.1 10.32.40.254 10.32.40.1 10.32.40.10 From the VM itself that is configured with the bridge interface to vlan 3240: uquevedo@kea-testing:~$ fping -qga 10.32.40.1 10.32.40.254 10.32.40.1 10.32.40.10 From a system that is connected to a port designated with vlan 3230 [10.32.3.0 network]: [uquevedo@fedora-system ~]$ fping -ga 10.32.40.1 10.32.40.254 10.32.40.1 10.32.40.10 From the actual RHEL9.2 host system, which of course can ping the IP address: [uquevedo@rh-vm01 ~]$ fping -ga 10.32.40.1 10.32.40.254 10.32.40.1 10.32.40.9 10.32.40.10 There are many bridged interfaces on the host system connecting to various vlan tagged interfaces: [image: 1684333278736-screenshot-2023-05-17-at-7.13.36-am.png] The bridge0 interface is a non-vlan tagged interface [vlan1?] and is accessible to all systems on the network. I was under the assumption that if a network interface was tagged with vlan information that it would be accessible to other systems that are part of that same vlan? Another thing about my setup is that these vlans are configured on a pfSense box for lab purposes, they are not configured on my main pfSense box [which I don't think matters]. So even though the opt ports of this system are technically on their own network, they are connecting to my main network.
  • 0 Votes
    1 Posts
    942 Views
    No one has replied
  • 0 Votes
    3 Posts
    1k Views
    W
    @WAR10CK said in Intel gigabit ct Desktop not detected: AHCI enclosure management bridge OK, pfsense recognizes the netcard, but why is it saying : AHCI enclosure management bridge under interface em0. There is no link when I plugin the cable to em0. The cable works fine in em1.
  • 0 Votes
    23 Posts
    4k Views
    B
    @mohkhalifa said in pfSense on ESXi | Best Practices: problem SOLVED after "Disabling hardware checksum offload" Awesome. I poked around on a few of mine and didn't find any with that enabled. Mostly Dell hardware here. Good find.
  • 0 Votes
    6 Posts
    701 Views
    stephenw10S
    Are the IP addresses you are using both public IPs? What address are you testing from? Something in the same subnet? Can you connect out from the console from the new address? Ping, say, both 8.8.8.8 and google.com? Steve
  • 0 Votes
    5 Posts
    1k Views
    stephenw10S
    Do you have a switch between the modem and pfSense? I would expect power cycling the modem to restore the connection if ifconfig donw/up works. Steve
  • 0 Votes
    1 Posts
    512 Views
    No one has replied