From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] GRE link state detection
Date: Thu, 05 Sep 2013 15:49:55 +0100 [thread overview]
Message-ID: <52289A13.6010403@thegeezer.net> (raw)
Howdy all,
i was wondering if anyone has any idea if there is a means by which i
can detect GRE link state ?
what i have is two sites each with two very unstable internet links
in order to vpn between them i have ipsec tunnels linking each side
twice (four ipsec tunnels in total)
i then have 4x GRE tunnels over the top of those in order that i have a
secured routable VPN
this gives me net.vpn0 net.vpn1 net.vpn2 and net.vpn3
finally i run BIRD over the top which works very well, and synchronises
routing tables between the two sites, and allows for me to do such fun as
# /etc/init.d/net.vpn0 stop
and watch all traffic automagically cut over to another link.
so far so awesome.
however, as i said the internet links are very unstable, and sometimes
just blackhole. so what i was hoping to do is just enable keepalives on
the gre tunnel. which sadly seems to be cisco only.
can anyone suggest a way of detecting if the GRE is not fully connected ?
BIRD only fails over if the net.vpn0 device is down (ifconfig up/down)
and for the life of me i cannot find how to detect if a GRE tunnel is
'connected', it seems to just blindly send packets to the remote IP.
is my only choice to use L2TP instead ?
thanks in advance for any suggestions; if anyone would like the configs
in order to set this up let me know and i'll reply to list with a mini-howto
PS if i'm on the wrong list i'd welcome a friendly push to the correct list
next reply other threads:[~2013-09-05 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:49 thegeezer [this message]
2013-09-07 18:23 ` [gentoo-user] GRE link state detection Mick
2013-09-09 10:12 ` thegeezer
2013-09-09 18:39 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52289A13.6010403@thegeezer.net \
--to=thegeezer@thegeezer.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox