From: Grant Edwards <grante@visi.com>
To: Nick Barnes <Nick.Barnes@pobox.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Notes on static configuration of an eCos network interface
Date: Mon, 17 Jul 2000 08:52:00 -0000 [thread overview]
Message-ID: <20000717155244.A29492@visi.com> (raw)
In-Reply-To: <25482.963837944@raven.ravenbrook.com>
> Notes on static configuration of an eCos network interface
> The siaddr and giaddr fields of a BOOTP message are irrelevant to
> configuring a network interface: they are used for talking to the
> BOOTP server (e.g. for TFTPing a kernel).
Aaargh. That's why my routing table isn't getting initialized.
> init_net() should initialize the interface as follows:
>
> SIOCSIFADDR, yiaddr
> SIOCSIFNETMASK, TAG_SUBNET_MASK
> SIOCSIFBRDADDR, TAG_IP_BROADCAST
> SIOCADDRT, 0, 0, TAG_GATEWAY
Right now, I'm building a fake bootp record and passing it to
init_net(). This seems to be way more work than it's worth
(especially since it's not right), so I'm going to throw out
all of the fake bootp stuff and just duplicate the code in
net_init(), passing the right IP addresses in the ioctl() calls.
It will end up being a lot smaller and simpler that way. Is
there any reason I shouldn't do that?
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2000-07-17 8:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 5:45 Nick Barnes
2000-07-17 6:59 ` Bart Veer
2000-07-17 7:07 ` [ECOS] Notes on static configuration of an eCos network inte Gary Thomas
2000-07-18 5:52 ` [ECOS] Notes on static configuration of an eCos network interface Nick Barnes
2000-07-18 8:03 ` Grant Edwards
2000-07-17 8:52 ` Grant Edwards [this message]
2000-07-17 9:03 ` [ECOS] Notes on static configuration of an eCos network inte Gary Thomas
2000-07-17 9:28 ` Andrew Lunn
2000-07-17 9:40 ` Grant Edwards
2000-07-17 9:47 ` Andrew Lunn
2000-07-17 9:29 ` Grant Edwards
2000-07-17 9:45 ` Gary Thomas
2000-07-17 10:01 ` Grant Edwards
2000-07-17 9:45 ` [ECOS] Notes on static configuration of an eCos network interface Hugo 'NOx' Tyson
2000-07-20 7:00 ` Hugo 'NOx' Tyson
2000-07-20 9:57 ` Bart Veer
2000-07-20 11:00 ` Hugo 'NOx' Tyson
2000-07-20 11:19 ` Bart Veer
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=20000717155244.A29492@visi.com \
--to=grante@visi.com \
--cc=Nick.Barnes@pobox.com \
--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).