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

[Solved] Problems with Proxmox/vlan-tagging/SG-2100 Switch config

Scheduled Pinned Locked Moved Official Netgate® Hardware
24 Posts 4 Posters 4.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.
  • F
    furom
    last edited by furom May 8, 2023, 4:07 PM May 8, 2023, 3:58 PM

    This is the config of one VM which won't get an IP on defined vlan (in fact no IP at all to be exact);
    54d52d6f-84a5-4026-83a4-1b207306feef-image.png
    And the Proxmox config;

    auto lo
    iface lo inet loopback
    
    iface eno1 inet manual
    
    auto vmbr0.22
    iface vmbr0.22 inet static
            address 192.168.22.2/28
            gateway 192.168.22.1
    
    auto vmbr0
    iface vmbr0 inet static
            bridge-ports eno1
            bridge-stp off
            bridge-fd 0
            bridge-vlan-aware yes
            bridge-vids 2-500
    

    Edit: I just now tried editing the last line, just specifying two vland id's, like "bridge-vids 30 44", but still refuse to work...

    What am I missing? I read and read and test, still not working. And I'm repeatedly told I won't need any rules for DHCP...

    R V 2 Replies Last reply May 8, 2023, 4:07 PM Reply Quote 0
    • R
      rcoleman-netgate Netgate @furom
      last edited by May 8, 2023, 4:07 PM

      @furom Do an unfiltered packet capture on the VLAN on pfSense (https://docs.netgate.com/pfsense/en/latest/diagnostics/packetcapture/index.html) and filter against UDP 68 with a limit of 0 packets and see if the traffic is even getting there... or if it is getting there and responding...

      I suspect the issue is in your PVE config

      Ryan
      Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
      Requesting firmware for your Netgate device? https://go.netgate.com
      Switching: Mikrotik, Netgear, Extreme
      Wireless: Aruba, Ubiquiti

      F 2 Replies Last reply May 8, 2023, 4:33 PM Reply Quote 1
      • F
        furom @rcoleman-netgate
        last edited by furom May 8, 2023, 4:41 PM May 8, 2023, 4:33 PM

        @rcoleman-netgate said in Problems with Proxmox/vlan-tagging/SG-2100 Switch config:

        @furom Do an unfiltered packet capture on the VLAN on pfSense (https://docs.netgate.com/pfsense/en/latest/diagnostics/packetcapture/index.html) and filter against UDP 68 with a limit of 0 packets and see if the traffic is even getting there... or if it is getting there and responding...

        I suspect the issue is in your PVE config

        Just so I get this right, I am supposed to do this from a VLAN that is not working, or from pfSense? I'm not used capturing other than quite simple tcpdumps, but will figure it out I hope :)

        Edit: I tried this from pfSense, and started a machine that should've requested an IP - nothing.

        [root@pfSense ~]# tcpdump -ni mvneta1.30 udp port 68
        
        R 1 Reply Last reply May 8, 2023, 4:52 PM Reply Quote 0
        • R
          rcoleman-netgate Netgate @furom
          last edited by May 8, 2023, 4:52 PM

          @furom the GUI in pfSense makes the PCAP easier... that's why I linked you to how to perform the packet capture in our documentation.

          Ryan
          Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
          Requesting firmware for your Netgate device? https://go.netgate.com
          Switching: Mikrotik, Netgear, Extreme
          Wireless: Aruba, Ubiquiti

          F 1 Reply Last reply May 8, 2023, 4:59 PM Reply Quote 1
          • F
            furom @rcoleman-netgate
            last edited by May 8, 2023, 4:59 PM

            @rcoleman-netgate Sorry. I used the GUI and I can see Proxmox trying something from its own GUI, I don't get anything in the PCAP....

            1 Reply Last reply Reply Quote 0
            • V
              viragomann @furom
              last edited by May 8, 2023, 5:02 PM

              @furom
              You have enabled the Firewall on the VMs virtual NIC. Did you also configure it properly to allow access?

              F 1 Reply Last reply May 8, 2023, 5:08 PM Reply Quote 0
              • F
                furom @viragomann
                last edited by furom May 8, 2023, 5:28 PM May 8, 2023, 5:08 PM

                @viragomann said in Problems with Proxmox/vlan-tagging/SG-2100 Switch config:

                @furom
                You have enabled the Firewall on the VMs virtual NIC. Did you also configure it properly to allow access?

                That is on by default I think, but turning it off makes no difference unfortunately, was hoping it would... Still not seeing any captured packets though. Something is quite weird. Even tried "promiscous" mode, leaving Port blank... That should show something, right?

                Edit: Only when I select WAN as interface I get some capture... :/ I don't get this. If I remove port and protocol I get some activity, but none on the one for Proxmox VM..

                Removing Port & protocol on vlan 30 on which I am trying to setup an ubuntu, this was all it captured;

                19:25:03.205680 IP 192.168.1.3 > 224.0.0.1: igmp
                19:26:03.820911 IP 192.168.1.3 > 224.0.0.1: igmp
                
                1 Reply Last reply Reply Quote 0
                • F
                  furom @rcoleman-netgate
                  last edited by May 8, 2023, 5:58 PM

                  @rcoleman-netgate said in Problems with Proxmox/vlan-tagging/SG-2100 Switch config:

                  @furom
                  I suspect the issue is in your PVE config

                  Agreed. With my limited knowledge of package capture and your help I think we can conclude that pfSense seems to do what it is supposed, right? It certainly looks as if PVE is not relaying anything to or from it's VMs...

                  I tried a laptop in a switch port for the same VLAN I set for the VM, and although it per definition is getting it untagged, the DHCP server responds as it should...

                  V 1 Reply Last reply May 8, 2023, 7:25 PM Reply Quote 0
                  • V
                    viragomann @furom
                    last edited by viragomann May 8, 2023, 7:26 PM May 8, 2023, 7:25 PM

                    @furom said in Problems with Proxmox/vlan-tagging/SG-2100 Switch config:

                    I tried a laptop in a switch port for the same VLAN I set for the VM, and although it per definition is getting it untagged,

                    The switch port, which is connected to Proxmox is a trunk with tagged VLANs as I understood so far.
                    If so and you connect a device to it, you have to configure its NIC for VLAN.

                    Can you post your interface settings of pfSense, please?
                    Status > Interfaces

                    Which interface did you run the packet capture?

                    F 1 Reply Last reply May 9, 2023, 6:11 AM Reply Quote 1
                    • F
                      furom @viragomann
                      last edited by May 9, 2023, 6:11 AM

                      @viragomann said in Problems with Proxmox/vlan-tagging/SG-2100 Switch config:

                      @furom said in Problems with Proxmox/vlan-tagging/SG-2100 Switch config:

                      I tried a laptop in a switch port for the same VLAN I set for the VM, and although it per definition is getting it untagged,

                      The switch port, which is connected to Proxmox is a trunk with tagged VLANs as I understood so far.
                      If so and you connect a device to it, you have to configure its NIC for VLAN.

                      Can you post your interface settings of pfSense, please?
                      Status > Interfaces

                      Which interface did you run the packet capture?

                      I got it working (!) while composing the answer to you! Thanks a lot!! It turned out to be a misconfiguration on the 2100-switch after all, I had not added the vlan to the port I am using... Having done that it now works as it is supposed to. This feels really great, and I am sorry for all the trouble, but very grateful for such a great forum and to all that has tried (and) helped!

                      Thanks !

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