Skip to contentSkip to conversation

double gateway - new thread

LARTC Paul Evans 3 participants 4 messages Jan 30, 2003 – Jan 31, 2003

lore
Share & tools
lore

Paul Evans

author
#0 lore raw

I've been subbing this list for a couple of months now, knowing this day would come :-)

I too am trying to do an equalize/next hop for 2 adsl lines. At the moment though I am testing with 1 2MB adsl modem and an ether connection to a switch from a second 2MB line.

I am doing it from the *outside* via ssh, which makes it a little more difficult, since when I mess up I lose access until I can get someone to restart the network without my changes...

I began by using the example from lartc.org, combined with a cron to undo my changes every half hour, but moved to following this page from sysadmin magazine:
http://www.samag.com/documents/sam0201h/

For some reason I got a better sense of what I was trying to do from it, plus it included a section on just where to place the new rules into the system scripts. It did not say just where to place the section for ifup-routes though.

I think I've got it pretty close, but since I just locked myself out again...

It's a mandrake 9.0 box and I didn't see where to prevent a default route from being set when it brings up ppp0 on the adsl line. I sort of hoped that my default routes would get set first and force the other to fail with the Exists error. Since I couldn't find it, I don't know in what order it gets run. I think that's where I messed up, but I can't get back in to read the logs right now.

Also, the above article uses ip to route to the lan, and I had intended/understood that I would masquerade to it later. Which is the correct approach then? I will want to move on to tc when I finally get this part working.

from the article:

advanced eth0 10.0.0.0/24 via 10.0.0.1 table 1
advanced eth0 10.0.0.0/24 via 10.0.0.1 table 2
advanced eth1 0/0 via 63.89.102.1 table 1
advanced eth2 0/0 via 65.3.17.1 table 2

Where eth0 is their lan and eth1/2 are isp. They have a new section in ifup-routes grepping a file named static-routes for '^advanced'.

Signature · 6 lines
Regards, Paul Evans


_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#1 lore raw

Paul,

Quoted 2 lines · Paul Evans

I've been subbing this list for a couple of months now, knowing this day would come :-)

My gut says I was not alone, you are not alone, and others will eventually be going down this path as well.

Quoted 7 lines

I too am trying to do an equalize/next hop for 2 adsl lines. At the moment though I am testing with 1 2MB adsl modem and an ether connection to a switch from a second 2MB line.

I am doing it from the *outside* via ssh, which makes it a little more difficult, since when I mess up I lose access until I can get someone to restart the network without my changes...

Ouch, that will slow things down during testing.

Quoted 4 lines

I began by using the example from lartc.org, combined with a cron to undo my changes every half hour, but moved to following this page from sysadmin magazine:
http://www.samag.com/documents/sam0201h/

Good article, I cam across it as well. However it really only is accurate on the DNS point of view from the outside world.

For things to work the other way around, from the inside going out you will need the nano-how-to and possible Julian's patches applied to a custom compiled kernel.

http://www.linuxvirtualserver.org/~julian/#routes

Quoted 4 lines

For some reason I got a better sense of what I was trying to do from it, plus it included a section on just where to place the new rules into the system scripts. It did not say just where to place the section for ifup-routes though.

When doing something of this nature I recommend not using any provided networking scripts and make your own. It's fairly straight forward and easy to do.

Just put all your commands into a function that can be called from outside of the script. Like

./mynetwork.sh start will call the start function.

Quoted 1 line

I think I've got it pretty close, but since I just locked myself out again...

That sucks. :)

Quoted 6 lines

It's a mandrake 9.0 box and I didn't see where to prevent a default route from being set when it brings up ppp0 on the adsl line. I sort of hoped that my default routes would get set first and force the other to fail with the Exists error. Since I couldn't find it, I don't know in what order it gets run. I think that's where I messed up, but I can't get back in to read the logs right now.

Like is said make your own scripts and do not use the originals for now, if possible. I think that your doing this from the outside may require you to use the default ones until you get things working. Then make your own and forget about the default ones.

Quoted 4 lines

Also, the above article uses ip to route to the lan, and I had intended/understood that I would masquerade to it later. Which is the correct approach then? I will want to move on to tc when I finally get this part working.

The way it works for me, and to my knowledge the only way it works is by masquerading. That's where the patches make things work.

However I thought I saw a comment from Julian that masquerading was not necessary? I thought it was? I would imagine Julian will set me straight one way or the other. ;)

Quoted 9 lines

from the article:

advanced eth0 10.0.0.0/24 via 10.0.0.1 table 1
advanced eth0 10.0.0.0/24 via 10.0.0.1 table 2
advanced eth1 0/0 via 63.89.102.1 table 1
advanced eth2 0/0 via 65.3.17.1 table 2

Where eth0 is their lan and eth1/2 are isp. They have a new section in ifup-routes grepping a file named static-routes for '^advanced'.

This stuff forget from the sys-admin article and stick to the routing rules on the nano-how-to.

The only part of the sys-admin article that I used and recommend others to use is the DNS aspect for redundancy/load balancing from the outside world. Although most of the same info with other examples can be found in the BIND manual.

Signature · 13 lines
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone  707.766.9509
Fax    707.766.8989
http://www.obsidian-studios.com

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#2 lore raw
In reply to Paul Evans

At 05:58 PM 1/30/2003, Paul Evans wrote:
<< Snip >>

Quoted 4 lines

I am doing it from the *outside* via ssh, which makes it a little more difficult, since when I mess up I lose access until I can get someone to restart the network without my changes...

Might I suggest mgetty and a POTS line so you can "phone home" and undo the damage yourself. ;-)

John
<*>

#3 lore raw
In reply to Paul Evans

Paul,

Quoted 2 lines · Paul Evans

Yes, the usual learning cycle of break/repair, break/repair cycle takes a looong time.

I sure spent my time in the trenches.

Quoted 4 lines

Thanks very much. I suppose it's back to my old script then. I was stuck with a 'file exists error', because of the existing default route. Of course, if I were to delete it, I'd suddenly not be 'there' anymore to apply the script. Maybe I can do both via cron instead.

In that case you will want to use two different scripts. The existing one and the new one. Have cron simply restart the network every so often probably like you are.

Also in part of your script is sounds like you need to flush out everything the default network script adds that you do not want.

Quoted 5 lines

Thanks yet again, I skipped Julian's page, because I thought it was just for the patch. I will go and read it. When I finally get my head around this part, I will probably have to consider recompiling the kernel and applying the patch (I think we're talking about the one to eliminate the route caching).

Yes, I tried to play with the cache settings directly, but no combo made things work like the patches. You must also adhere to the nano-how-to rules on routes and such.

Quoted 9 lines

I'm familiar with bash functions and I will follow your advice, for me I am still trying to untangle all the nested calling of the many and varied scripts that come into play when bringing up all the interfaces. Which do you recommend my redoing exactly. I mean the existing one for network, ifxxup, adsl-start are all doing fine the way they are (except for the bit where I don't know how to prevent a default route being set by adsl-start that is). I had hoped I could end up with a single script from, say rc.local or something. Not to be huh? ( I still haven't read the nano you ref'ed earlier).

You can still use your existing network script, just make another one that removes the default ADSL route and anything else that is getting in your way, and then run your commands to get things working your way.

Once you are done with your script put it in /etc/rc.d/init.d and add a symbolic link in the proper run level(s) with the necessary startup number. Probably just after the standard network script is run.

If you want a single one, add everything you need to your new script and use instead of the default. Although depending on the type of ADSL, PPOE type, you may want to keep and use the default startup script.

There is nothing wrong with two, but it is Linux so do what you like and put things were you want them.

Make sure to read the nano-how-to or at least make sure all your rules are exactly the same within reason. I tried some deviations, but all failed. Obviously you do need to use the exact IP's as in the example, but use the same rules, and commands using your IP info.

Quoted 4 lines
Quoted 2 lines

The way it works for me, and to my knowledge the only way it works is by masquerading. That's where the patches make things work.

Ok good. That part realy confused me after all the reading I've done on stef's site etc.

That part still some what confuses me. What is clear is I had a goal and was able to reach it. Masquerading was not a requirement for me, but I did not mind doing it as well.

I simply ended up with two rounds of NAT/PAT or two back to back firewalls on either link.

More on my config can be found in the archives, but feel free to contact me directly for any questions and specific configuration examples.

Signature · 13 lines
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone  707.766.9509
Fax    707.766.8989
http://www.obsidian-studios.com

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/