From: Christoph Simon <ciccio@kiosknet.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Gre Tunneling Problem
Date: Tue, 08 Jan 2002 09:48:34 +0000 [thread overview]
Message-ID: <marc-lartc-101048334710841@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101039544916808@msgid-missing>
On Mon, 7 Jan 2002 17:40:47 +0800
"glynn" <glynn@itextron.com> wrote:
> when you configure that tunneling did you reconfigure your kernel? what
> should i enable in my kernel? by the way when i log-on to the linux A, I
> could ping the linux B eth0(internet) and eth1(let say "192.168.1.1")
> but when i ping the "192.168.1.2" which is a windows workstation
> connected to hub it wont pass thru. how do i sniff the interface where
> the packets go, can you help me about that pls. Thanks
So you can ping from 192.168.2.1 to 192.168.1.1, this is good, as it
means that the tunnel definitively is working.
Now, if you try to ping from 192.168.2.1 to 192.168.1.2, the Windows
box, it seems to fail. First I would try to ping from 192.168.1.1 to
192.168.1.2, just to make sure, everything is working fine locally. If
this works too, I would make tcpdump listen at the external interface
of 192.168.2.1. Does the packet actually go out? If not, the routing
or filter problem must be there. If it works, I'd listen on the
external interface of 192.168.1.1; obviously these must arrive because
the tunnel is working and the packet left at the other side. Now you
can listen to the internal interface, seeing if the packet is actually
being forwarded. If this fails, your problem is routing, filtering or
forwarding on 192.168.1.1. Don't know how to sniff on a Windows, but
as the ping from 192.168.1.1 to 192.168.1.2 presumibly worked, there
shouldn't be a need.
If you have access and there is no other traffic, a much simpler
method would be just to watch the leds on the modems, network cards,
hubs, etc. This will help finding out where your problem is. As you
can ping the first computer after the tunnel, I feel sure, the tunnel
is working fine, the problem must be in another place, probably a
stupid little detail.
Note that the suggestion of introducing a different network address
for the tunnel interfaces themselves will slightly complicate
routing. But if you pay attention, this shouldn't be a problem.
--
Christoph Simon
ciccio@kiosknet.com.br
---
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-01-08 9:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 9:39 [LARTC] Gre Tunneling Problem glynn
2002-01-07 0:58 ` glynn
2002-01-07 1:48 ` glynn
2002-01-07 4:04 ` glynn
2002-01-07 6:28 ` glynn
2002-01-07 6:35 ` glynn
2002-01-07 9:40 ` glynn
2002-01-07 10:21 ` glynn
2002-01-07 11:41 ` Christoph Simon
2002-01-08 0:56 ` Christoph Simon
2002-01-08 1:01 ` Joe Patterson
2002-01-08 1:07 ` glynn
2002-01-08 1:15 ` glynn
2002-01-08 1:18 ` Christoph Simon
2002-01-08 4:54 ` Greg Scott
2002-01-08 7:28 ` glynn
2002-01-08 9:14 ` Christoph Simon
2002-01-08 9:48 ` Christoph Simon [this message]
2002-01-08 12:40 ` Greg Scott
2002-01-09 2:44 ` Greg Scott
2002-01-09 3:02 ` glynn
2002-01-09 14:27 ` Michael T. Babcock
2002-01-09 17:49 ` Greg Scott
2002-01-09 17:58 ` Michael T. Babcock
2002-01-09 18:28 ` Greg Scott
2002-01-09 18:43 ` Michael T. Babcock
2002-01-09 19:40 ` Greg Scott
2002-01-11 14:21 ` Greg Scott
2002-01-11 15:20 ` Joe Patterson
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-101048334710841@msgid-missing \
--to=ciccio@kiosknet.com.br \
--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.