I've noticed something strange with the Wireless Security feature; if one reboots the Astaro unit (or shuts it down, it loses power, etc.), and a Windows 7 laptop reconnects (automatically) to the Wireless Network, Windows 7 keeps identifying the wireless network as a "new" one, and asks the end user to select whether it's a Home, Work, or Public network. This was not an issue before when using a standalone WAP (non astaro) behind the ASG. The client I'm testing with even has a static IP assignment in DHCP.
Windows matches the locally saved MAC address of the Default Gateway at every link establishment. If the MAC address of the Default Gateway changed, Windows reports a new network has been discovered.
The WiFi feature internally uses RED which works with random generated MAC addresses on every initialization. That is causing the trouble.
Windows matches the locally saved MAC address of the Default Gateway at every link establishment. If the MAC address of the Default Gateway changed, Windows reports a new network has been discovered.
The WiFi feature internally uses RED which works with random generated MAC addresses on every initialization. That is causing the trouble.
Ah... that explains it. Would probably be a good idea to change this in the RED too, as I'm sure the changing MAC addresses would have the same effect, say, for a mobile user that goes from site to site connected via RED.
CTO, Convergent Information Security Solutions, LLC
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
