Il 18/06/2014 12:01, Tomasz Bursztyka ha scritto:
Hi,
FallBackNameserver are used only if you don't have any other dns from
>>other connection like 3g. Correct?
>
>
>That's correct, but it is also used by default (if present) as the dns
>settings when tethering.
>Have a look at src/tethering.c from line 234 to 261
>
I was thinking that it's only used if the list is empty
There is no check done if any nameservers list is empty or not. In
tethering, it does not
care directly about it: it only cares about the dnsproxy and this
FallbackNameservers.
Hi Tomasz,
sorry for a so late reply, I have been busy on another project so I
can't try your suggestion
For me doesn't work as expected
Here the DHCP messages exchanged
################################################
DHCP discover sent - Client MAC : 08:00:27:dd:78:48
DHCP offer received - Offered IP : 192.168.0.3
DHCP offer details
----------------------------------------------------------
DHCP offered IP from server - 192.168.0.3
Next server IP(Probably TFTP server) - 0.0.0.0
DHCP server - 1.0.168.192
Lease time - 1 Days 0 Hours 0 Minutes
Subnet mask - 255.255.255.0
Router/gateway - 192.168.0.1
----------------------------------------------------------
DHCP request sent - Client MAC : 08:00:27:dd:78:48
DHCP ack received - Acquired IP: 192.168.0.3
DHCP ack details
----------------------------------------------------------
DHCP offered IP from server - 192.168.0.3
Next server IP(Probably TFTP server) - 0.0.0.0
DHCP server - 1.0.168.192
Lease time - 1 Days 0 Hours 0 Minutes
Subnet mask - 255.255.255.0
Router/gateway - 192.168.0.1
----------------------------------------------------------
################################################
Here the messages exchange with a common ISC DHCP Server from another
machine
################################################
DHCP discover sent - Client MAC : 14:da:e9:4f:14:4c
DHCP offer received - Offered IP : 192.168.14.34
DHCP offer details
----------------------------------------------------------
DHCP offered IP from server - 192.168.14.34
Next server IP(Probably TFTP server) - 0.0.0.0
DHCP server - 192.168.14.1
Lease time - 3 Days 0 Hours 0 Minutes
Subnet mask - 255.255.255.0
Router/gateway - 192.168.14.1
DNS server - 192.168.14.1
----------------------------------------------------------
DHCP request sent - Client MAC : 14:da:e9:4f:14:4c
DHCP ack received - Acquired IP: 192.168.14.34
DHCP ack details
----------------------------------------------------------
DHCP offered IP from server - 192.168.14.34
Next server IP(Probably TFTP server) - 0.0.0.0
DHCP server - 192.168.14.1
Lease time - 3 Days 0 Hours 0 Minutes
Subnet mask - 255.255.255.0
Router/gateway - 192.168.14.1
DNS server - 192.168.14.1
----------------------------------------------------------
################################################
Please notice 2 things
1) There is no "DNS Server" line in the response from connman
2) the line "DHCP Server" has the right IP in a wrong order
(1.0.168.19). I suppose thsi has to do with byte ordering
What I can check on connman to add the DNS section
Or better can you point me on the right source file in order to verify
the code?
Thank you
--
Andrea Cappelli
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
