From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] interaction between different tables' default routes
Date: Thu, 28 Feb 2002 10:48:43 +0000 [thread overview]
Message-ID: <marc-lartc-101489337820656@msgid-missing> (raw)
On Wed, Feb 27, 2002 at 04:29:23PM +0530, suresh wrote:
> to forward request from another lan network it works fine
> but req from 172.16.1.0 does not work
>
> if i remove
> ip route del default via w.x.y.z dev eth1
>
> its work well.
>
> Did i leaveout anything in configuration?
I'm not sure about this. At one point I understood how this worked but I
don't anymore. There is something in the HOWTO about fallback routes. I
think there are people here who do understand the interaction between
different tables' default routes.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-02-28 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 10:48 bert hubert [this message]
2002-02-28 11:14 ` [LARTC] interaction between different tables' default routes Arthur van Leeuwen
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-101489337820656@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.