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

    DHCP not working across bridge. Bridge has IP and dhcp server, physical interfaces have no IP or DHCP server.

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 398 Views 2 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.
    • R Offline
      ryanfelder
      last edited by

      Hi,
      I have been banging my head against this for about three days now.

      I have 3 interfaces, bridge0, vtnet1, vtnet2. The members of bridge0 are vtnet1 and vtnet2.

      If I assign an IP address to vtnet1 and enable a dhcp server there, I can get an IP on the device I have plugged into vtnet2.

      If I remove the IP address from vtnet1, disable the dhcp server on vtnet1, but put an IP and DHCP server on bridge0, I cannot get DHCP on the device on vtnet2.

      If I tcpdump bridge0, I can see the dhcp traffic. Why isn't the dhcp server responding to it?
      I have all/all/all/all rules on vtnet1, vtnet2, and bridge0. I have added specific UDP all/67-68/all/67-68 rules to all three interfaces after becoming desperate.

      tcpdump -i bridge0 -n port 67 and port 68
      tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
      listening on bridge4, link-type EN10MB (Ethernet), capture size 262144 bytes
      01:07:40.188954 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:9b:11:3a:53, length 300
      01:07:46.099678 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:9b:11:3a:53, length 300
      01:07:49.447344 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:9b:11:3a:53, length 300
      01:07:57.997038 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:9b:11:3a:53, length 300
      
      

      Oh, and interestingly, if I static my IP on the device plugged into vtnet2, I can ping my gateway and route out, so it seems to be broadcast traffic specific.

      I feel like I'm missing something simple here, but any help would definitely be appreciated.

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        What are the exact rules you have on each interface? And what are the current values of the tunables net.link.bridge.pfil_member and net.link.bridge.pfil_bridge?

        In a bridged setup the most optimal configuration has the bridge0 interface assigned with the IP address, DHCP server, and so on configured there.

        You will need special rules to pass DHCP but if your rules really are any source / any destination / any port that should cover them,

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • R Offline
          ryanfelder
          last edited by

          Honestly, I'm afraid I gave up after waiting a few days for a response.
          I now have the bridge set to no ip and the physical interface set with the ip.

          It's ugly, and it prevents some future configurations I wanted to have access to, but it works.

          1 Reply Last reply Reply Quote 0
          • R Offline
            ryanfelder
            last edited by ryanfelder

            And I got a developer response too, shit.

            I did, and do have pfil_member set to 0, and pfil_bridge set to 1.

            Rules were set to proto any, source any, dest any...
            I'll reattempt either tonight or in the next day or two with one of my unused physical interfaces and let you know.

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