Slackware :: Configure System To Start Wlan0 Instead Of Eth0?
Nov 29, 2010
I'm running Slackware-13.1 on my laptop. Connection to my network is via wlan0, a cable in most cases not pluged in.When starting the system the first attempt to configure the network is via eth0, which ends with dhcpcd timing out since there is no cable pluged in. Afterwards wlan0 is set up properly.
I have installed ifplugd, which is a daemon who connects to ethernet only if a cable is connected. With Gentoo this works out of the box. With Slackware ifplugd is started after rc.inet1 (probably). So the the system still tries to connect via ethernet before connecting to the wireless network.
I have also installed wicd.How can I manage that wlan0 is prefered over eth0?I noticed that neither wicd nor ifplugd belong to the default full installation of Slackware and therefore assume, there must be a solution which meets my requirements without even one of both programs.The laptop is only used at home. Wireless connection is normaly used. I need eth0 only in a case of emergency.
In an attempt to set up wireless so I could connect to the university network, which I think I probably should have just downloaded network manager or something but I didn't, I tried to put things in /etc/conf.d/net and some other places and I am afraid I'm not sure exactly what (and I have learned my lesson! I will pay attention to what I am doing so I can undo it next time I mess around with stuff!)
Anyway, the long and the short of it is now, when the computer is starting up and its doing the init stuff net.lo doesn't start. Later try and start net.lo or net.eth0 you get told "not enough arguments"
Installed a TP-Link TG-3269 Gigabit card in a machine running OS 11.3 32 bit, when I go into Yast, Network Devices, Network to try configuring the card I get this errormsg: Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details. Couldn't find any mention of the card in dmesg's output, (though the 8139 onboard card is in there) there is some stuff about pci host bridge but I don't know whether they would be relevant or not
The chip on the card says it's rtl8169sc but lspci lists it as being 00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8369 (rev 10) Done some googling and there don't seem be any drivers for a Realtek 8639 and it returns no matches from a search on realtek's site, but there is a driver there for rtl8169sc chips, which I downloaded and installed, no errors when installing it Even after a reboot I still get the same error in Yast's Network Settings screen, lspci still lists it as 8369 and the device isn't listed at all if I run ifconfig
Quick question guys and gals: How do I get "wlan0" and "eth0" interfaces to start at startup as as well as for "dhclient" to obtain an IP address automatically for "eth0?"
I just switched from Fedora 13 to openSUSE 11.3 on my laptop and so far love it...well...not quite. I'm having some major network issues. As in...no networks.
I installed everything and booted up for the first time. Everything worked great, I had wireless through wlan0 and could connect directly to my home router via eth0 with no problems. Installed a few applications and ran into some problems with hibernating/suspend modes. I rebooted and like magic, NetworkManager said networking was diabled. My WiFi light was off. Network switch on the computer didn't do anything.
I thought alright, I'll connect my ethernet cord and can go from there....problem is that won't work either. I tried searching for drivers online on my desktop, found some and transferred them via USB with no luck. They won't install. I have no idea why, or whats going on but I really need my laptop for school on Monday so it would be AWESOME to have it working by then.
Here is what I have: Intel 5150 WiFi card Dell Studio XPS M1640 laptop OpenSUSE 11.3
On a new Dell Lattitude e6400, I have installed both arch and Ubuntu. Ubuntu recognized wifi and ethernet right away and connected and is working fine, but in arch, I am having more problems then I usually do when using arch. From the output of lspci the ethernet is a intel device 1502, I have researched this and found it to need the e1000e module as its driver. I modprobed this module sucessfully, but no ethernet. With wlan, i have found that the card is a DW1501 Wireless-N WLAN Half-Mini Card that has a broadcom 4727 chip in it. I downloaded the windows driver for this chip and isntalled it with ndiswrapper but this did not help. What I think is the root of the problem is the error message that restarting networking creates.
Quote:
Dell only supplies drivers for ubuntu, but it should still be possible to get this to work. I have tried booting various live distros that I had drives for and I found that the parted magic boot disk saw the ethernet port and was able to connect to ethernet, and that the ubuntu live disk was able to connect to both wifi and ethernet. Somehow they must be seeing the prescense of the hardware in a way that I have not tried with arch. Please help, I really need to get this computer workign with arch.
Is there a way to get conky to show only eth0 or wlan0? My configuration only shows the wireless bit when wifi is switched on but shows eth0 all the time.
Temperature: I have nvidia card with drivers from rpm fusion, can conky give me the temperature of the card and the cpu?
I have a wired connection going to my router, which is encrypted with WPA2-PSK. That works fine. I hooked up a WUSB54G v4 (Linksys USB Wireless Adapter), and used ndiswrapper to install the drivers from Vista to make it compatible with WPA2. Also configured the /etc/network/interfaces with the wpasupplicant lingo to make it all work. So if I do that, my eth0 will not work anymore. Also on a side note my network manager stops with displaying in the top panel. Not a problem I can run /etc/init.d/networking (re)start and dhclient eth0 (wlan0) and all the other commands that are necessary to make it work.
Back to the problem, so I hook up wlan0 with the settings and eth0 stops working. I want to use the wlan0 solely for the purpose of my media server. The eth0 is there for my internet and that is it .
I'm running Ubuntu Server 10.10 on a 64 bit laptop (also have GNOME installed just for convenience), and have a website up using apache2. I am wondering if it is possible to configure both eth0 and wlan0 to the same local static IP address? I would like to walk around my house and do stuff when I want and still have the website accessible, but also be able to jack my laptop back into the router when I am away, just for peace of mind.
Is this possible? If it is, do I need to do some configuring in apache2 to tell it to use another device? Is this even a smart way to get what I want done?
I'm running Linux Mint 10 . I have a wireless PCMCIA card (Linksys WPC 11 ver.3) that I've put into master mode, and I'm trying to set up my laptop as a wireless hotspot. I am very confident that I want to do this and have no interest in using a wireless router....I say that because that topic inevitably comes up with posts like this. The problem I'm having is I don't understand how to get wlan0 and eth0 to "talk" to each other...That is, I don't know how to set it up so that traffic from wlan0 goes through eth0, so that devices that connect to my hotspot can access the internet.I've seen a few guides about this, but they were either much broader in scope (i.e. much more complex), or for other distributions, etc, and it's too much for me to follow as a linux .
I would like to pose is very specific to a system I'm assembling. I have ask for assistance from other forums and people, however the answers receive were too vague to implement.
As for my background, I am a network user able to write TCP Linux client/server applications quite easily. At a Linux system level I do not understand the necessary combination of applications and services to affect the following;
Network components;
- WiFi access point/router with four ethernet ports
- Laptop (user computer) cabled directly into the access point via a physical cable
- Second computer running Ubuntu 10.04, with one WiFi (wlan0) and one ethernet (eth0) interface. Eth0 is configured as a DHCP server with the following;
IPaddress 192.168.252.1 broadcast 255.255.255.0
Eth0 is physically connected to an IP camera via a Cross-over cable. The camera is configured as a DHCP client. This connection works perfectly from the Linux box with a KVM attached.
Wlan0 is connected wirelessly to the access point and the Laptop can access the Linux box and vice versa.
My objective is to have the
- Laptop via the access point/router connect directly to the IP camera on the Linux box via the wireless link.
- I would prefer not to make any configuration or routing changes/entries on the access point/router.
The type of response I'm looking for;
- is this possible at a macro level
- what facilities/server are required on the Linux box (I would like all configuration applied to this computer only)
- what commands need to be executed and in what order. If possible a brief explanation of why the command is needed and where it fits in the grand scheme of the solution.
This is probably a gigantic request outside what the forum usual activity.
now my system does not connects automatically when fedora start's to eth0 i have to connect it manually by pull down menu in the beginning hostnname was dbe272b22.dslam-172-17-161-245-0532-474.dsl.cantv.net i do not remember if the last part ".cantv.net" was there.... i changed hostname "dbe272b22.dslam-172-17-161-245-0532-474.dsl" maybe ending with ".cantv.net" with system-config-network for hostname "edicta" i modified /etc/hosts by hand twice, now do not remember what i did exacly but here you can see /etc/hosts
I am very new to linux.I have a network camera which only has an Ethernet port but no WiFi. Sadly no Ethernet port is available close to the camera.
Therefore I now bought a raspberry pi and installed raspbian to create a bridge into the wireless network, for connecting the camera to the internet.I now played around with the interface- and bridge configuration but I have problems with it.This is how my interfaces file looks like:
(The WiFi is secured with WPA2 Enterprise)
Code: Select all# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d
[code]....
The WiFi is connection works fine and I am in the internet using the WiFi.But I am wondering about eth0. The network parameters I specified are not the same as the parameters ifconfig tells me.Ip, Broadcast, Mask, nothing is as specified.It would be nice to give the camera a static IP that I can access it always with the same IP from the RaspberryPi.The Raspberry Pi itself gets always a new IP from the WiFi network. How do I get the camera into the internet using the existing connection of the Pi?
client <--> wlan0 <--> computer <--> eth0 <--> internet
i have 2 network connections eth0 wired connected to internet wlan0 wireless (work fine) i have installed hostapd with madwifi and so on oki when i run hostapd the clients see the hot spot oki clients connect with wpa oki network manager run at demand not automatic (keep it for internet help) now i'm a bit lost what do i need is wlan0 give the client an ip (dhcp demand) create a bridge between wlan0 and eth0 steps to create a permanent bridge between wlan0 and eth0
currently on an acer aspire 5532, and using mozilla and google chrome. webpages take about 10-12 seconds to load using the ethernet, wifi its about 2-3 seconds. using eth0 loading videos - broadcast yourself. in chrome, will sit at "resolving host" for about 10 seconds before bringing up the page. you would think eth0 is faster than wlan0, but for browsing the web its slower. i tested the speeds at speedtest.net - the global broadband speed test and both wlan0 and eth0 get the max speed my internet provides.i never downloaded drivers for the ethernet card or wifi, they worked so i didn't try to mess with them. but perhaps that is my problem?
I have installed Open SUSE in my DELL server which has 2 broadcom NIC cards, it showing both the NIC cards in Network configuration in YAST ,but it showing as not configured and not connected . Kernel device eth0,wlan0 are not present. In device manager also 2 Broadcom nic cards are detected.
I just installed Fedora 13 on a new Dell XPS desktop and some of the networking files are not created/missing. The computer has Broadcom Gigabit wired card and Asus PCE-N13 wireless card. When I type lspci, I see that Network conroller: RaLink RT2860 and Ethernet controller: Broadcom BCM57780 Gigabit Ethernet. So, somehow they are being detected by the OS, but I am not sure if the drivers are installed or why some of the network files are missng.
I've had 11.4/KDE working pretty well on dual boot Asus G73SW for a few weeks now. Only issues were the FN-* functions that control keyboard lights and whatnot but no biggie since the essential worked.The last couple of days the update notification was indicating 1,201 updates to be made. Yeah it seemed extreme but I googled around and checked the forums and there was nothing related. I figured I might be missing some packages since I installed from the live KDE CD (still 1202 updates!!!???). So I updated. Big mistake!!!!! Ever since NetworkManager cannot connect to the internet, be it wired or wireless.
Initially it could not even see my home network but it picked it up after I removed the plasmoid from the panel and reinstalled it. However it doesn't respond when I click the network icon and still no connection.I managed to get eth0 working with ifup but not wifi. The last part of network manager log file is quoted below. I can send the whole thing to whoever is interested. I can't make sense of it but maybe someone on the forums can.
i can't get a pppoe conection working over a wireless network,in windows I have to connect to the router first, and then put in my user and password to get connected, but i don't know how to do this on fedora, i get connected to the router through network manager, and ping is ok, but when i try to make a new xDSL connection i don't know how to make it work through the wireless network that is established and working with my router.
I'm new to this forum site and I was wondering how can I bridge a network between the eth0 and wlan0 connections?my eth0 NIC is a RealTek RTL8111B 10/100/1000 Ethernet Card (OnBoard) and my wlan0 NIC is a RealTek RTL8187B 802.11b/g WiFi USB Adapter Card.Are there any utilities, such as bridge-utils that I can use, except for Firestarter since Firestarter states that the eth0 connection is not established, or do I right-click on the network icon and select Edit Connections and go to Auto eth0 and under the IPv4 Address setting and select Shared to other computers and run a live connection there?The main reason is that I need an Internet connection for my Xbox 360, which is connected to my Linksys WRT54G 802.11b/g Wireless Router, that has DD-WRT firmware installed and 4 WiFi hotspots for any wireless device, such as my PSP, DS, DS Lite, Wii, Laptop(s), my brother's PC (needs a WiFi card), and my dad's PC (needs either a WiFi card or an Internet connection from my brother's computer to my dad's PC)
Here are my Computer Specs: ECS nForce6m-a Motherboard 2GB DDR-800 PC6400 Memory
I am using slackware64-current and this morning I have updated my system with using slackpkg. (As you know, huge changes has been applied on the current branch. Kernel, glibc and etc..) Everything went flawness and seems OK. I did not see any error message or somethink like this. After the update, kde does not start. Problem is, after KDM login, nothing happens and turn back to KDM login screen.
To understand what is going on, I switched to init 3 and performed "startx" command. Result is same but I saw some dbus error.
Then I checked whether hald and dbus does run or not and I saw it is running without problem.
Lastly I have removed dbus and hald packages and reinstalled but problem is still running.
I did a clean install, and so far I haven't noticed any serious problems with KDE4, although I can't find what I'm looking for, usually. I don't use my laptop much though. I also did a clean install on another system to 13.0 about the same time. X won't start on that system, it can't figure out the hardware I guess.
So I've just been using the command line. I don't really need a graphical interface on that system anyway. Right now I'm using the motherboard graphics support, but I will probably install a video card in a PCI-E slot and try X again. The system that I just upgraded from 12.2 (LUKS encrypted volumes and LVM) to 13.0 tonight has a number of problems. This was an upgrade, not a clean install. Based on my experience so far on this system, KDE4 does not seem to be ready for prime time. It is buggy, the menu system is more difficult to navigate than KDE3, and there are some apps I just can't find (e.g., Kedit). Overall it seems to have fewer apps than KDE3. Either that or they are well hidden well enough that I can't find them. My first impression was that KDE4 had clean lines and a modern appearance.......
I've been able to get a laptop on Fedora 14 (2.6.35.6-48) working with a Netgear WNA1100 Once up and running, I execute "ifconfig wlan0 up" from root, and everything connects just fine and is stable as long as I stay logged in. But, I haven't found how to do this automatically on boot.
I've tried to use NetworkManager, but I cannot figure out how to get the GUI to show up - it says its running and enabled in the Services gui, but I haven't figured out how to actually use it! I checked to see if the nm-applet is running with ps, and for the user login, I see:
I'm not sure if the "sm-disable" flag is my problem, or how to change it. I'm not even sure if NetworkManager will allow me to set things up for bootup, but that is the path I ran down...
I assume this is a fundamentally easy process to set this up on bootup, but I'm not stumbling across the method. I recall doing this kind of thing years ago when I was an engineer, and before I got my lobotomy to become a manager...
my Conky needed the Coretemp, and a friend of LQ told me to run modprobe, and it works greate! no every time I start my system, I need to run the modprobe to add the module to Kernel. How can I put the coretemp to start every startup? (I think there is somenthing to do with a file on the rc.module at /etc/rc.d/, but I'm afraid to do something stupid...) I want to make the conky running after start of the system. How can I do this?
I have Slackware 13.1 x64 and my graphic card is ATI Radeon HD 2400 on my laptop. I install from ATI official site driver for this card and now when I try to come in System Settings->Desktop I got this error:
2nd and 3rd might be linux kernel problems but may help someone else so I included here.1st -- run level 4, /etc/rc.d/rc.4 and xdm -nodaemonJust installed 13.1 on an odd system, including building a new kernel.One thing I do is have the system boot to a command prompt and then run /etc/rc.d/rc.4 to start XBut I found that the rc.4 uses xdm -nodaemon flag and it was causing problems so I removed and all is pretty good. I still see some odd behavior with the virtual ttys sometimes.2nd -- when building a new kernel, I found I need the device-mapper butcouldn't tell if that was a linux kernel issue or something to do with lilo, I didn't want and don't need multiple disk devices like for LVM or MD so I didn't plan to have this enabled.3rd -- CONFIG_EXT4_USE_FOR_EXT23 When that kernel config option was selected and I have only an EXT4 filesystem, the filesystem was mounted as an EXT2, even though the kernel had no EXT2 feature. /etc/fstab specified EXT4 but the mount command showed EXT2. A silent problem that could leave an unpleasant surprise since EXT2 hos no journaling.4th -- I had to run lilo -C by hand in a virtual tty before finishing the install. This was what I had to do when installing 13.0 on different hardware. It seems that the lilo part of the install needs some sorting out.
