If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
Yes, the resolv.conf file is created by running DHCP. If using a static IP and DHCP has never been run, you would have to create the file. So in almost all cases, if DHCP has been successfully run there will be a resolv.conf file, but if it has never been run, then you would have to create the file to use a static IP. I will add a note to the howto.
BTW /etc/resolvconf is a directory and not a file.
HowTo worked fine. Thanks very much. But FYI, there is no network-manager-kde in 9.04, at least on my system. And people should be warned that when they remove network-manager their networking component will (understandably) crash. Don't panic because KDE will restart within a few seconds, and you will not lose your terminal.
The problem with that is, I don't really have that much experience with wireless. I do use it on my laptop, and I have a couple of USB wireless devices lying around, but I really have not experimented with them enough to feel qualified on how to write a "howto". Actually, most wireless problems seem to be getting the device to work, and getting the the security set up. Both of which are somewhat beyond the scope of this howto. Most folks report that Wicd is the best way to go.
The problem with that is, I don't really have that much experience with wireless. I do use it on my laptop, and I have a couple of USB wireless devices lying around, but I really have not experimented with them enough to feel qualified on how to write a "howto". Actually, most wireless problems seem to be getting the device to work, and getting the the security set up. Both of which are somewhat beyond the scope of this howto. Most folks report that Wicd is the best way to go.
understood bro. i have wicd running btw. was working all the while...until my laptop battery was drained and somehow the wireless interface - eth1 disappeared. now the wireless nic , bcm 4312 still shows up when i do 'hwinfo', except i dont know how to assign it as eth1?
Thanks for the howto Detonate. I recently updated my partner's machine to 9.04 and so was back to DHCP which doesn't work well for my taste and local setup. No problem. I'm quite familiar with /etc/network/interfaces so I just went to fix it, but got a big surprise when I saw what it looks like now! Anyway, I found your excellent information, the key point of which (to me) was to "sudo apt-get remove network-manager". That's when the screen stopped responding and I had a really DUH moment. lol Using telnet to configure a remote machine's network connection has it's drawbacks. Suffice it to say that after sawing off the branch that I was sitting on, I had to leave my chair and actually go upstairs and sit at the relevant machine.
Comment