public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] connect() to machine outside local network
Date: Fri, 14 Jul 2000 05:30:00 -0000	[thread overview]
Message-ID: <ptlmz429be.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <9513.963574635@raven.ravenbrook.com>


Nick Barnes <Nick.Barnes@pobox.com> writes:
> It seems to me that build_bootp_record() in network_support.c should
> 
>         add_tag(vp, TAG_GATEWAY, ...)
> 
> and that its failure to do so could account for my problems here.
> 
> This from single stepping through most of init_all_network_interfaces().

This is if it's statically configured, right?  You're right, that makes
perfect sense, I'll see to it.  BTW, full DHCP coming real soon...

	- Huge

> At 2000-07-12 17:26:43+0000, Cedric Berger writes:
> > That may mean that your default gateway is *not* on your local subnet.
> > Nick Barnes wrote:
> > 
> > > At 2000-07-12 14:36:47+0000, Nick Barnes writes:
> > > > connect() works OK for local machines but gives me EHOSTUNREACH
> > > > outside the local network.
> > >
> > > After some single-stepping in the TCP/IP stack, I think this is an
> > > eCos problem, not a problem with my local network.  rtalloc() inside
> > > ip_output() is returning 0.

  reply	other threads:[~2000-07-14  5:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <396CAA52.A429F2C6@berger.to>
2000-07-14  4:37 ` Nick Barnes
2000-07-14  5:30   ` Hugo 'NOx' Tyson [this message]
2000-07-14  5:34     ` Nick Barnes
2000-07-14  5:39     ` Andrew Lunn
2000-07-14  8:45       ` Hugo 'NOx' Tyson
2000-07-14  9:17         ` Andrew Lunn
2000-07-14  6:37     ` Nick Barnes
2000-07-12  7:36 Nick Barnes
2000-07-12  7:44 ` Gary Thomas
2000-07-12  7:48   ` Nick Barnes
2000-07-12  9:10 ` Nick Barnes

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=ptlmz429be.fsf@masala.cygnus.co.uk \
    --to=hmt@cygnus.co.ukx \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).