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

Red 15w and Standard/Split

I would like to get 100% confirmation that this either works or does not work. Based on reading this board and articles posted in the KB I cannot find a definitive answer. I see some issues from back in 2016 but cannot determine if they were ever resolved.

Setup:

XG firewall running 17.5.8

Red 15w: 10.100.100.1/26, DHCP relay to Windows DHCP server with 234 option set pointing to the FW. Standard/Split

Hardwired ports all work in this setup perfectly. Internet traffic goes out and LAN traffic stays in.

Built-In wireless is not working. I was able to register the "internal" AP the first time around with Standard/Unified.
Changing that to Standard/Split no longer sees the internal AP on the Red 15w. It does not get an address from the DHCP server or show up in the pending access points. At first, I thought it might be because of the DHCP server and not being able to relay. So, I changed it to the XG handling the DHCP requests. Still nothing. I have researched a bit into bridge-to-LAN but have not found a way to get that to work with the Red 15w.

Big question:

Is it possible to have an XG and Red 15w operate with a DHCP relay/XG DHCP in Standard/Split mode that includes both the physical ports and the WIFI?

 

Another option I am considering is a base model Red and an AP 15.

Any suggestions would be greatly appreciated.



This thread was automatically locked due to age.
  • Hi  

    Your scenario is possible under the Standard/Split configuration.

    Could you please provide the below details?

    1. Make sure that the DHCP lease range for RED should not be conflicted with other Interface IP range

    2. Please share the output of the below given command, please take SSH access of the XG console and Advanced shell.

    tcpdump -nei reds1

  • 1. I am not sure what you mean by other interface. The DHCP range for the Red is 10.100.100.10-60. That DHCP range is served up via relay from a Windows server. Separate DHCP is served for each Red.

    2. Here is the output from the device in question:

    08:52:25.513867 reds7, IN: 00:1a:8c:95:5d:a4 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 346: vlan 1300, p 0, ethertype IPv4, 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:1a:8c:95:5d:a4, length 300

    It repeats at regular intervals (as expect when looking).

  • One note: That is with it in standard/unified mode.

  • Hi 

    Thank you for providing details.

    I would request you to contact technical support and open a service request to investigate the issue further, This should work with the scenario you want to achieve. Please contact technical support and they will resolve the issue further. Please PM us the service request number.

  • I sent the PM and eagerly awaiting the response to all three items currently open.

  • Further testing . . .

    This line/log

    08:52:25.513867 reds7, IN: 00:1a:8c:95:5d:a4 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 346: vlan 1300, p 0, ethertype IPv4, 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:1a:8c:95:5d:a4, length 300

    vlan 1300 should not be part of that request. No matter what changes I make to the device, it continues to hold onto that vlan 1300. I have no vlan configured for that device that references any vlan 1300.

    How do I clean that up from the Red?