Comments
-
Got a cased logged, been passed over to 2nd line, will post the issue and hopefully the fix. Cheers for your help Bruce, seems you live on here, If you don't work for watchguard they should be paying you. Cheers Gary
-
Sorry subnet is / 16, got carried away
-
Bruce, Vlan 3 is on a optional zone, with a IP address of 10.75.0.103, dhcp is disabled as the AP provides them, that is assigned to eth0 where only Vlan 3 is selected, and send / receive tagged traffic for vlan is ticked. Gary
-
The only place 10.75.0.77 is listed is in the DHCP pool on the AP Cloud settings, it assigned that address to a device that is connected to the SSID with that pool, that SSID has a vlan id of 3, tagged on the switch, and then tagged on the firewall interface it's plugged into, traffic seems to get to the firewall, but then…
-
Ok, Sorted the managed side of it, getting traffic from the cloud managed AP to the firebox, but now I get the following logged on the firebox, Tried adding to allowed sites, the IP is a DHCP one assigned from the Cloud AP, seems it's trying to resolve to google's dns server, but thinks it's spoofed. 2020-10-08 10:41:10…
-
Cheers Bruce, Figured out the Vlan against interface after I posted, I have a management Vlan for my other AP's that are managed by the firebox, but as soon as you convert the AP to a cloud managed one, you lose the ability on the AP to assign anything against the IP it assigns itself, unless I am missing something. Cheers…
-
Getting closer, I have the Vlan of one of my SSID's on the Ap120 set up on the switch and tagged on the port the AP plugs into, now, how does the firebox know which vlan ID to look for, is that done as a seperate vlan in network configuration or in the gateway access controller. Also as the port is tagged for the SSID on…
-
Cheers Bruce, We are moving away from our physical fireboxes to go to a virtual cloud one, hence the need to move the AP's to the cloud, I will setup a Vlan on my switches now and see how far I get. Gaz
-
Thank you James. Gary