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 guess it is time to step back and start over? all the information that i have given you is all that i know as far as the router, IP address etc.
I have used the commands that you requested, sometimes spelling was a problem, but it just is not working, it is getting worse. I am going to try to reinstall the Ubuntu once again to see if it corrects its self.
LN;
I asked you several times for complete answers, I asked for specific tests, and I asked for a summary in which you address ALL of the suggestions and questions to date.
I do not understand why you do not want to do the tests I requested--and why you will not respond to several specific questions. But, that is your choice.
Your best bet at this point might be to find a local expert to sit with you and work through this---I would start with a local Linux user group.
The way I read the problem, re-installing Ubuntu is not going to help.
I guess it is time to step back and start over? all the information that i have given you is all that i know as far as the router, IP address etc.
I have used the commands that you requested, sometimes spelling was a problem, but it just is not working, it is getting worse. I am going to try to reinstall the Ubuntu once again to see if it corrects its self.
thanks for the time and hope to connect soon.
I've stayed out of this since my first post to this thread. I think you need to concentrate on getting one connection.
You could use the 'The Broadcom Firmware (tar.gz)' file from the above sight. Once you have the proper firmware installed then the operation will fall into place without to much effort.
I've got a 'BCM4312' which required me to jump through hoops. I went with the 'STA' drivers & patches but found the driver/firmware to be a problem at times. I tried to revert to older firmware but could not get the right one. BY chance I found this older driver that will work with my version of the 'BCM4312'. Sure, you will get warning error at boot that the driver maybe to old but it will work. The switching of the device to the 'eth1' device has caused me some reliability and recognition problems. If you use the referred driver then the 'wlan0' device will be recognized.
BTW, to reinstall your OS may/maynot remedy the problem. As I said earlier, break the problem down to working on ONE issue at a time.
I guess it is time to step back and start over? all the information that i have given you is all that i know as far as the router, IP address etc.
I have used the commands that you requested, sometimes spelling was a problem, but it just is not working, it is getting worse. I am going to try to reinstall the Ubuntu once again to see if it corrects its self.
thanks for the time and hope to connect soon.
Those were 2 tests. You should have done 1 test, test the pages I indicated and THEN do the second test. I'm trying to get information from your environment. I don't know the ip address of your router and I was trying to guess it was either 192.168.0.1 OR 192.168.0.2. I still don't know because you mixed up the two tests. Please do them in order and report what you find step after step. Indeed, it is not ideal to work like that, it would be best if you could provide information from windows, like asked by pixellany. But from what I understand, your Windows machine is connected to the internet by a wire and we don't know if it is connected to the same router you are trying to connect to with your Ubuntu machine. Reinstalling Ubuntu won't help I'm afraid. You still need a way to talk to a router you know nothing about. With luck we can find how to connect to it, but it would be best if you could ask the router administrator to assign an ip address to you or to activate the DHCP server on that router.
At that time, there was a DHCP offered by machine 192.168.0.1 (as you can see in the post you linked to).
But as you can see in post #52, we don't have any DHCP server responding on eth1 (connected on the linksys via wifi) anymore. I suspect there was another machine connected to the router that had a DHCP server and now this machine is off. I suspect the router doesn't offer DHCP. It looks like the router is on network 192.168.0/24 because the machines that acted as DHCP server were 192.168.0.1 and later 192.168.0.2. He pinged both machine in post #30. I don't know the ip address of the router, maybe it is one of those two machines?
We don't have DHCP anymore, so we have to guess the correct ip to set the machine to and the ip of the router to connect to. I don't know how this network is set up, but there are several machines, or the router administrator likes to change the settings without notice.
LN Smith needs to find a machine that is connected to that linksys or an administrator and tell us what is the ip address of the router, or we can use nmap and try every single machine until we find the router. I think his patience is running low though, so the last option will be difficult, especially since he doesn't like the command line much. He doesn't seem to be able to tell us which machines are connected to the router and he doesn't seem to have any contact with any administrator either. I don't know what is the best plan from there. What do you think?
^ are we sure the route command didnt mess with their ability to dhcp (admittedly, i dont know much about the route command).
i think they mentioned that their ipod works on the network. is it possible to see what the network parameters are on the ipod - i dont have one so i dont know how to get to that menu.
Ok not giving up just yet! this is what i know so far: This problem with the wireless connection and the Ubuntu system started when i got disconnected, a wireless connection, during a download upgrade, after I was first connected to the internet. I have been trying to install everything from a USB stick back onto the Mini sense then. Everything is working fine except for the internet connection and the NetworkManager, all other information seams to be fine.
the wireless drivers to my knolege are installed and working. they were BCM4312 and i am now using STA drivers. the iwconfig is:
Quote:
smith@smith-laptop:~$ sudo iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thrff Fragment thrff
Power Managementmode:All packets received
Link Quality=5/5 Signal level=-57 dBm Noise level=-57 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
smith@smith-laptop:~$
The active linksys card that i am trying to connect to is Cell 01 it is at my work place:
smith@smith-laptop:~$ sudo iwconfig eth1 essid "linksys_OW_45452"
smith@smith-laptop:~$ sudo dhclient
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/pan0/5a:9d:c3:f9:24:64
Sending on LPF/pan0/5a:9d:c3:f9:24:64
Listening on LPF/eth1/00:25:56:66:4c:0d
Sending on LPF/eth1/00:25:56:66:4c:0d
Listening on LPF/eth0/00:25:b3:46:f1:88
Sending on LPF/eth0/00:25:b3:46:f1:88
Sending on Socket/fallback
DHCPREQUEST of 192.168.0.51 on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPREQUEST of 192.168.0.51 on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
smith@smith-laptop:~$
When trying to connect using the wireless connection all the settings are set to automatic. that is what they were set at when i got connected the first time.
when i tried to connect with the LAN connection on our network this is what the settings were set at, and i did not turn on my desktop to run at the same time.:
IP address 10.1.1.60
SubnetMask 255.255.255.0
Default Gateway 10.1.1.254
DNS 10.1.1.100
10.1.1.101
Metric Automatic.
Again I would like to thank all of you for your Help and support.
hi ln, i share you frustration...
if i understand you correctly your wired lan gives ip's like 10.1.1.x
but your wireless lan gives ip's like 192.168.1.x
so either the router uses class a hierarchy for wired and class c for wireless (i dont know if that is possible).
or your workplace has 2 different routers (1 for wired/ 1 for wireless).
or it is possible that the dhclient program is screwed up because it is no longer getting an ip address from your router (you were before - maybe in the last 2 days someone changed it so that people have to be set up by an admin for security reasons -- does your ipod still work on that network ?).
this is starting to get wierd.
maybe tethering your fone would help you get internet access (but i dont know how to do that).
You have the kind of positive attitude I like.
Maybe your desktop is using some kind of vpn virtual interface? Do you have any device that can connect to your wireless router currently?
Do you know how many machines are connected to the router? Maybe the maximum has been reached and he does not accept any other host?
I don't expect it to work, but could you please try to connect like that:
Code:
sudo iwconfig eth1 ap 00:18:39:72:9C:23
sudo dhclient eth1
(please post the output of the commands)
then post the output of
Yes all i was given by the IP person was to use the setting :
IP address 10.1.1.(and any range 60 to 69 hear)
Subnet Mask 255.255.255.0
DNS 10.1.1.254
and then they said i would be connected! there are Two people hear today with Ipod's that aru using the router and they are connected just fine.
using this code I get:
Quote:
smith@smith-laptop:~$ sudo iwconfig eth1 ap 00:18:39:72:9C:23
[sudo] password for smith:
Error for wireless request "Set AP Address" (8B14) :
SET failed on device eth1 ; Invalid argument.
smith@smith-laptop:~$ sudo iwconfig eth1 ap 00:18:39:72:9C:23
Error for wireless request "Set AP Address" (8B14) :
SET failed on device eth1 ; Invalid argument.
smith@smith-laptop:~$ sudo iwconfig eth1 ap 00:18:39:72:9c:23
Error for wireless request "Set AP Address" (8B14) :
SET failed on device eth1 ; Invalid argument.
smith@smith-laptop:~$ sudo dhclient eth1
There is already a pid file /var/run/dhclient.pid with pid 3073
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:25:56:66:4c:0d
Sending on LPF/eth1/00:25:56:66:4c:0d
Sending on Socket/fallback
DHCPREQUEST of 192.168.0.51 on eth1 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.0.51 on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
Trying recorded lease 192.168.0.51
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.