Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 46 subscribers
  • Views 39922 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP Static IP mapping for same client multiple networks?

KyleK

I have two networks setup that are vlan tagged and on a LAG interface. I have a client that can connect to both of those networks and would like to assign a static IP address to that client on both networks. Initially I assigned a static IP address in the DHCP options on the one network but then noticed whenever the client tried to connect to the second network they would receive no DHCP lease. Looking through the forums I found the option "system dhcp static-entry-scope global" which alleviated this problem. However I am still unable within the web interface to assign the same MAC on multiple networks in the DHCP "Static IP MAC Mapping". It works fine on one of the networks but then when I try it on the second I receive: "DHCP Configuration with the same hostname/MAC address/DUID address already exists, choose a different hostname/MAC address/DUID address"

Is this a limitation or is there another shell command I need to run to enable this?


Appreciate the help.



This thread was automatically locked due to age.
Parents
  • 0
    Dear all,

    I have the same issue.
    In my case i get the static IP assigned in DHCP settings of VLAN 1 also in VLAN 2 (different IP Network) instead of getting a free ip out of the dhcp range of vlan2.
    I`m also not able to create a second ip mapping for same MAC on DHCP of VLAN 2.

    BR,
    Jose
  • 0 in reply to mjoschi

    I'm seeing this same behavior.

    Port1 (native VLAN) is assigning IP addresses from the proper DHCP pool to my "normal" SSID, which is untagged, same VLAN as the XGFW Port1.

    Port1.200 (VLAN 200) is not assigning IP addresses from correct subnet.  It's assigning from the DHCP pool for the native VLAN.

    There is no setting I can find to map the DHCP pool to the Port1.subinterface correctly.

    This means that guest traffic is co-mingled with the LAN, and no bandwidth rules are working.

    This is a huge security risk, as well as a fine way to eat up bandwidth by multiple guests using YouTube at HD resolution.

Reply
  • 0 in reply to mjoschi

    I'm seeing this same behavior.

    Port1 (native VLAN) is assigning IP addresses from the proper DHCP pool to my "normal" SSID, which is untagged, same VLAN as the XGFW Port1.

    Port1.200 (VLAN 200) is not assigning IP addresses from correct subnet.  It's assigning from the DHCP pool for the native VLAN.

    There is no setting I can find to map the DHCP pool to the Port1.subinterface correctly.

    This means that guest traffic is co-mingled with the LAN, and no bandwidth rules are working.

    This is a huge security risk, as well as a fine way to eat up bandwidth by multiple guests using YouTube at HD resolution.

Children
Unfiltered HTML