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

    VLAN troubles, trouble connecting from VLAN 10 to LAN, others work.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    16 Posts 3 Posters 1.5k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Most likely the proxmox server has no route or a bad route to 192.168.10.X. Or it has a firewall running on it blocking access from that subnet.
      Can you ping out from Proxmox to anything in VLAN10?

      Steve

      D 1 Reply Last reply Reply Quote 0
      • D
        davidg1982 @stephenw10
        last edited by davidg1982

        @stephenw10 I cannot ping anything from Promox to VLAN 10. I can ping from Proxmox to VLAN 20. Proxmox can ping the LAN gateway. How would I diagnose bad routes?

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

          Look at its routes... It really should only have the default I would think.

          When you do a traceroute does its actually send the traffic to pfsense... Or does it maybe think that network is local to it?

          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 24.11 | Lab VMs 2.8, 24.11

          1 Reply Last reply Reply Quote 0
          • D
            davidg1982
            last edited by davidg1982

            Proxmox Routes:

            pve:~$ sudo route
            Kernel IP routing table
            Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
            default         192.168.0.1     0.0.0.0         UG    0      0        0 vmbr1
            192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 vmbr1
            
            

            Zabbix Routes:

            zabbix ~# route
            Kernel IP routing table
            Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
            default         192.168.10.1    0.0.0.0         UG    0      0        0 eth0
            192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
            
            

            webserver routes on VLAN20:

            # route
            Kernel IP routing table
            Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
            default         192.168.20.1    0.0.0.0         UG    0      0        0 eth0
            192.168.20.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
            

            Proxmox traceroute to 192.168.10.4:

            david@pve:~$ sudo traceroute 192.168.10.2
            traceroute to 192.168.10.2 (192.168.10.2), 30 hops max, 60 byte packets
             1  192.168.0.1 (192.168.0.1)  0.312 ms  0.341 ms  0.472 ms
             2  * * *
             3  * * *
             4  * * *
             5  * * *
             6  * * *
            

            Zabbix traceroute to 192.168.0.2

            zabbix ~# traceroute 192.168.0.2     
            traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
             1  192.168.10.1 (192.168.10.1)  0.437 ms  0.455 ms  0.526 ms
             2  * * *
             3  * * *
             4  * * *
             5  * * *
            

            web server on VLAN20 to 192.168.0.2

            :~# traceroute 192.168.0.2
            traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
             1  192.168.20.1 (192.168.20.1)  0.396 ms  0.424 ms  0.458 ms
             2  192.168.0.2 (192.168.0.2)  1.305 ms  1.307 ms  1.327 ms
            
            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Hmm, looks OK.

              I'd run packet captures on the interfaces in pfSense whist trying to ping between the hosts. See exactly what is arriving an leaving.

              Steve

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

                Yeah maybe your mask is wrong on the box your trying to ping... Your multiple vlans getting confusing..

                Lets just deal with the vlan talking to the other vlan

                You hit the right first hop and then nothing..

                Ok then sniff on the other vlan or the client do you see the ping? Does the dest IP your trying to ping have the correct /24 mask?

                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 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 0
                • D
                  davidg1982
                  last edited by

                  Looks like all the machines have /24 operating.
                  Here is what the ICMP looks like from the LAN side with packet sniffing.

                  13:54:18.518924 52:5c:ff:1f:67:44 > 32:e8:8d:67:76:e5, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 25026, offset 0, flags [DF], proto ICMP (1), length 84)
                      192.168.0.2 > 192.168.10.4: ICMP echo request, id 25888, seq 1, length 64
                  

                  Does it come out the other side? Nope. Nothing comes out to VLAN10.

                  Same way in reverse.

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

                    So these are all vlan tagged on pfsense and just 1 vitrual nic em1.. Why would you not do the vlans in your vm hosting software..

                    Makes no sense that pfsense would get a packet and not send it somewhere..

                    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 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • D
                      davidg1982
                      last edited by davidg1982

                      Exactly. I don't understand why it wouldn't route it. Yep, here is my config on the proxmox. There has to be something I am missing.
                      Well..I am. Doing VLANs this way is recommended by Proxmox. Read up more here: link

                      auto lo
                      iface lo inet loopback
                      
                      allow-ovs vmbr0
                      
                      allow-vmbr0 eno1
                      iface eno1 inet manual
                              ovs_type OVSPort
                              ovs_bridge vmbr0
                      
                      auto vmbr0
                      iface vmbr0 inet manual
                              ovs_type OVSBridge
                              ovs_ports eno1
                      
                      auto vmbr1
                      iface vmbr1 inet static
                              address  192.168.0.2
                              netmask  255.255.255.0
                              gateway  192.168.0.1
                              ovs_type OVSBridge
                              ovs_ports vlan10 vlan20 vlan30 vlan40
                      
                      allow-vmbr1 vlan10
                      iface vlan10 inet manual
                              ovs_type OVSIntPort
                              ovs_bridge vmbr1
                              ovs_options tag=10
                      
                      allow-vmbr1 vlan20
                      iface vlan20 inet manual
                              ovs_type OVSIntPort
                              ovs_bridge vmbr1
                              ovs_options tag=20
                      
                      allow-vmbr1 vlan30
                      iface vlan30 inet manual
                              ovs_type OVSIntPort
                              ovs_bridge vmbr1
                              ovs_options tag=30
                      
                      allow-vmbr1 vlan40
                      iface vlan40 inet manual
                              ovs_type OVSIntPort
                              ovs_bridge vmbr1
                              ovs_options tag=40
                      
                      
                      1 Reply Last reply Reply Quote 0
                      • D
                        davidg1982
                        last edited by

                        I should point out that I have a plex machine setup with a NAT for VLAN10. So, it's accessible from WAN.

                        1 Reply Last reply Reply Quote 0
                        • D
                          davidg1982
                          last edited by

                          PFSense Routes. Scrubbed of some public information.

                          IPv4 Routes
                          Destination		Gateway	Flags	Use	Mtu	Netif	Expire
                          default			WAN GATEWAY	UGS	1058841	1500	em0	
                          10.1.0.0/24		10.1.0.2	UGS	1746	1500	ovpns1	
                          10.1.0.1		link#11	UHS	0	16384	lo0	
                          10.1.0.2		link#11	UH	0	1500	ovpns1	
                          10.41.10.9		link#13	UH	3615	1500	ovpnc3	
                          10.41.10.10		link#13	UHS	0	16384	lo0	
                          10.72.10.5		link#12	UH	3632	1500	ovpnc2	
                          10.72.10.6		link#12	UHS	0	16384	lo0	
                          WAN IP/29		link#1	U	3640	1500	em0	
                          WAN ANOTHER IP		link#1	UHS	0	16384	lo0	
                          WAN ANOTHER IP		link#1	UHS	0	16384	lo0	
                          WAN ANOTHER IP 		link#1	UHS	0	16384	lo0	
                          127.0.0.1		link#4	UH	118	16384	lo0	
                          192.168.0.0/24		link#2	U	5068	1500	em1	
                          192.168.0.1		WAN GATEWAY	UGHS	0	1500	em0	
                          192.168.10.0/24		link#7	U	396258	1500	em1.10	
                          192.168.10.1		link#7	UHS	0	16384	lo0	
                          192.168.20.0/24		link#8	U	74842	1500	em1.20	
                          192.168.20.1		link#8	UHS	0	16384	lo0	
                          192.168.30.0/24		link#9	U	0	1500	em1.30	
                          192.168.30.1		link#9	UHS	0	16384	lo0	
                          192.168.40.0/24		link#10	U	3	1500	em1.40	
                          192.168.40.1		link#10	UHS	0	16384	lo0	
                          
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by stephenw10

                            Normally I would look for policy based routing here. You don't have a gateway set in any of the rules shown above but you could have floating rules or an interface group passing that traffic and sending it out the WAN.

                            You might also have an IPSec VPN grabbing that traffic.

                            Steve

                            1 Reply Last reply Reply Quote 1
                            • D
                              davidg1982
                              last edited by

                              Ah.......it wasn't DNS this time, but it was IPSEC. It was some pesky IPSEC that wasn't fully enabled, only enabled on one side.
                              A few months ago I was going to setup some IPSEC stuff but gave up on it' I guess I never disabled it. I went ahead and disabled my half-assed IPSEC and now it's working.
                              I want to thank everyone for their help. Appreciate it. This was a tough one for me.

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