This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Andrew, The attached patch now allows the DNS negotiation to be configurable as you described. However, can you please reconsider allowing the new function? I'd like to keep it for the following reasons: 1) It allows the application to see the negotiatied address. We display the address to the user of our product. 2) Having PPP invoke cyg_dns_res_init limits the application's flexibility. For example, we have both an ethernet port and PPP port active simultaneously. We don't want to start using the PPP DNS address if the ethernet DNS address is still good. 3) It provides an extensible mechanism to get the negotiated values from the PPP stack. For example, it's a very simple way to get the local and peer IP address. Also, if someone wants to enable the other aspects of RFC1877, it could be used for those addresses as well. Thanks, -- Matt --- Andrew Lunn <andrew@lunn.ch> wrote: > Could you make this configurable please. Maybe > something like > CYGPKG_PPP_NS_NEGOTIATE which has a default value of > CYGINT_ISO_DNS. > > The DHCP/BOOTP code does this differently. It > automatically passes the > address of the DNS server to the DNS client. See > bootp_support.c:559. > Could the ppp code do the same? > > Thanks > Andrew > __________________________________ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html
Attachment:
rfc1877_1.pat
Description: 1965913308-rfc1877_1.pat
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |