public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Sid Boyce <sboyce@blueyonder.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19 and up to  2.6.20-rc2 Ethernet problems x86_64
Date: Tue, 2 Jan 2007 12:50:50 +0100	[thread overview]
Message-ID: <20070102115050.GA3449@ff.dom.local> (raw)
In-Reply-To: <4595CD1B.2020102@blueyonder.co.uk>

On Sat, Dec 30, 2006 at 02:21:15AM +0000, Sid Boyce wrote:
> Jarek Poplawski wrote:
> >On 28-12-2006 04:23, Sid Boyce wrote:
> >>
> >>I first saw the problem on the 64x2 box after upgrading to 2.6.19. The
> >>network appeared OK with ifconfig and route -n, but I had no network
> >>access. Pinging any other box, the box was responding, but no response
> >...
> >>barrabas:/usr/src/linux-2.6.20-rc1-git5 # ssh Boycie ifconfig
> >>Password:
> >>eth0      Link encap:Ethernet  HWaddr 00:0A:E4:4E:A1:42
> >>          inet addr:192.168.10.5  Bcast:255.255.255.255  
> >>          Mask:255.255.255.0
> >
> >This Bcast isn't probably what you need.
> >
> >Regards,
> >Jarek P.
> >
> >
> 
> Corrected on the one box where it was not correct, problem is still there.

There are many things to suspect yet:
- firewall,
- switch,
- routing,
- ifconfig,
- other misonfigured box,
- connecting
and so on.

I think you should try with some linux networking group
at first and if you really think it's driver then
netdev@vger.kernel.org (instead of linux-kernel@).

If you could send full ifconfig, route -n (or ip route
if you use additional tables) and tcpdump (all packets)
from both boxes while pinging each other and a few words
how it is connected (other cards, other active boxes in
the network?) maybe something more could be found.

Cheers,
Jarek P. 

PS: Sorry for late responding.

  parent reply	other threads:[~2007-01-02 11:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28  3:23 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64 Sid Boyce
2006-12-29  6:32 ` Jarek Poplawski
     [not found]   ` <4595CD1B.2020102@blueyonder.co.uk>
2007-01-02 11:50     ` Jarek Poplawski [this message]
2007-01-02 15:32       ` Sid Boyce
2007-01-03 10:48         ` Jarek Poplawski
2007-01-03 16:53           ` Sid Boyce
2007-01-04 11:46             ` Jarek Poplawski
2007-01-02 15:33       ` Sid Boyce
2007-01-02 15:39       ` Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2007-01-02 15:24 Sid Boyce
2007-01-02 15:41 Sid Boyce
2007-01-02 16:59 ` Len Brown
2007-01-02 22:57   ` Sid Boyce
2007-01-03  6:17     ` Len Brown
2007-01-05  9:09       ` Sid Boyce

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=20070102115050.GA3449@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyce@blueyonder.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox