All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kelly Scroggins <kelly@cliffhanger.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 is not routing
Date: Sun, 24 Mar 2002 15:48:33 +0000	[thread overview]
Message-ID: <marc-lartc-101698485406810@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101696074924194@msgid-missing>

Quoting Stef Coene <stef.coene@docum.org>:

... snip ...
   
   But you have to make sure that the box you are trying to ping, has a route to 
   you.  So it knows where to send the answer to the ping.  If i't doesn't know, 
   you have to add a route on the target box or masqueing the packets.


The hosts on the other side have default gateways,
which are the interfaces of the linux-router.
   
... snip ...


   > tcpdump is not installed on this box.  And the
   > iptables rules are disabled.  In other words they
   > are all set to accept.  If I use the iptables
   > command you suggest, will it actually log
   > anything?

   ipables -A INPUT -j LOG
   gives in /var/log/messages :
   
   Mar 24 16:16:03 lieve kernel: IN=eth0 OUT= 
   MAC\0:a0:c9:1a:9c:eb:00:50:da:d0:d8:95:08:00 SRC\x192.168.1.101 
   DST\x192.168.1.100 LEN\x164 TOS=0x00 PREC=0x00 TTLd IDd662 DF PROTO=TCP 
   SPT234 DPT`00 WINDOWc712 RES=0x00 ACK PSH URGP=0
   
   Stef


Okay, I don't know anything about iptables syntax,
and very little about ipchains syntax either.

I'll do that.  Should I do the samething for the
other chains (FORWARD, ACCEPT)?


Thanks,
kelly


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-03-24 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24  9:06 [LARTC] iproute2 is not routing Kelly Scroggins
2002-03-24 10:40 ` Stef Coene
2002-03-24 14:51 ` Kelly Scroggins
2002-03-24 15:19 ` Stef Coene
2002-03-24 15:48 ` Kelly Scroggins [this message]

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-101698485406810@msgid-missing \
    --to=kelly@cliffhanger.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.