From: Peter Rabbitson <rabbit@rabbit.us>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: multiple routing tables for internal router programs
Date: Tue, 12 Jun 2007 11:23:42 +0000 [thread overview]
Message-ID: <466E823E.8020509@rabbit.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0706111505070.3751@tigger.tntechs.com>
Salim S I wrote:
> Thanks! I get it now.
> But why the src address for the interface is wrong?
> In my case eth2 has a.b.c.d and eth3 has p.q.r.s.
>
> DNS queries going through eth2 has p.q.r.s as src address and those
> going through eth3 has a.b.c.d. Something wrong with routing?
Possible. Post full configuration and someone might be able to help.
> I was wondering, how the ping script (to check the lonk status) of
> others work id domain name is used.
Don't know about others, and I personally use ip addresses :)
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-12 11:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 19:06 [LARTC] Re: multiple routing tables for internal router programs Tom Diehl
2007-06-11 19:23 ` Javier Charne
2007-06-12 7:59 ` Andrea
2007-06-12 8:09 ` Salim S I
2007-06-12 9:01 ` Peter Rabbitson
2007-06-12 9:15 ` Andrea
2007-06-12 9:29 ` Peter Rabbitson
2007-06-12 9:49 ` Salim S I
2007-06-12 10:02 ` Peter Rabbitson
2007-06-12 10:10 ` Andrea
2007-06-12 10:20 ` Salim S I
2007-06-12 11:23 ` Peter Rabbitson [this message]
2007-06-13 4:08 ` Salim S I
2007-06-14 3:50 ` Salim S I
2007-06-14 4:23 ` Alex Samad
2007-06-14 7:26 ` Peter Rabbitson
2007-06-14 10:34 ` Salim S I
2007-06-15 3:26 ` Salim S I
2007-06-15 6:00 ` Peter Rabbitson
2007-06-15 6:01 ` Peter Rabbitson
2007-06-15 6:21 ` Salim S I
2007-06-15 6:29 ` Peter Rabbitson
2007-06-15 9:36 ` Salim S I
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=466E823E.8020509@rabbit.us \
--to=rabbit@rabbit.us \
--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.