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

    LAN has no connectivity

    Scheduled Pinned Locked Moved Firewalling
    20 Posts 3 Posters 909 Views 3 Watching
    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.
    • T Offline
      toddehb @johnpoz
      last edited by

      @johnpoz

      Well, expressed myself a little confusing. Not I enabled NAT, the system did as shown in the screenshot "auto created rule"

      johnpozJ T 2 Replies Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator @toddehb
        last edited by johnpoz

        @toddehb what is your wan IP on your pfsense, its not a 10.x address itself is it?

        What I would do is sniff on your pfsense wan while you pinging from this client to say 8.8.8.8 do you see that traffic going out your pfsense wan?

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1

        1 Reply Last reply Reply Quote 0
        • T Offline
          toddehb @toddehb
          last edited by

          @toddehb said in LAN has no connectivity:

          @johnpoz

          Well, expressed myself a little confusing. Not I enabled NAT, the system did as shown in the screenshot "auto created rule"

          no, look at the screen witch icmp packets. I obfuscated the ip a little bit

          T 1 Reply Last reply Reply Quote 0
          • T Offline
            toddehb @toddehb
            last edited by

            @toddehb

            Did a capture on LAN interface. Looks good to me

            14:06:35.533408 STP 802.1w, Rapid STP, Flags [Learn, Forward], bridge-id 4000.ec:13:db:42:a3:02.83fd, length 43
14:06:36.951555 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 1, length 64
14:06:36.952826 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 1, length 64
14:06:37.482424 STP 802.1w, Rapid STP, Flags [Learn, Forward], bridge-id 4000.ec:13:db:42:a3:02.83fd, length 43
14:06:37.965989 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 2, length 64
14:06:37.967227 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 2, length 64
14:06:38.990013 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 3, length 64
14:06:38.994021 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 3, length 64
14:06:39.347396 STP 802.1w, Rapid STP, Flags [Learn, Forward], bridge-id 4000.ec:13:db:42:a3:02.83fd, length 43
14:06:39.582728 IP 10.16.0.173.58226 > 4.2.2.1.53: UDP, length 50
14:06:39.582754 IP 10.16.0.173.58226 > 4.2.2.1.53: UDP, length 50
14:06:39.587955 IP 4.2.2.1.53 > 10.16.0.173.58226: UDP, length 113
14:06:39.589825 IP 4.2.2.1.53 > 10.16.0.173.58226: UDP, length 113
14:06:39.629909 ARP, Request who-has 10.16.0.172 tell 10.16.0.173, length 46
14:06:39.629917 ARP, Reply 10.16.0.172 is-at 00:22:1f:67:ee:4b, length 28
14:06:40.014032 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 4, length 64
14:06:40.014877 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 4, length 64
14:06:41.037968 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 5, length 64
14:06:41.038966 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 5, length 64
14:06:41.183358 STP 802.1w, Rapid STP, Flags [Learn, Forward], bridge-id 4000.ec:13:db:42:a3:02.83fd, length 43
14:06:42.061955 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 6, length 64
14:06:42.062820 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 6, length 64
14:06:43.085975 IP 10.16.0.173 > 8.8.8.8: ICMP echo request, id 15, seq 7, length 64
14:06:43.086910 IP 8.8.8.8 > 10.16.0.173: ICMP echo reply, id 15, seq 7, length 64
14:06:43.118359 STP 802.1w, Rapid STP, Flags [Learn, Forward], bridge-id 4000.ec:13:db:42:a3:02.83fd, length 43
            V johnpozJ 2 Replies Last reply Reply Quote 0
            • V Offline
              viragomann @toddehb
              last edited by

              @toddehb
              So the responses go out on LAN properly to the VM IP.

              Check if the IP has the correct MAC in pfSense ARP table in Diagnostic > ARP.
              Otherwise I can only imagine that there goes something wrong on HyperV.

              1 Reply Last reply Reply Quote 0
              • johnpozJ Offline
                johnpoz LAYER 8 Global Moderator @toddehb
                last edited by

                @toddehb so what is not working - looks like both your pings are working from that trace. I see both a ping reply from 8.8.8.8 and dns reply from the 4.2.2.1 etc.

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1

                T 1 Reply Last reply Reply Quote 0
                • T Offline
                  toddehb @johnpoz
                  last edited by

                  @johnpoz said in LAN has no connectivity:

                  @toddehb so what is not working - looks like both your pings are working from that trace. I see both a ping reply from 8.8.8.8 and dns reply from the 4.2.2.1 etc.

                  The console is not showing any output when pinging. NSLOOKUP does not lookup and apt update eg. is not working. The system does not seem to have internet conenction.

                  johnpozJ 1 Reply Last reply Reply Quote 0
                  • johnpozJ Offline
                    johnpoz LAYER 8 Global Moderator @toddehb
                    last edited by

                    @toddehb but from your sniff pfsense is sending on the reply to your ping and to your dns query.

                    So whatever the problem isn't a pfsense issue, it did what you asked, it sent on your ping and dns.. And when it got a reply it sent it back to the client that asked..

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      toddehb @johnpoz
                      last edited by

                      @johnpoz said in LAN has no connectivity:

                      @toddehb but from your sniff pfsense is sending on the reply to your ping and to your dns query.

                      So whatever the problem isn't a pfsense issue, it did what you asked, it sent on your ping and dns.. And when it got a reply it sent it back to the client that asked..

                      Yes, but cannot figure out what is going wrong. Did a reinstall on that VPS, same issue. Will contact support of Hoster. Maybe they know what is going on

                      T 1 Reply Last reply Reply Quote 0
                      • T Offline
                        toddehb @toddehb
                        last edited by

                        @toddehb

                        Just want to update all on the solution. My hoster had some ebtable rules active which were actively blocking the traffic. They disbaled them and now everything is going smooth :👍

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