[plug] ADSL failover

[Justin Hall]

Quick clarification.

The modem has an ethernet port. You setup a static ip on your server/computer -
with a default route to the static ip address assigned to your ADSL link/gateway
(and a route back to your network, for all 192.168.1.0 addresses etc - if you
have 2 or more NICs, MASQing etc).

So it basically it acts like a LAN connection to the net. Just plug and go. You
don't need to tell the modem to do anything, as soon as it is connected to the
line it links up with the dslam (or what ever it is called) at the other end
(telstra exchange) - your link is up.

Justin

Simon Scott wrote:

>         no pppoe?
>
>         How does it work specifically? How does the modem connect to the
> box?
>
>         Is it static IP?
>
>         From:   Justin Hall <justin at inwa.com.au> on 15/08/2001 10:28 AM
>         Please respond to plug at plug.linux.org.au@SMTP at Exchange
>         To:     plug at plug.linux.org.au@SMTP at Exchange
>         cc:
>
>         Subject:        Re: [plug] ADSL failover
>
>         I use iinet ADSL, and it hasn't gone down since i had it put in in
> May. They use
>
>         Telstra but do it in a different way to Telstra. They don't use
> pppoe or
>         anything, your link has an IP address - and they give you an address
> for your
>         box, and that is it. In my opinion a much cleaner system.
>
>         Justin
>
>         Simon Scott wrote:
>
>         >         Funny, they are getting iinet adsl, but i thought iinet
> were using
>         > Hel$tra infrastructure? I had bigpong adsl and it sucked the big
> one.
>         >
>         >         Yeh, I think the if-down/up scripts will be the way to go.
> Or
>         > possibly a seperate daemon that monitors these things and makes
> sure one or
>         > the other is up.
>         >
>         >         Altho Im going to look at Pizzabox and perhaps it has some
> way for
>         > this to be handled. Even manually would be ok I guess.
>         >
>         >         They wont be serving, so it doesnt matter.
>         >
>         >         Thanks
>         >
>         >         From:   James Bromberger <james at rcpt.to> on 14/08/2001
> 04:14 PM
>         >         Please respond to plug at plug.linux.org.au@SMTP at Exchange
>         >         To:     plug at plug.linux.org.au@SMTP at Exchange
>         >         cc:
>         >
>         >         Subject:        Re: [plug] ADSL failover
>         >
>         >         On Tue, Aug 14, 2001 at 03:25:46PM +0800,
> Simon.Scott at flexiplan.com
>         > wrote:
>         >         > A friend of mine is setting up a linux box to act as a
> gateway for
>         > a small
>         >         > network. He plans on getting ADSL, as well as a dialup
> account
>         > (due to ADSL's
>         >         > problematic nature).
>         >
>         >         I've had very few problems with my iiNet DSL...
>         >
>         >         > Has anyone written/heard of a script which will
> automatically dial
>         >
>         >         > in after ADSL fails (plus a few retries)?
>         >
>         >         /etc/network/if-down.d or similar. You can tell pppd to do
> something
>         >
>         >         when it exists. Why not tell it to pick up the modem!
>         >
>         >         > If not, can anyone think of the best way of acheiving
> this? It
>         > would be
>         >         > nice to
>         >         > go the other way too, where the script would start a
> cron job to
>         > test ADSL
>         >         > connectivity (maybe via pppoe switches to see if the
> access
>         > concentrator is
>         >         > visible) every now and then and if ADSL comes up, drop
> dial up.
>         >         >
>         >         > As an aside, if I had a dialup account and ADSL up at
> the same
>         > time, what would
>         >         > the routing issues be? (ie which would take preference?)
>         >
>         >         Evil. Assuming you are calling the same service provider,
> you can
>         > try and
>         >         get them to figure this out. You may have to delve into
> BGP
>         > broadcasts if
>         >         you have a protable network block, or Dynamic DNS, if
> you're hosting
>         > services.
>         >
>         >         If you're just putting web traffic over it, and not
> serving stuff
>         > up,
>         >         then it should matter if you change IP addresses.
>         >
>         >         --
>         >          James Bromberger <james_AT_rcpt.to> www.james.rcpt.to
>         >
>         >          Remainder moved to
> http://www.james.rcpt.to/james/sig.html
>         >
>         >
> **********************************************************************
>         > This email and any files transmitted with it are confidential and
>         > intended solely for the use of the individual or entity to whom
> they
>         > are addressed. If you have received this email in error please
> notify
>         > the system manager.
>         >
>         > This footnote also confirms that this email message has been swept
> by
>         > MIMEsweeper for the presence of computer viruses.
>         >
>         > www.mimesweeper.com
>         >
> **********************************************************************
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************