From: "Géczi Szabolcs" <szabszi@goodwill.hu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: 3 interfaces in one linux box
Date: Wed, 17 Jul 2002 06:11:50 +0000 [thread overview]
Message-ID: <marc-lartc-102688634909024@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102650738903835@msgid-missing>
On Sat, Jul 13, 2002 at 12:54:02PM +0200, bert hubert wrote:
> > Great, a little corrections needed, the solution provided by ahu.
> > I did what bert wrote, but ahu adviced that I should write ip rule add from
> > internal.ip.address table leased, after that the servers in subnet can
> > answer. Thanks to Bert and ahu.
>
> Bert and <ahu> are one guy :-) This means that ipchains acts AFTER the
> policy table has been selected. iptables may well go BEFORE - be aware of
> that before upgrading.
[...]
>
> Try 'tcpdump -n -i interface' to see where packets go. They probably go out
> the wrong interface.
there are some additional problems with routing :).
So after I set up my iproute2 (ip rule add, ip route) my servers answer from
subnet, BUT the client from subnet can't reach the linuxbox's public
interface (217.65.110.146) and about this problem, they can't see the
webpage on the linux box. The internal ip address is available from subnet,
but the leased line's public interface cannot be reached.
any idea ?
--
Géczi Szabolcs
GPG: http://www.goodwill.hu/~szabszi/szabszi.asc
Fingerprint: B36C 150C C316 5A15 DB5F 183A 303B 5AEB 36C2 3162
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-17 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 20:55 [LARTC] Re: 3 interfaces in one linux box bert hubert
2002-07-17 6:11 ` Géczi Szabolcs [this message]
2002-07-17 11:25 ` bert hubert
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-102688634909024@msgid-missing \
--to=szabszi@goodwill.hu \
--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.