Router WAN Management over HTTPS

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Oct 27, 2023
6
0
In light of Steve's reminder this last Tuesday during podcast 945, I'm curious how the gang feels about my solution to permitting WAN management in a secure manner. I work on the networking team for a larger enterprise, about 50 sites. Each site has a connection to the internet and a commercial class firewall. We have a mesh of site-to-site VPNs and use OSPF to dynamically route traffic on the enterprise LAN. We do have a client VPN solution which terminates to a datacenter and depending on the user can route through the enterprise network as needed.

WAN management is something we use frequently for these firewalls, but agreed early on that leaving this open to the entire public internet was not good. So we signed up with a No-IP account and gave our networking team each a dynamic FQDN. For example, netadmin1.domain.com. We then created address-objects and firewall policy disabling WAN management but allowing these dynamic FQDNs. We also hard coded a few WAN IPs for main sites in the event that DNS went sideways. Each network admin has the no-ip software running on their corporate computer so they are able to access WAN management from anywhere they may be working from. Assuming the firewall has had adequate time to perform a fresh lookup of their assigned FQDN.

This seems to work for us and still maintains security. We get real-time alerts anytime there is a bad username and password attempt. Bad idea?

Regards,
Adam Tyler
 
I'm a big believer in opening local ports only to specific remote IPs. I do that myself. I have pfSense firewalls which have Dynamic DNS client services running. Thus, those domains are kept synchronized with their ISP-assigned IPs. Granted those IPs don't change often... but when they do the firewall rules automatically re-synchronize to continue to permit access.
 
  • Like
Reactions: Adam-TheMan-Tyler