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

    pfSense won't ping LAN device

    Scheduled Pinned Locked Moved Virtualization
    8 Posts 2 Posters 1.1k 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.
    • E
      eiger3970 0
      last edited by

      Hello, I have a home virtual pfSense router which pings its host and LAN devices, however is unable to ping 1 LAN device for some reason.
      The LAN device in question appears to have the correct settings of
      IP: 192.168.1.110
      Subnet Mask: 255.255.255.0
      Router: 192.168.1.1701.1.1.1
      DNS Server: 8.8.8.8, 8.8.4.4, 192.168.1.170, 1.1.1.1
      alt text
      alt text
      Network topology
      Network topology detailed

      E V 2 Replies Last reply Reply Quote 0
      • E
        eiger3970 0 @eiger3970 0
        last edited by

        @eiger3970-0
        Host computer Terminal:

        linuxmint@linuxmint:~$ ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:ca:06:f0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.120/24 brd 192.168.1.255 scope global noprefixroute br0
       valid_lft forever preferred_lft forever
    inet6 fe80::1e61:b4ff:fe6d:384f/64 scope link 
       valid_lft forever preferred_lft forever
6: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:09:d3:92 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe09:d392/64 scope link 
       valid_lft forever preferred_lft forever
7: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:ac:44:b5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:feac:44b5/64 scope link 
       valid_lft forever preferred_lft forever
8: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:a1:d1:e2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fea1:d1e2/64 scope link 
       valid_lft forever preferred_lft forever

        Virtual pfSense router terminal:

        [2.7.2-RELEASE][root@pfSense.home.arpa]/root: ifconfig
vtnet0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: LAN
	options=800b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE>
	ether 52:54:00:09:d3:92
	inet 192.168.1.170 netmask 0xffffff00 broadcast 192.168.1.255
	inet6 fe80::5054:ff:fe09:d392%vtnet0 prefixlen 64 scopeid 0x1
	media: Ethernet autoselect (10Gbase-T <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: WAN
	options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether a8:a1:59:6e:1f:8b
	inet 100.76.25.213 netmask 0xffc00000 broadcast 100.127.255.255
	inet6 fe80::aaa1:59ff:fe6e:1f8b%re0 prefixlen 64 scopeid 0x2
	media: Ethernet autoselect (1000baseT <full-duplex,master>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
enc0: flags=0 metric 0 mtu 1536
	options=0
	groups: enc
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet 127.0.0.1 netmask 0x0
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=100<PROMISC> metric 0 mtu 33152
	options=0
	groups: pflog
pfsync0: flags=0 metric 0 mtu 1500
	options=0
	maxupd: 128 defer: off version: 1400
	syncok: 1
	groups: pfsync
ovpns1: flags=1008043<UP,BROADCAST,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=80000<LINKSTATE>
	inet 10.0.8.1 netmask 0xffffff00 broadcast 10.0.8.255
	inet6 fe80::aaa1:59ff:fe6e:1f8b%ovpns1 prefixlen 64 scopeid 0x7
	groups: tun openvpn
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	Opened by PID 35746
        1 Reply Last reply Reply Quote 0
        • V
          viragomann @eiger3970 0
          last edited by

          @eiger3970-0
          Post the network settings and the routing table of the machine in question.

          E 1 Reply Last reply Reply Quote 1
          • E
            eiger3970 0 @viragomann
            last edited by

            @viragomann Sorry, the share link failed.
            These share links hopefully show the machine in question
            Terminal top half and Ethernet configuration
            Terminal bottom half

            E 1 Reply Last reply Reply Quote 0
            • E
              eiger3970 0 @eiger3970 0
              last edited by eiger3970 0

              @eiger3970-0 Sorry, looks like that file sharing link is too slow also.
              Here's the links with another image sharing platform:
              Terminal top half and Ethernet configuration
              Terminal bottom half

              E 1 Reply Last reply Reply Quote 0
              • E
                eiger3970 0 @eiger3970 0
                last edited by

                @eiger3970-0 Here's another screenshot
                Internet pings for 71 icmp_seqs, then stops.

                V 1 Reply Last reply Reply Quote 0
                • V
                  viragomann @eiger3970 0
                  last edited by

                  @eiger3970-0
                  When the machine says "no route to host" regarding a public IP, I assume, it also cannot access its default gateway.

                  Does its network settings change, when the issue appears?
                  Maybe something in the logs?

                  A reason for that could be, that another machine uses the same IP.
                  If this is the case you should see some ARP lines in the pfSense system log, complaining that the IP moves from one IP to another.

                  E 1 Reply Last reply Reply Quote 1
                  • E
                    eiger3970 0 @viragomann
                    last edited by

                    @viragomann The machine's Ethernet is set to a static IP 192.168.1.110/24 gateway 192.168.1.170.
                    The Wi-Fi is DHCP I guess?
                    I set up a new Network location on the machine and the Ethernet DHCP would not connect, so I switched back to the original network with the Ethernet static IP and it connected.
                    Guess I'll see how long it stays online until the problem returns.

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