internetnews.com— A new DHCP client can recognize when a Linux user has disconnected from a particular DHCP server and look for a new connection. Cool! Gimme gimme.
Feb 22, 2006View in Crawl 4
In the case of wireless, auto DHCP can be a security issue. If someone is hosting a nosey AP that is named the same as all the other AP's around it [ex. at a university] and passes traffic you generate onto the internet, but holds onto packets and listens for unsecured passwords and the like. Most users would be oblivious.
I can honestly say that i've had tons more trouble connecting to networks through Windows than Linux, especially with Windows not aquiring a DHCP network address.WiFi is just starting to get support & pick up speed on Linux & swapping WiFi networks would be far easier with this though.Good stuff!
I run a program called ifplugd.... If I manually unplug my ethernet cord it automatically releases my ip, and if I plug it in somewhere else it will renew it. The cool thing about the program is that it acts much as wireless management tools for windows in the sense that you can set it to automatically grab an ip for any wireless networks in range, which saves you from all the "iwconfig essid myap" stuff.Nothing new to see here people... move along.
i'll give you a hint...ready?ready?....ready?...rc-update add ifplugd defaultif you unplug your ethernet, the iface goes down, and the DHCP lease goes away, plug it back in, and guess what? It dhcps, and the interface comes back up.
Okay, before everyone says "My OS does this already" here are some facts...Windows starts networking in PARALLEL with other services. If you have an IP or not, your network services start. This means some services will pause while the interface is waiting for an IP. Because the GUI is already running, the user has no idea.Linux (*NIX), however, is a different story. It's not better, maybe it's worse. I don't know. The point is, it's different. *NIX OSs have always had a network-centric lifestyle- they have always consumed or provided network services. Therefore, you want your network to be up before you try to consume or provide. On top of that, *NIX's typically evolve painfully slowly. This is good in some areas- stability, longevity, etc. However, in the arena of system start-up, we all know how bad it can be. That is changing, though, with several parallel init systems- the starting of the GUI as soon as possible, and other optimizations.As to DHCP delaying start-up, you can change that. Background the DHCP client daemon and you're off to the races. Hackish? Yes. More than that, if you do not get an IP later services will fail. Think of your system syncing its clock with pool.ntp.org without DNS or and IP. Obvious problem.
bigsteveFeb 23, 2006
In the case of wireless, auto DHCP can be a security issue. If someone is hosting a nosey AP that is named the same as all the other AP's around it [ex. at a university] and passes traffic you generate onto the internet, but holds onto packets and listens for unsecured passwords and the like. Most users would be oblivious.
tripmoneyukFeb 23, 2006
I can honestly say that i've had tons more trouble connecting to networks through Windows than Linux, especially with Windows not aquiring a DHCP network address.WiFi is just starting to get support & pick up speed on Linux & swapping WiFi networks would be far easier with this though.Good stuff!
swillyFeb 23, 2006
I run a program called ifplugd.... If I manually unplug my ethernet cord it automatically releases my ip, and if I plug it in somewhere else it will renew it. The cool thing about the program is that it acts much as wireless management tools for windows in the sense that you can set it to automatically grab an ip for any wireless networks in range, which saves you from all the "iwconfig essid myap" stuff.Nothing new to see here people... move along.
blhackFeb 23, 2006
i'll give you a hint...ready?ready?....ready?...rc-update add ifplugd defaultif you unplug your ethernet, the iface goes down, and the DHCP lease goes away, plug it back in, and guess what? It dhcps, and the interface comes back up.
drdabblesFeb 24, 2006
Okay, before everyone says "My OS does this already" here are some facts...Windows starts networking in PARALLEL with other services. If you have an IP or not, your network services start. This means some services will pause while the interface is waiting for an IP. Because the GUI is already running, the user has no idea.Linux (*NIX), however, is a different story. It's not better, maybe it's worse. I don't know. The point is, it's different. *NIX OSs have always had a network-centric lifestyle- they have always consumed or provided network services. Therefore, you want your network to be up before you try to consume or provide. On top of that, *NIX's typically evolve painfully slowly. This is good in some areas- stability, longevity, etc. However, in the arena of system start-up, we all know how bad it can be. That is changing, though, with several parallel init systems- the starting of the GUI as soon as possible, and other optimizations.As to DHCP delaying start-up, you can change that. Background the DHCP client daemon and you're off to the races. Hackish? Yes. More than that, if you do not get an IP later services will fail. Think of your system syncing its clock with pool.ntp.org without DNS or and IP. Obvious problem.
pacobellAug 31, 2006
You lose for spelling "ridiculous" like that =P
pacobellAug 31, 2006
Obviously not you, so FO.