Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
I think this probably needs to be an FAQ. This sounds like the same problem I had initially, which was that I was getting connected to the AP and getting an address via DHCP, but not getting a default route for the wireless interface (eth1). Here's the catch: when dhcpcd starts up for multiple interfaces, it only accepts a default route on the <b>first</b> interface. Once I changed the wired (eth0) interface to come up manually instead of "onboot", the wireless worked fine.
Bring up YaST, go to "Network Devices", "Network Card". Select your wired card. Under the "advanced" settings, there's a dropdown menu for "Device Activation". It's probably set to "At Boot Time". Change it to "manually".
ERROR: command 'iwconfig' eth1 mode 'manged' returned
error for wireless request "set mode" (8B06):
set failed on device eth1; operation not supported.
eth1 (DHCP) ..... ip net mask: 192.168.103 / 255.255.255.0
I got this message with all 3 modes...what's wrong with this?
That's odd. But it looks like you're getting an address from DHCP, even with the error. Can you paste in the output from "ifconfig eth1", "iwconfig eth1", and "netstat -nr"?
when i typed first 2 on x-terminal...it says bash: ifconfig: command not found, and iwconfig: command not found. maybe I didn't installed some packages??
but netstat -nr
kernel ip routhing table
destination gateway genmask flags msswindow irtt iface
192.168.1.0 0.0.0.0 255.255.255.0 u 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 u 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 u 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 ug 0 0 0 eth1
They're in /sbin and /usr/sbin, you probably don't have those in your path. That looks like a good routing table, though. What happens when you try to ping something like, say, www.novell.com?
OK, how about if you try to ping them by IP (130.57.4.27)? Sounds like you may not be gettng a name server, which could be a configuration issue with your AP.
ping 130.57.4.27 (130.57.4.27) 56(84) byes of data.
64bytes from 130.57.4.27: icmp_sq1 ttl =52 time70.3 ms
64bytes from 130.57.4.27: icmp_sq2 ttl =52 time69.0 ms
64bytes from 130.57.4.27: icmp_sq3 ttl =52 time73.6 ms
--- 130.57.4.27 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 69.097/71.034/73.646/1.929 ms
It means that you'r e not getting a DNS server address from your DHCP host. I don't know how your network is set up, but typically either
a) you have an all-in-one router/AP/firewall dingus, or
b) you have a router/firewall box and a separate WAP.
In either case, you typically have to tell whichever box is providing DNS for you to hand out a DNS server address. Usually the address is the router or WAP itself, and it just proxies DNS queries out to another system. But your Linux system seems to be doing everything it should be.
Sorry, I'm pretty much out of suggestions at hit point. Without knowing what your DHCP host is, I couldn't even venture a guess. The only useful suggestion I could give you at this point is to look at the documentation for your DHCP device and see if it says anything useful. Oh, one other thing you could do as a workaround for the moment: put the address of your DHCP device (which is almost certainly proxying DNS) directly into /etc/resolv.conf (man resolv.conf will tell you the format of the file). Good luck!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.