You wouldn't want guest accessing your LAN (printers and servers). Third time is a charm! Sometimes a loose cable is all it takes to lose internet access. When you bridge the wireless network, the wireless users are in the same security zone as other users on the bridge network, and the traffic for these mobile users is handled by the same security policies as traffic for other users on the bridged network. Do you own that address space? Last step is to add the wireless network to the bridge. It does sound like the point where our support should help, and they will probably want a copy of your config to check things our. The rest of my setup closely mirrored yours. Also, I would not make VLAN1 as the guest. This person is a verified professional. *make sure to use a network address for Wireless Guest Network... not a host address (for example, x.x.x.0. The WatchGuard wireless Firebox supports two different frequency bands, 2.4 GHz and 5 GHz.

That said, I did a quick search of our own WatchGuard support forum, and I found a thread about a similar issue: Because most wireless clients are not VLAN-capable, you can configure the VLAN as untagged.If you do not configure an untagged VLAN for this interface, clients which are not configured to use a selected VLAN will be unable to use this wireless network. Sorry I have not replied - had somethings come up over the holidays that demanded my attention. I contacted WatchGuard's tech support number and spoke to a rep, who listened to my issues, then told me I would have to be transferred to tech support. (do you have a reseller like cdw that you work with? Saw the last few posts in the last few days. How about a reset to factory defaults and then reconfigure the device? To continue this discussion, please For more information, see You can configure any access point as a wireless guest network. Users will be able to connect to the SSID, but will not be able to send or receive data.Computers that connect to the custom network connect through the wireless Firebox to You can enable wireless clients to connect to the wireless device as part of the trusted network or part of the optional network. This option is disabled by default. @jaylee - when you go for the Bridge option, the Eth1 and Wireless AP1 will be bridged, like they were on a switch. She did mention if I wanted a guaranteed call back within one hour, I could pay $195 per incident! This can result in some client authentication connections to fail and be reestablished. I am going to have to call in an outside consultant I guess, and I may have to eat the cost. For more information on how to create a network bridge, see When you configure a wireless interface with the interface type of If you want your wireless users to be on the same network as your wired optional network, you must use a network bridge between the wireless interface and the optional wired interface. I am going to turn it off since it is not really needed for us. I have configured the a regular wireless network with no issues and it is running DHCP. I believe I tried that awhile back, but not sure. I tried the guest wireless AP, but still can't get to Internet. port 15 on switch A: port configured in access mode for VLAN3 untagged When this happens, your router will work on your network but since it can't reach the internet, it won't have a valid public … This topic has been locked by an administrator and is no longer open for commenting. Unfortunately it did not work. enabled  "prohibit client to client wireless network traffic" I do not see any policies that would apply directly to the guest network. All users who access this private network can access the outside internet. This is because the problem isn't with your connection to the router but with your router's connection to your ISP.. For more information, see For detailed instructions on how to bridge a wireless interface to the trusted interface, see the You can configure the wireless network as a VLAN interface to connect wireless clients to a configured VLAN within your network. If you do own 134.0.x..x, and are intentionally using it that way with public addressing, ignore this.