I think this topic has already been discussed before on this list.
However, Google and I can't seem to find the discussion thread.
We have fixed IPs from both a cable and DSL provider. It it feasible to
our multi-home AstLinux using a Soekris net5501? If so, how?
Thanks.
Dan
Dan,
You're not really 'multi-homed', you just have two Internet circuits. If
one goes down, it's not like you can use the same IP address on the
other one.
What you can do though is setup the second circuit as a fail-over if the
first one goes down. We do this and it works very well. We basic
Hi James,
Thanks for catching and correcting my misnomer. Indeed, we wouldn't be
using the same IP address so it's just as you said: Two Internet circuits.
I also appreciate the recipe for the script, which sounds like it's just
the ticket. We'll explore this further...
Cordially,
Dan
O
Hi Dan,
probably a script is efficient enough in most cases. Just want to show
you something what else could be done:
http://mpath-tools.optilian.org/
Regards,
Ingmar
On 09/22/2010 06:15 PM, Dan Ryson wrote:
> Hi James,
>
> Thanks for catching and correcting my misnomer. Indeed, we wouldn'
Hi Ingmar,
It's nice to have options. Thank you for suggesting mpath-tools, which
looks like it's worth of a close look.
Are you using this with AstLinux?
Dan
On 9/22/2010 12:30 PM, Ingmar Schraub wrote:
> Hi Dan,
>
> probably a script is efficient enough in most cases. Just want to show
>
Hi Dan,
no, I am not using it with astlinux. Probably it's not hard adding it.
Though this might not be the only or best option for astlinux. That's
something the developers should comment on. Of course if you are
familiar with the astlinux internals, you could give it a try yourself.
Maybe you do
Technically, "multi-homed" is exactly that: having more than one IP address.
Doing hot-failover with no loss of connectivity is a lot easier to do with two
circuits of the same kind (or at least through the same provider, terminating
into the same peering gateway).
On 9/22/10 8:16 AM, James
Is been discussed many times but no one yet shared an elegant Astlinux/ Soekris
working approach. Just ideas, sugestions or theory. I tried the "dual default
gateway" approach but never completly worked for me so I didn't share anything
since I didn't have anything good to share. In my setup the
Thanks Ionel Chila,
This is a good start. I'm merely a hacker so it's unlikely I'll pull
together something worthy of advertising. But if I do, I'll gladly share.
Dan
On 9/22/2010 5:52 PM, Ionel Chila wrote:
> Is been discussed many times but no one yet shared an elegant Astlinux/
> Soekri
Thanks Philip.
Regardless of what it should be called, what we need is fail-over
diversity. For our purposes, we hope to avoid having two circuits from
the same provider because when our cable modem stops working, cable
Internet service also quits working at neighboring businesses in our
co
Asterisk will likely only try to re-co0nnect when the SIP provider
registration timer expires.. you can try setting your reg timer low.. like
say 300 seconds.. the SIP provider wont know where to send the calls until
you re-register with them... ive not tried using a qualify setting for a
SIP p
About the only really cleanly working solution I can think of is to have a
"proxy" in a data center that accepts traffic for address 'A', and then
encapsulates it (either via IPsec ESP with NULL encryption or with GRE) and
then forwards the traffic to your IP addresses B and C.
You can decide
Yeap did that already, set the reg time lower from the default :-) I think I
had another post about that... My Asterisk just keep on trying to re-connect
but
never makes it despite one of the two ISP's being available and the routing
working just fine. That's way I had to put in such a radical
Ionel Chila wrote:
> Yeap did that already, set the reg time lower from the default :-) I think I
> had another post about that... My Asterisk just keep on trying to re-connect
> but
> never makes it despite one of the two ISP's being available and the routing
> working just fine. That's way I
Hi Philip,
That's simply brilliant. However, as you said, it would introduce
another single point of failure. Further, to be honest, I sometimes
tend to get flummoxed. Therefore, a simple solution might be a better fit.
I'd gladly settle for something that's not-so-clean... but is simple t
For a data center it may be an appropriate solution but for a small shop or
home
use this is just an extra piece of hardware to buy, maintain and a failure
point
as well. I wish there was something elegant that can be built into the astlinux
image I have two ISP at home and Comcast regular
I use an older 3 nic snapgear router (SG570) to front end my cable modem and
DSL service for VOIP.
Snapgear routers are linux based and do a pretty good job at failover and load
balancing. They are also based on uclibc and
operate much like astlinux in many aspects (and have more or less the
There are ways to do what you're doing without a reboot.
You first need to figure out what state changes before/after the reboot, and
then come up with a way to automate that.
On 9/22/10 8:31 PM, Ionel Chila wrote:
> For a data center it may be an appropriate solution but for a small shop or
18 matches
Mail list logo
