Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Gáspár Lajos" <swifty@freemail.hu>
To: John Lister <john.lister@kickstone.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Checking line status
Date: Wed, 02 Sep 2009 12:23:18 +0200	[thread overview]
Message-ID: <4A9E4796.2040202@freemail.hu> (raw)
In-Reply-To: <591B070B9C3D465CA4CCE1B11024DBEA@squarepi.com>

Hi!

I have written a target for this:  www.glsys.eu/iface

Swifty

John Lister írta:
> Hi, I have a multihomed machine to which i'd like to check the status 
> of each line periodically. I want to do this so that I can modify the 
> iptables rules and send new connections out over the active lines and 
> restore service when the line comes back up.
>
> I thought I could use ping with the -I option, but that doesn't seem 
> to work, it always uses the default route. However if I get rid of the 
> default route and modify the rules to match the packets I get a 
> "network unreachable" message without it ever hitting iptables. For 
> example adding something like this never gets matched for the ping.
>
> iptables -t mangle -I OUTPUT -j LOG --log-prefix "output: "
>
> Normally ping results in ICMP messages being traversed, but not this 
> time.
>
> Could someone explain what is going on and I'd be grateful if there 
> were any suggestions on other ways to detect if a line is down - 
> simply looking in /proc/net/dev or similar wouldn't help as the local 
> connection is likely to be up, but the physical line to the ISP may be 
> down.
>
>
> Thanks
>
> John
> -- 
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2009-09-02 10:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 11:33 really need your help about iptables J. Bakshi
2009-08-25 12:27 ` Problem with statistic module nth mode John Lister
2009-08-25 12:48   ` Patrick McHardy
2009-08-25 12:55     ` John Lister
2009-09-02  9:23     ` Checking line status John Lister
2009-09-02 10:23       ` Gáspár Lajos [this message]
2009-09-02 11:21         ` John Lister
2009-09-02 12:47       ` Thomas Jacob
2009-09-02 13:54         ` John Lister
2009-09-02 14:02         ` John Lister
2009-09-02 14:29           ` Pascal Hambourg
2009-09-02 14:42             ` John Lister
2009-09-02 15:16               ` Pascal Hambourg
2009-09-02 16:48                 ` John Lister
2009-09-02 14:30           ` Thomas Jacob
2009-09-02 15:02             ` John Lister
2009-09-02 14:13       ` Tormod Nygård
2009-08-25 14:09 ` really need your help about iptables Oskar Berggren
2009-08-26 12:14   ` J. Bakshi
2009-08-26 12:36     ` Re:[possible solution] " J. Bakshi

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=4A9E4796.2040202@freemail.hu \
    --to=swifty@freemail.hu \
    --cc=john.lister@kickstone.com \
    --cc=netfilter@vger.kernel.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