From: "Andy Gospodarek" <andy@greyhouse.net>
To: "DI BACCO ANTONIO - technolabs" <Antonio.DiBacco@technolabs.it>
Cc: "Florian A. Voegel" <fvoegel@carangul.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Network is blocked till ping is issued
Date: Thu, 30 Aug 2007 08:52:03 -0400 [thread overview]
Message-ID: <bdfc5d6e0708300552g71a995c9x10f17322613ca9c1@mail.gmail.com> (raw)
In-Reply-To: <F1F6EC0C8B75034F9E3A79FC85122E8EA1869B@aquib01a>
On 8/30/07, DI BACCO ANTONIO - technolabs <Antonio.DiBacco@technolabs.it> wrote:
> > sounds to me like it could be a classical ARP problem. Have you
> checked the ARP cache on the non-Linux
> > machine?
>
> But if Linux received the SYN packet of TCP connection, shouldn't the
> Linux machine reply to the source mac address of SYN packet with a
> SYN,ACK packet?
>
No. You are confusing Ethernet frames and IP packets a little bit.
If a Linux machine receives a SYN from a remote host (not on the same
network) then the Linux machine needs to ARP for the router that is
listed as the default route in the routing table.
If no such default route exists, you will not be able to reach the
remote host. If the router doesn't reply to your ARP request, you
will not be able to reach the remote host.
Check to make sure you are not having either one of these problems.
next prev parent reply other threads:[~2007-08-30 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 17:27 Network is blocked till ping is issued DI BACCO ANTONIO - technolabs
2007-08-29 18:34 ` Network is blocked till ping is issued(update) DI BACCO ANTONIO - technolabs
2007-08-29 23:07 ` Network is blocked till ping is issued Florian A. Voegel
2007-08-30 6:24 ` DI BACCO ANTONIO - technolabs
2007-08-30 12:52 ` Andy Gospodarek [this message]
2007-08-30 13:59 ` DI BACCO ANTONIO - technolabs
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=bdfc5d6e0708300552g71a995c9x10f17322613ca9c1@mail.gmail.com \
--to=andy@greyhouse.net \
--cc=Antonio.DiBacco@technolabs.it \
--cc=fvoegel@carangul.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).