George, good to hear from you!
We do apear to be working on the same thing, other than the T-1/DSL vs DSL/modem
difference.
I'm starting from the same scripts from the "Detecting Disconnected Network" thread.
Right now I'm focusing on the routing issue and I need to get a bunch of shorewall
rules set up. Let me know if you make any progress on the script. If I get anywhere
on the routing issue I let you know stat.
We will have to keep the list posted on our efforts.
I'm also very interested in contributing this configuration with solid documentation.
I'm willing to do quite a bit if not all the documentation if we could both take good
notes. I'm not sure what form this would take, maybe a couple of scripts in addition
to the configuration files, one to set up the needed cron job and any other safe
configuration changes that can be automated, and the actual monitoring/interface
change scripts.
Richard Amemran
-----Original Message-----
From: George Luft [mailto:[EMAIL PROTECTED]]
Sent: Tue 6/11/2002 12:01 PM
To: [EMAIL PROTECTED]
Cc: Richard Amerman
Subject: RE: [leaf-user] Bering DSL + modem failover - default route
I wish you well in this endeavor, Richard. I am trying to do basically the
same thing. I want to use static DSL as a backup to a T-1 (mainly to maintain
connectivity to/from our mail server), and I keep bumping into the issue of the
default gateway.
I think we'll end up using a script to test connectivity to various hosts as
was discussed in the Detecting Disconnected Network thread.
Perhaps we can figure it out together...
> -----Original Message-----
> From: Richard Amerman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 11, 2002 2:43 PM
> To: [EMAIL PROTECTED]
> Subject: [leaf-user] Bering DSL + modem failover - default route
>
>
> As some of you may have noted I am working on a Bering
> configuration with a main external interface at eth0 of a DSL
> router and an additional external connection consisting of an
> external modem for redundant failover.
>
> I have had no problem getting the modem to work and it looks
> like the firewall portion may not be too bad (knock on wood!)
> but I can’t seem to get past the existing defaultroute.
>
> How does one change the defaultroute on the fly? I have my
> pppd setup configured to set the ppp connection as the defaultroute.
>
> pppd logs the following message:
> "not replacing existing default route to eth0"
>
> The only other negative sounding message is the following:
>
> "Cannot determine Ethernet address for proxy ARP"
>
> I also experimented with settings in the interfaces config
> file in the "ppp0" interface section. The default is
> auto ppp0
> iface ppp0 inet ppp
> provider provider
>
> I changed this to :
> auto ppp0
> iface ppp0 inet ppp
> Address xxx.xxx.xxx.xxx
> Masklen 27
> Gateway xxx.xxx.xxx.xxx
>
> I’m not sure this is appropriate but I could not find further
> documentation on this file to indicate whether I can use
> these settings with a ppp interface, and even if I can, that
> it is appropriate.
>
> I also added a local:remote entry to the ppp options file and
> tried the -ip setting to force the use of these settings but
> the ppp connection was dropped with a message from the ISP to
> the effect of "No network protocol running".
>
> Any ideas?
>
> I’m also working on a script to monitor the DSL connection
> and bring up the modem connection if it is determined as
> down. When the DSL connection was restored for a given
> period of time then the modem would be disconnected. This
> setup also depends on a secondary MX record pointing to the
> static ip for the modem connection so mail will still get through.
>
> I am definitely working to set this up in the most ideal
> manor as It seems like this configuration would be useful to
> contribute.
>
> Richard
>
>
>
> 2mhథ*'ejz'
yᜲ.r晴.m4晴m(汭ڕZഝrq^֫柺ǫx%ey壧αŊlqzm젶?X( ~zwᜭ
> Xb젝?ൕǫI@Bmy鮈r杭+no朲hshrfj崫 |‶Xm
>
[b)eâYZ*&^z{h"mƬ *'8k M6i00jv{uܢojWuyj)b
b^izb,y+m+-.ǟ +-bا~yDPi^ik7 ځv"w_=f
