From: Paulo Andre <pandre@darkstar.nom.za>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Connectivity
Date: 03 Dec 2002 08:30:09 +0200 [thread overview]
Message-ID: <1038897009.345.7.camel@bigblue> (raw)
I am running iptables 1.2.6a. The firewall/gateway server links a DMZ,
Internal, External zones. The DMZ card is aliased with two different
ip's (196.10.1.x and 196.10.10.x).
I have a router on the DMZ that reboots every evening at a specific
time, the router is not under our control.(196.10.10.y)
When this happens iptables does not allow traffic through even though
the router comes up immediately.
I basically have to take the card down, reconfigure it with another ip
(196.10.10.b) then it sees the router, take the card down again and
reconfigure it to the original ip (196.10.10.x) and re-apply the rules.
Then everything works fine again.
One way of fixing this is to get the router fixed, but this is not under
my control. Could anyone tell me how I could fix the iptables side of
things, surely iptables should be able to handle when and router
reboots...???
Any suggestions please...
next reply other threads:[~2002-12-03 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 6:30 Paulo Andre [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 7:11 Connectivity Paulo Andre
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=1038897009.345.7.camel@bigblue \
--to=pandre@darkstar.nom.za \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.