host addresses at
the moment (A or records). Would it be best for me to modify core/dns.c,
or implement my own separate code?
--
Craig McQueen
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
om.", then it wouldn't try "server.com.example.com".
Note that the current functions in dns.c will fail a DNS look-up given a string
that ends with a trailing dot. Technically is this correct or incorrect? See
the following which discusses trailing dots in domain names:
h
if lwIP supporting DNS look-ups in RFC 1035 encoding would somehow
help support internationalized DNS names.
--
Craig McQueen
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
rough idea what would be accepted.)
--
Craig McQueen
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
goldsi...@gmx.de wrote:
> On 12.11.2018 01:04, Craig McQueen wrote:
> > DHCP option 120 provides SIP server address(es), which may be an IP
> address or a DNS name. If it's a DNS name, then it is already encoded in the
> encoding used for DNS look-ups (RFC 1035). See
], looking for any
pre-existing DHCP_OPTION_PARAMETER_REQUEST_LIST. Then I can insert the extra
options into it. It's a bit fiddly, but I've got it working. Does that sound
like a reasonable thing to do in LWIP_HOOK_DHCP_APPEND_OPTIONS()?
--
Craig McQueen
_
goldsi...@gmx.de wrote:
> On 11.11.2018 23:41, Craig McQueen wrote:
> > I'd like to do DNS lookups of other RR types, such as SRV, PTR or TXT
> records. SRV is my immediate interest, though SRV, PTR and TXT would
> facilitate doing DNS-SD queries in future. What would be n
I wrote:
> goldsi...@gmx.de wrote:
> > On 11.11.2018 23:41, Craig McQueen wrote:
> > > I'd like to do DNS lookups of other RR types, such as SRV, PTR or
> > > TXT
> > records. SRV is my immediate interest, though SRV, PTR and TXT would
> > facilitate d
. Looking in the lwIP code at nd6_process_autoconfig_prefix(), it looks as though it does SLAAC with the host part of the address copied from the link-local address. Is there any way to do a privacy extension address instead?
--
Craig McQueen
Craig