From: Colin Ford <colin.ford@pipinghotnetworks.com>
To: eCos <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Error when adding eth1
Date: Wed, 31 Jan 2001 03:21:00 -0000 [thread overview]
Message-ID: <200101311120.LAA04605@cartman.pipinghotnetworks.com> (raw)
Hello All,
I've been trying to create a bridge using two ethernet
ports, eth0 and eth1. Eth0 gets its IP address and
configuration from a DHCP server where Eth1 has
it set statically using the net.cdl. Eth0 gets set correctly
but eth1 errors with:
SIOCIFADDR 2: File exists
The error originates from the file boot_support.c at line
449 from the code snipit:
// Must do this again so that [sub]netmask (and so default route)
// is taken notice of.
addrp->sin_addr = bp->bp_yiaddr; // The address BOOTP gave us
if (ioctl(s, SIOCSIFADDR, &ifr)) {
perror("SIOCIFADDR 2");
return false;
}
I can't see why this should fail? It seems to
do this twice in init_net and it works the first
time.
Can anyone help with this?
Many thanks,
Col.
--
===========================================
Colin Ford PipingHot Networks
Software Engineer +44 (0)1364 655510
reply other threads:[~2001-01-31 3:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200101311120.LAA04605@cartman.pipinghotnetworks.com \
--to=colin.ford@pipinghotnetworks.com \
--cc=ecos-discuss@sources.redhat.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).