All of lore.kernel.org
 help / color / mirror / Atom feed
From: "glynn" <glynn@itextron.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Gre Tunneling Problem
Date: Mon, 07 Jan 2002 09:40:47 +0000	[thread overview]
Message-ID: <marc-lartc-101048197007821@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101039544916808@msgid-missing>

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

Glynn

----- Original Message -----
From: "Christoph Simon" <ciccio@kiosknet.com.br>
To: "glynn" <glynn@itextron.com>
Cc: <jpatterson@asgardgroup.com>; <lartc@mailman.ds9a.nl>
Sent: Tuesday, January 08, 2002 5:14 PM
Subject: Re: [LARTC] Gre Tunneling Problem


> On Mon, 7 Jan 2002 14:35:08 +0800
> "glynn" <glynn@itextron.com> wrote:
>
> > now im trying to install a new slackware 7, maybe it work :(
>
> I'm running debian here. But I do think, you should try to trace the
> problem. Send a ping and sniff on each interface, step by step, where
> the packets go and what they look like. Trying different distributions
> seems little reasonable for me, but mabe you want to recompile the
> kernel just to make sure, everything's OK, no strange patches, etc.
>
> --
> 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/

  parent reply	other threads:[~2002-01-07  9:40 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 [this message]
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
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-101048197007821@msgid-missing \
    --to=glynn@itextron.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.