public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Dan Conti" <danc@iobjects.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] DHCP w/ Win2K server?
Date: Wed, 28 Nov 2001 14:39:00 -0000	[thread overview]
Message-ID: <D8DFF0AFE792914996F997E68FEC3A48F4C4@bunker.iobjects.com> (raw)
Message-ID: <20011128143900.jJXm_pckzNreReA8Z3pVUcOmVs71F_a5C2fB_p11xbg@z> (raw)

I think we saw this at one point. IIRC (it's been a while), the eCos
DHCP client assumes a gateway will be returned, and with linux dhcp
servers one is returned by default, but on win2k it isn't. I believe it
says in the spec that you actually are supposed to request a gateway
server ip if you want one, making this an eCos bug?

In net/tcpip/current/src/lib/dhcp_prot.c, around line 596 (in case
DHCPSTATE_REQUESTING), try adding the following line:

	    set_fixed_tag( xmit, TAG_DHCP_PARM_REQ_LIST, TAG_GATEWAY, 1
);

to add the gateway request to the DHCP packet. I dont know if there is a
way to adjust the win2k dhcp server configuration to automagically give
this out though.

> -----Original Message-----
> From: Grant Edwards [ mailto:grante@visi.com ]
> Sent: Wednesday, November 28, 2001 2:35 PM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] DHCP w/ Win2K server?
> 
> 
> 
> From the "MS Windows continues to deteriorate" department...
> 
> I've had a customer complain that eCos DHCP client doesn't get
> a gateway address when used with a Win2K server (WinNT is OK).
> I've verified it by capturing network traffic between eCos and
> our office's Win2K server: no gateway is sent by the DHCP
> server. (Though BOFH claims it is.)
> 
> Has anybody else seen this problem?
> 
> Is there a setting in the Win2K DHCP server that needs to be
> chanaged?  Both the customer and our BOFH claim that their
> respective DHCP servers are configured to send gateway
> addresses.
> 
> Needless to say, it works fine with Linux...  ;)
> 
> -- 
> Grant Edwards
> grante@visi.com
> 

             reply	other threads:[~2001-11-28 14:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19  2:48 Dan Conti [this message]
2001-11-19  3:50 ` Grant Edwards
2001-11-28 14:56   ` Grant Edwards
2001-11-28 14:39 ` Dan Conti
  -- strict thread matches above, loose matches on Subject: below --
2001-11-26  4:05 Dan Conti
2001-11-30 12:17 ` Dan Conti
2001-11-22  4:33 Dan Conti
2001-11-23  6:21 ` Hugo Tyson
2001-11-23  7:44   ` Hugo Tyson
2001-11-25 19:40     ` Grant Edwards
2001-11-25 20:38       ` Hugo Tyson
2001-11-25 23:57         ` Grant Edwards
2001-11-30  9:28           ` Grant Edwards
2001-11-30  9:17         ` Hugo Tyson
2001-11-30  9:05       ` Grant Edwards
2001-11-30  5:12     ` Hugo Tyson
2001-11-24  4:58   ` Hugo Tyson
2001-11-30  7:08     ` Hugo Tyson
2001-11-30  2:52   ` Hugo Tyson
2001-11-29 13:10 ` Dan Conti
2001-11-19  3:01 Dan Conti
2001-11-22  4:27 ` Hugo Tyson
2001-11-29 10:18   ` Hugo Tyson
2001-11-28 14:40 ` Dan Conti
2001-11-19  2:02 Grant Edwards
2001-11-19  2:55 ` Gary Thomas
2001-11-19  3:48   ` Grant Edwards
2001-11-28 14:44     ` Grant Edwards
2001-11-28 14:39   ` Gary Thomas
2001-11-28 14:30 ` Grant Edwards

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=D8DFF0AFE792914996F997E68FEC3A48F4C4@bunker.iobjects.com \
    --to=danc@iobjects.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).