Delays in interface going to RUNNING state

		LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
Delays in interface going to RUNNING state

Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

Are you new to LinuxQuestions.org? Visit the following links:
Site Howto | Site FAQ | Sitemap | Register Now

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.

Exclusive for LQ members, get up to 45% off per month. Click here for more info.

Search this Thread

02-22-2010, 09:17 AM	#1
Skaperen Senior Member Registered: May 2009 Location: center of singularity Distribution: Xubuntu, Ubuntu, Slackware, Amazon Linux, OpenBSD, LFS (on Sparc_32 and i386) Posts: 2,684 Blog Entries: 31 Rep:	Delays in interface going to RUNNING state I've been doing some tests ... rebooting with scripts in place to log the output of ifconfig. What I am seeing is that sometimes some interfaces are not in the RUNNING state by the time network daemons would be starting up. The problem is that it appears that while IP addresses can be configured for the interface, the IPv6 link-local address is not. This is with Ubuntu-9.10 server ... at least for now. Is it correct that the kernel itself is configuring the IPv6 link-local address on the interface ... and only doing so when the interface goes into RUNNING state? Any idea how to have scripts to start network daemons be automatically delayed until all UP interfaces are in RUNNING state and the IPv6 link-local address is present ... or a timeout period is exhausted?

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is Off HTML code is Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to get link state of interface	avinash_ag1985	Linux - Networking	6	11-16-2010 02:52 PM
iptables -I INPUT -p tcp --dport 22 -i eth0 -m state --state NEW -m recent --set	deadeyes	Linux - Server	14	07-29-2009 04:30 AM
Not able to put my zone in running state. boot gives an error	dningale	Solaris / OpenSolaris	19	08-20-2008 05:29 AM
LXer: State by state, Microsoft responds to creeping threat	LXer	Syndicated Linux News	0	05-01-2007 07:16 AM
LXer: CA State NOT out of the running in the OSS/Linux races	LXer	Syndicated Linux News	0	09-06-2006 05:54 PM

All times are GMT -5. The time now is 05:53 PM.

Main Menu

(Con't)

My LQ

Write for LQ

LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.

Main Menu

Syndicate

Latest Threads

LQ News

Twitter: @linuxquestions