[email protected] wrote:

>My ISP is AT&T DSL, and their so-called "static" IP addresses are really
>an abuse of the PPP and PPPoE specifications.  The PPP protocol is only
>completed for a single IP address, and the other addresses are just
>passed through the same link, so unless the administrator manually adds
>them (via alias devices in Linux, for example), they will be unusable.
>It's a shame that a PPP negotiation session can't be done for each IP
>address in parallel.

That's actually the normal way of doing it - your router gets one 
address, and further addresses are simply routed to it. If your modem 
doesn't cope with that then that's your end that's at fault. I can 
imagine a lot of consumer grade equipment being unable to do it.


[email protected] wrote:

>  > Having a /24 attributed to your company with redundant routers and
>>  redundant ISPs will allow you to announce this /24 on both ISPs network
>>  (providing they do support BGP) and will be clean.
>
>That would be sweet indeed.  Unfortunately, I'm just a residential
>connection.  Besides, wouldn't very powerful routers be needed, and I'd
>need my own ASN number as well, to truly have my own IP addresses that
>would be independent of any ISP going down?

You don't need powerful routers - I believe you can do BGP4 with a Linux box.


Linux Advocate wrote:

>what's an ASN number?

Autonomous System Number.

The internet uses BGP4 for passing routing information about. The 
basic unit is an AS number which identifies a "chunk" of network - 
and then IP address blocks are associated with an AS number. To be a 
routable part of the internet, you get an IP allocation and an AS 
number - you then get to send out a route advertisement through 
any/all of your connections to peers, and that route gets propagated 
around so people know where to send packets. If a link goes down, 
route advertisements stop going out through it and the internet as a 
whole learns an alternate route to you. You can advertise routes 
through each link with a different cost metric (perhaps related to 
bandwidth costs, or link speed, etc) - so different bits of the 
internet could reach you by different means.

It's a fascinating subject to get into - we've been considering doing 
that at work to increase resilience since we run a  lot of hosted 
services for customers.

http://en.wikipedia.org/wiki/Autonomous_system_(Internet)




There is another option no-one has mentioned. There are third parties 
that will provide a bonded service independent of your ISP. How it 
works is that they allocate you one or more IP address(es) from their 
assignment. All your inbound and outbound traffic goes via the third 
party, and then is encapsulated and routed via whatever connections 
you have available. At your end, you just need a small router capable 
of maintaining the multiple encapsulated tunnels and 
splitting/combining the traffic.

You still have a single point of failure at each end. The router at 
your end is a failure point (but if it's important then you can keep 
a spare or have a failover setup). The service provider at the other 
end is also a SPF, but if you choose right they are big enough to 
have the engineering setup and staff to manage it - rather than your 
usual "have you rebooted your router" script based support from your 
ISP.

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to