beaker67
asked on
Wireless connection says it gets no IP on startup, but it does work after Linux finishes loading
Not really any urgent or important question - I'm just curious as to why. When the system is starting, it gets to the point where it says it is configuring the firewall, and it says that "wlan0" has no IP address yet. Yet some 10 or so lines later, it mentions something about "spoofing" (or maybe "spoof proctection" or something like that...) and gives the right IP address for the connection. Yes, it is turned on even before I start the computer.
I really wouldn't care much about this if it weren't for the fact that it was doing the same thing with my Ethernet connection. My laptop has built-in Ethernet and wireless connections, and in order to get the wireless to work I ended up disabling the Ethernet because it was being assigned the same address and this seemed to confuse the system. Anyway, when I was still using both, the ethernet connection would be reported as having no IP address at startup, but the wireless *did*. Yet, the ethernet connection worked, and the wireless didn't.
Again, this really isn't important, but I am curious...
I really wouldn't care much about this if it weren't for the fact that it was doing the same thing with my Ethernet connection. My laptop has built-in Ethernet and wireless connections, and in order to get the wireless to work I ended up disabling the Ethernet because it was being assigned the same address and this seemed to confuse the system. Anyway, when I was still using both, the ethernet connection would be reported as having no IP address at startup, but the wireless *did*. Yet, the ethernet connection worked, and the wireless didn't.
Again, this really isn't important, but I am curious...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I originally had both ethernet (eth0) and wireless (wlan0) connections enabled. The ethernet connection would allow me to connect to the internet, but the wireless connection wouldn't. But, at startup (while starting the firewall) the ethernet was listed as not yet having an IP address, while the wireless did have one. In order to get wireless to work, I ended up having to disable the ethernet (apparently they were on the same subnet, or something, and this confused linux) - see all the details of that here - https://www.experts-exchange.com/questions/20957801/Internet-connection-in-Linux.html
Although you may be right - the firewall may simply be on before the connection has time to start - although it is turned on even before I turn the computer on.