Hi,

Yes 


-----Original Message-----
From: Daniel Wagner [mailto:[email protected]] 
Sent: Wednesday, July 23, 2014 2:27 PM
To: [email protected]; Kirankumar Bobbu
Cc: Jukka Rissanen
Subject: Re: fix nfs boot issue from 1.19 to 1.17-reg

Hi Kirankumar,

On 07/23/2014 08:03 AM, Kirankumar Bobbu wrote:
> HI  Juka Rissanen,
> 
> Yes . I agree with ur solution.
> But I cant hardcode as " connmand -n -I eth1 "
> We may use eth0  or eth1 as nfs  n/w interface. 
> Same service must work for  non nfs boot and should manage all n/w interfaces.
> 
> If you have any patch to tweak this in systemd  scripts  . please 
> provide
> 
> Right now we cant move  to 1.24 as I may need recipe file as part of genivi . 
> That’s grey area for us.
> 
> Best Regards
> Kirankumar Bobbu
> 
> 
> -----Original Message-----
> From: Jukka Rissanen [mailto:[email protected]]
> Sent: Wednesday, July 23, 2014 11:11 AM
> To: [email protected]
> Cc: Kirankumar Bobbu
> Subject: Re: fix nfs boot issue from 1.19 to 1.17-reg
> 
> Hi Kiran,
> 
> On ke, 2014-07-23 at 10:27 +0530, Kirankumar Bobbu wrote:
>> Hi,
>>
>> I am getting the nfs boot issue[ connmand gets down the  nfs n/w interface ] 
>> because of the connman service . ( 1.17 )  as a part of genivi 5.0.2
>> I want to back port   the bugfix from 1.19 to 1.17.
>>
>> I found few patches:
>>
>> -
>> http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=1b8
>> 7
>> cd7535a360dae57e3238829c91476853af68
>> http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=39a
>> 6
>> 8b38aaa3188c3949506083bf469dd87b80f8
>> http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=fd9
>> f
>> 99e5320ef904d7fadabdfb401d07eeb3ef26
>>
>> Please let me know if am missing something more here?
>> Still I am not able to fix the issue.
>> Nfs boot  use  eth1 .
> 
> Try ignoring eth1 so that connman does not touch it and reset it as it is 
> used for nfs. Just start connman with "connmand -I eth1 ..."

If I understood you correctly, the interface name changes but the MAC address 
stays the same?


> [service_ethernet]
> Type = ethernet
> IPv4 = 11.0.0.1/255.255.255/11.0.0.1
> MAC = 00:04:4B:1D:EB:B8
> Nameservers = 8.8.8.8

If this is the case you could have a udev rule which always assigns the 
interface the same name based on the MAC address. Then you could use the trick 
with the 'connmand -I eth1'.

Thanks,
Daniel


-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may 
contain
confidential information.  Any unauthorized review, use, disclosure or 
distribution
is prohibited.  If you are not the intended recipient, please contact the 
sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman

Reply via email to