| |||||||||||||
The CoDel queue management algorithmThe CoDel queue management algorithmPosted May 30, 2012 14:50 UTC (Wed) by TomH (subscriber, #56149)In reply to: The CoDel queue management algorithm by nye Parent article: The CoDel queue management algorithm
Those routers allow the LAN interface to be given up to two aliases in addition to their primary address.
So what I did was to set the primary address to a unique RFC1918 address, which was just used for management purposes when I needed to telnet to a specific router, and then to set the alias on each router to the same, shared, public address.
I then added static routes on each router to pass traffic for our public IPs back to the linux box where the bonding was done.
The WAN ports were configured with separate public addresses - a unique one for each router.
Bridge mode wasn't used - they were acting as normal routers.
I wouldn't like to say if the P660 is particularly good or bad - they were the free routers our ISP provided with the lines.
(Log in to post comments)
The CoDel queue management algorithm Posted May 30, 2012 15:16 UTC (Wed) by nye (guest, #51576) [Link]
>The WAN ports were configured with separate public addresses - a unique one for each router.
Interesting, so this sounds like a different configuration than some bonding setups which appear to require only a single public IP address. I wonder if that's down to how the ISP configures their interfaces.
I suspect I could make a lot more progress here if experimentation didn't mean scheduling connection downtime of an unknown duration, which in practice means being physically present in a locked office building in the dead of night (for which honestly they Do Not Pay Me Enough™).
At any rate, thanks for the information.
|
|||||||||||||