Hi,

please do not top post in this mailing list.


On ke, 2014-07-23 at 11:33 +0530, 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

This systemd tweaking is an distro issue and not part of connman. Please
consult your local genivi expert for advice.


Cheers,
Jukka


> 
> 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=1b87
> > cd7535a360dae57e3238829c91476853af68
> > http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=39a6
> > 8b38aaa3188c3949506083bf469dd87b80f8
> > http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=fd9f
> > 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 ..."
> 
> Also I would recommend that you upgrade to 1.24 if possible, lot of bugs have 
> been fixed since 1.19.
> 
> Cheers,
> Jukka
> 
> 
> 
> 
> -----------------------------------------------------------------------------------
> 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