Re: DHCP & hostname faceplant

2015-10-21 Thread Patrik Flykt
Hi, On Thu, 2015-10-08 at 01:31 -0600, Daniel Wagner wrote: > 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

Re: DHCP & hostname faceplant

2015-10-21 Thread Daniel Wagner
On 10/21/2015 12:19 PM, Patrik Flykt wrote: > On Thu, 2015-10-08 at 01:31 -0600, Daniel Wagner wrote: >> 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

Re: DHCP & hostname faceplant

2015-10-21 Thread Jussi Kukkonen
On 21 October 2015 at 13:27, Daniel Wagner wrote: > On 10/21/2015 12:19 PM, Patrik Flykt wrote: > > Looks like there are two ways to tame this: have a main.conf entry or > > retry without sending a hostname. In the latter case people expecting > > their host name to be added to

Re: DHCP & hostname faceplant

2015-10-08 Thread Daniel Wagner
Hi Patrik, On 09/22/2015 12:12 AM, Patrik Flykt wrote: On Fri, 2015-09-18 at 02:50 +, 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

Re: DHCP & hostname faceplant

2015-09-22 Thread Patrik Flykt
Hi, On Fri, 2015-09-18 at 02:50 +, 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 >

DHCP & hostname faceplant

2015-09-17 Thread Daniel Wagner
Hi, 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