EdgeRouterX and UISP Network Management

  • 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.)

bhelman

Member
Jan 7, 2021
13
0
I'm using the EdgeRouterX essentially as a layer 2 device:

Gbs Internet ONT --> EdgeRouterX Interface 1/Interface 2 ---> Home Router
100Mbs Internet Modem --> EdgeRouterX Interface 3/Interface 4 ---> Home Router
EdgeRouterX Interface 5 (management) ---> Home Router

Interfaces 1, 2 are in a layer 2 VLAN
Interfaces 3, 4 are in a different layer 2 VLAN
Interface 5 is in a 3rd VLAN

Interface 5 has an IP address (for management)

I then have an Ubuntu (ESXi) VM running the Ubiquiti UISP software. It monitors the EdgeRouterX and gives me nice graphs to show me my Internet throughput. It also lets me see if my backup Internet (100Mbs) kicks in.

Both (UISP and ERX) are running the most recent code/firmware (as of 1/1/2023).

Before the last ERX firmware my UISP instance would lose connection to the ERX. Pinging the ERX from the same VM would continue, but increase from about .3ms to upward of 80+ms. At the same time, pings to Google's DNS would remain steady (around 18ms).

I also have UISP "monitoring" (ping only) my home router. It never gets reported by UISP as down. Also, traffic never stops flowing across the ERX.

I was hoping the firmware upgrade would fix this, but now that I'm on the latest, it isn't any better.

Is anyone using an NMS against their ERX?

Thoughts?
 
The ERX is really quite under powered by most accounts. You're probably pushing it harder than it wants to go. If you're stuck on Ubiquity products, try a more powerful router?
 
Upvote 0
There may be a power saving mode in one of your devices which puts the NIC to sleep if it is not used for xx minutes. It could be worth checking what settings are available.
 
Upvote 0