All of lore.kernel.org
 help / color / mirror / Atom feed
From: lartc user <lartc@theorb.net>
To: lartc@vger.kernel.org
Subject: [LARTC] iproute2 ping  question
Date: Wed, 29 Jun 2005 23:20:23 +0000	[thread overview]
Message-ID: <42C32CB7.6020505@theorb.net> (raw)

Hi List,

New subscriber/lartc user here.  Have read the entire lar&tc howto, 
alexy's ip_cref, etc. and must say, this makes iptables seem downright 
*easy*.

I'm trying to build a three-legged linux router (WAN/LAN/DMZ) and have 
had it more or less working with iptables but would like to learn layer2 
routing with iproute2.

I have an adsl/29 network and would like my router to answer on all five 
of my static addresses on the WAN side of the router.  For testing 
purposes I'm using tcpdump and ping.

For list purposes the WAN is
$ADSL.0  network
$ADSL.1  gateway
$ADSL.2  WAN-address1 (eth1)
$ADSL.3  WAN-address2
$ADSL.4  WAN-address3
$ADSL.5  WAN-address4
$ADSL.6  WAN-address5
$ADSL.7  broadcast

First I bring up the nic.
   "ifup eth1"
Ping and eth1 ($ADSL.2) replies correctly.

Next I add a second address to the nic.
   "ip addr add $ADSL.3/29 dev eth1"

Ping gets no response from the new address but tcpdump shows the nic 
receiving the request.

If instead I bring the addresses up as aliases on eth1 the pings work.

Would somebody please explain how to use ip to attach the addresses to 
that interface and have it respond to them?

Many thanks in advance, and apologies for the thickness of my skull.

:m)
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-06-29 23:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 23:20 lartc user [this message]
2005-06-30  2:11 ` [LARTC] iproute2 ping question gypsy

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=42C32CB7.6020505@theorb.net \
    --to=lartc@theorb.net \
    --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.