Specifications

the EtherIP tunnels therefore other clients will not see the traffic and not be able to see file and printer
shares. In order to send broadcast traffic back out the EtherIP tunnels the following routes must be added
under network>routing table>create static route entry for the appropriate managed interface.
Broadcast Traffic
Route Destination
192.168.160.255
Route Gateway
255.255.255.255
Netmask
255.255.255.255
Interface
Managed
This above example assumes we are referring to the managed physical network and the subnet is
192.168.160.0/24. If this is a managed vlan the Interface entry should be populated with the appropriate
managed vlan.
You may also be required to allow services in the firewall policy of the appropriate role. For example
TCP port 139 and UDP port 137,138 for NetBIOS and TCP 445 for SMB.
WARNING. Configuring this broadcast route in networks with large broadcast domains/subnets
may cause performance issues.
Unable to Transparent Proxy HTTPS on BSC
We have Transparent Proxy enabled in the role with the appropriate proxy server:port and HTTP ports to
proxy on the BSC. We are unable to transparently proxy HTTPS. We tried to add port 443 to the list of
HTTP ports but received the following error:
"HTTPS (443) is an encrypted protocol and cannot be transparently proxied."
Why can't I transparently proxy HTTPS?
Transparent proxy does not support HTTPS traffic. You cannot transparently proxy HTTPS as a nature of
the HTTPS protocol. This would be considered a man in the middle type of attack.
Users that are inactive or have gone out of wireless range for some period of time are getting
dropped from active connections of the BSC and have to re-authenticate.