From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Forcing an "external" route
Date: Fri, 07 Dec 2001 22:38:25 +0000 [thread overview]
Message-ID: <marc-lartc-100776476519479@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100776128506945@msgid-missing>
On Fri, Dec 07, 2001 at 04:46:00PM -0600, Greg Scott wrote:
> What if you used some iptables rules to DENY packets from eth0 with
> destination ip address 172.16.1.100? I'm thinking you might have to put in
> the rules in the OUTPUT table and catch them on the way out from
> 192.168.1.100. No clue whether or not that will work, but worth a try.
That just drops the packets. You might try some DNAT stuff on the iptables
POSTROUTING chain, perhaps that works. I think it might.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-12-07 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 21:38 [LARTC] Forcing an "external" route David Purves
2001-12-07 22:27 ` bert hubert
2001-12-07 22:38 ` bert hubert [this message]
2001-12-07 22:46 ` Greg Scott
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=marc-lartc-100776476519479@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@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 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.