Hi Patrik,
On 09/22/2015 12:12 AM, Patrik Flykt wrote:
On Fri, 2015-09-18 at 02:50 +0000, Daniel Wagner wrote:
The WiFi APs provided by the local ISP here in Utah does not like the
hostname in the DHCP Request packet. Without it the hostname I get the
ACK instead of the NACK as respond. Any ideas how we could handle this
problem? E.g. stop sending the hostname after the first round of retries
have failed?
Hm, sounds like very strange way of not handing out DHCP leases. This is
definitely a first for ConnMan, congratulations!
Yeah, I have a good hand for this :)
Isn't this funny, the
expected use cases are for DHCP updating DNS information but sabotaged
by this kind of interesting network setup ;-)
I don't know why this ISP their routers to behave like this but there
isn't much we can do.
There of course aren't any instructions from the ISP not to send
hostnames on the network? Do you have a tcpdump of the exchange to
share?
I have uploaded two traces. Both created on my Linux machine.
- This one is with an unmodified ConnMan:
http://www.monom.org/connman/dhcp-not-working.pcapng
- And this one is with a modified ConnMan which doesn't sent its
hostname:
http://www.monom.org/connman/dhcp-working.pcapng
How does a normal Windows machine cope with this?
I don't know. I have didn't have one around and didn't try it with MacOS.
Any possibilities to
get a packet dump and check how those machines work as sending a host
name is quite a normal operation...
Argh, I should have done that but forgot. And now it is too late. I am
back which means working network :)
FWIW, we could create an bug entry and add the traces and wait until we
get another user reporting problems. Without testing I'd rather not
change the current code. What do you think?
cheers,
daniel
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
