ALT Linux users (in English only)
 help / color / mirror / Atom feed
From: Michael Shigorin <mike@osdn.org.ua>
To: djbouley <djbouley@shaw.ca>
Cc: community-en@altlinux.org
Subject: [Comm-en] Re: Sorry to trouble you. but....
Date: Tue, 29 Apr 2003 20:23:41 +0300
Message-ID: <20030429172341.GE11320@osdn.org.ua> (raw)
In-Reply-To: <200304271112.16533.djbouley@shaw.ca>

On Sun, Apr 27, 2003 at 11:12:16AM -0600, djbouley wrote:
> I was wondering if you could offer any further advice to me as
> to why I can't seem to get network sharing working on my
> system.

I'm sorry for being *really* slow -- got holidays and a bunch of
work to finish before them.

> > >Could you do the following on any client:
> > >ping 192.168.0.1
> No response from ping.  However, I can ping the client
> (192.168.0.4) from the host PC.  It seems to "see" the client
> okay.

Seems like firewall is "completely up" and blocking pings.

> > >tracert 81.222.130.6 (win)
> > >/usr/sbin/traceroute or
> > >/usr/sbin/tracepath 81.222.130.6 (linux)
> This pauses for a moment (30 - 40 seconds) then gives me an output of:
>         1  192.168.0.1 0.836 ms 0.45 ms 0.383 ms

so 192.168.0.1 is here (on some interface).  Looks like really
blocked.  OK, so let's look there.

> When I do this, and try the traceroute on the client, I get a response of 
> 19 packets received by filter
> 0 packets dropped by kernel

Ugh.

iptables -L -v
iptables -L -v -t nat

?

> I know you're a very busy guy.  If you have some time later on,
> I'd really appreciate your input.

Ahem.  You'd reply to the list too, someone could be better than
me on that side :)

-- 
 ---- WBR, Michael Shigorin <mike@altlinux.ru>
  ------ Linux.Kiev http://www.linux.kiev.ua/


           reply	other threads:[~2003-04-29 17:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200304271112.16533.djbouley@shaw.ca>]

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=20030429172341.GE11320@osdn.org.ua \
    --to=mike@osdn.org.ua \
    --cc=community-en@altlinux.org \
    --cc=djbouley@shaw.ca \
    /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

ALT Linux users (in English only)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community-en/0 community-en/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community-en community-en/ http://lore.altlinux.org/community-en \
		community-en@lists.altlinux.org community-en@lists.altlinux.ru community-en@lists.altlinux.com
	public-inbox-index community-en

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community-en


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git