Hi Jukka,

On 19.03.2015 09:02, Jukka Rissanen wrote:
> Hi Andreas,
> 
> On ke, 2015-03-18 at 16:27 +0100, Andreas Oberritter wrote:
>> Booting an nfsroot with connman requires passing -I eth0 to ignore
>> the interface. This isn't very nice, for at least the following
>> reasons:
>>
>> * A User interface based on connman is led to believe that there's no
>>   network interface and thus connman seems to be offline when it's not.
>> * The DHCP lease obtained by the kernel won't get renewed.
>> * DNS servers won't get obtained from DHCP, thus requiring a workaround
>>   to copy /proc/net/pnp to /etc/resolv.conf and passing -r to connmand.
>>
>> Therefore change behaviour to restrict interfaces passed with -I to
>> read-only ioctls.
>>
> 
> I have seen this NFS thing being asked before and one workaround has
> been to use the -I option to ignore the NFS link. This is kind of wrong
> as then the link is not managed and used by ConnMan any more.
> 
> I just wonder if we could tweak device.c:cleanup_devices() function to
> skip the NFS link instead of this patch that changes lot of things in
> the code. The cleanup_devices() is cleaning the links when ConnMan
> starts so that connmand has a known initial state. Perhaps we could skip
> the cleaning of NFS link if ConnMan notices that there is such a link.
> This would be less invasive than having these read checks all over the
> place.

I'll try this and report back.

Do you think I should add a new command-line option to pass the
interface to ConnMan? Identifying the interface used for NFS requires
parsing /proc/cmdline and, in case of static addresses, knowledge about
the interfaces' IP address. Until now I preferred to let the shell do it.

Thanks,
Andreas
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman

Reply via email to