NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

mwgmwg's avatar
mwgmwg
Aspirant
Jun 07, 2018

M4100 DHCP over VLAN eating packets

I have the following setup:

 

pfSense Firewall -> Cisco Switch (servers) -> Cisco Switch (users) -> M4100-D10e -> Cable Modem

 

The pfSense firewall does the routing and NAT and is VLAN aware.   I have VLAN's setup for internal users, and back-end servers, as well as untrusted internet.  The link beteween the M4100 and the Cisco switch is a VLAN trunk and needs to pass trusted and untrusted VLANs between it. The link between the cisco switches is also a vLAN trunk.

 

The trouble I have is, with the M4100 in place, DHCP REQUEST packets from pfSense are not making it to the Cable Modem.  If I replace the M4100 with a dumb media converter, and change the trunk to a port assigned to the untrusted vLAN, things work as expected.  With the M4100 in place, the cable modem seems to think that the it's Client is the M4100 (it tries to reserve an IP for the MAC of the port on the M4100)

 

The DHCP and ARP and Relay settings on the router are fairly confusing, so I think I need help figuring out which ones to set to allow it to pass the DHCP packets without trying to intercept them.

6 Replies

  • JohnC_V's avatar
    JohnC_V
    NETGEAR Employee Retired

    Hi mwgmwg,

     

    Welcome to our community! :)

     

    As per checking, your pfSense firewall is at the bottom of your network which should be next to your cable modem. Is this how you want your network to be setup? Also, Have you tried setting up the M4100 in static?

     

    Regards,

    • mwgmwg's avatar
      mwgmwg
      Aspirant

      The pfSense firewall cannot be physically located where the cable modem comes into the building. They are about 800 feet apart and connected via fiber.

       

      I have not tried setting it up in 'static', I'm not sure what that means exactly.  But I'm sure it would work if I can make the switch a dumb layer-2 switch with vlan support.

      • JohnC_V's avatar
        JohnC_V
        NETGEAR Employee Retired

        mwgmwg,

         

        Then you can just create a port-based VLAN in order for it to work. You can set all the specific members with U or Untag then set the PVID to its corresponding VLAN ID.

         

        Regards,

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More