From: Jeremiah Savage <jeremiahsavage@yahoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] simple router
Date: Sat, 30 Jun 2001 04:05:16 +0000 [thread overview]
Message-ID: <marc-lartc-99387398705823@msgid-missing> (raw)
Hello,
I am attempting to construct a (simple?) router based
on Linux 2.4 with iproute2.
I have 3 ethernet cards on the router, with eth0
connected to a host,eth1 connected to a server and
eth2 connected to another computer.
xx.yy.88.101
+--------+
| |
| host |
+---+----+
|
xx.yy.zz.aa |
| |eth0 - xx.yy.88.100
| |
+---------+ | +----------------+
|another | eth2 | |
|computer +---------+ router |
| | | |
+---------+ +-------+--------+
xx.yy.zz.ab |
| eth1 - xx.zz.110.145
|
+---+-----+
| |
| server |xx.zz.110.148
| |
+---------+
I am simply trying to get traffic through eth0 to eth1
so it can get to the server and get back out, but so
far I can't ping the server through the router,
although the router itself is capable of pinging the
server (so the link eth1 is active). And I've verified
that eth0 is also active as the router and the host
can ping each other.
So how do I get the router to pass traffic through to
the server?
I've tried
# ip route add to unicast xx.zz.110.148 dev eth1
RTNETLINK answers: File exists
and yet the host still can't ping the server.
And I've tried making eth0 "promiscuous"
# ifconfig eth0 promisc
but that doesn't help either.
Anyone know the magic incantation that I need?
--
Jeremiah
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-06-30 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-30 4:05 Jeremiah Savage [this message]
2001-06-30 6:38 ` [LARTC] simple router Jing Shen
2001-06-30 21:22 ` Jeremiah Savage
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-99387398705823@msgid-missing \
--to=jeremiahsavage@yahoo.com \
--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.