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
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
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
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
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
>
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