[Ubuntu] Access Point Connection
Solved
Yoan
Posted messages
11905
Status
Moderator
-
maxime -
maxime -
Hello,
I would like to connect to a Wifi access point (Livebox Inventel) with Ubuntu 5.10. No need to explain that I'm struggling :(....
I came across this:
http://www.bloggure.info/index.php?2005/12/23/534--tuto-wi-fi-dongle-livebox-sagem-et-linux-ubuntu
And in this case, I'm not using the Inventel adapter but a Hercules network card (well recognized by buntu). So, I'm in the process of discovering the operating system and I'm struggling a bit, thank you :D.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
I would like to connect to a Wifi access point (Livebox Inventel) with Ubuntu 5.10. No need to explain that I'm struggling :(....
I came across this:
http://www.bloggure.info/index.php?2005/12/23/534--tuto-wi-fi-dongle-livebox-sagem-et-linux-ubuntu
And in this case, I'm not using the Inventel adapter but a Hercules network card (well recognized by buntu). So, I'm in the process of discovering the operating system and I'm struggling a bit, thank you :D.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
30 answers
- 1
- 2
Next
Hello,
Go instead to the dedicated site (frenchy): http://www.ubuntu-fr.org/
and more specifically here: http://doc.ubuntu-fr.org/installation/wifi
--
See you...cheers and Happy New Year 2006.
Go instead to the dedicated site (frenchy): http://www.ubuntu-fr.org/
and more specifically here: http://doc.ubuntu-fr.org/installation/wifi
--
See you...cheers and Happy New Year 2006.
JP: Zen, my Nuggets! ;-) Knowledge is only good if it is shared.
Doesn't work :(((
The WiFi card's diode doesn't light up, I suppose I need the drivers? They are not available for Linux....
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
The WiFi card's diode doesn't light up, I suppose I need the drivers? They are not available for Linux....
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
Well, I sent an email to Hercules, the adapter is supposedly "based on the Ralink RT2570 chipsets from the RT2500 family." So I went to download this:
http://www.ralinktech.com/supp-1.htm
Now:
1-Ubuntu is not on the list (neither is Debian).
2- I don't know how to install this :-). Once unzipped, what do we do with it? I'm familiar with rpm, but this is something else entirely....
Thank you.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
http://www.ralinktech.com/supp-1.htm
Now:
1-Ubuntu is not on the list (neither is Debian).
2- I don't know how to install this :-). Once unzipped, what do we do with it? I'm familiar with rpm, but this is something else entirely....
Thank you.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
Well, I'm making progress on my own, but 'up' again ;-)
The drivers are installed and the hardware is recognized correctly. The blue LED indicating that the card is powered on is still not lit, even though it is under Windows. And I obviously can't connect to the access point...
Is there a utility that works with all adapters to connect easily?
Thank you.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
The drivers are installed and the hardware is recognized correctly. The blue LED indicating that the card is powered on is still not lit, even though it is under Windows. And I obviously can't connect to the access point...
Is there a utility that works with all adapters to connect easily?
Thank you.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
Hello,
Do you really want to use Wifi? Because the Livebox can also connect via Ethernet, provided you have a network card (which can be integrated into the motherboard). With Ethernet, the setup is very simple since it doesn’t require any drivers, and you need to use the IP address 168.192.1.1 for the Livebox modem-router.
I wrote a tutorial for installing the Livebox via Ethernet on several Linux distributions. It is intended to be published in the Linux+ DVD magazine, but I will try to summarize it to make a FAQ.
If anyone is already interested, just give a shout ;-)))
--
Toco y se gausos !!!
Do you really want to use Wifi? Because the Livebox can also connect via Ethernet, provided you have a network card (which can be integrated into the motherboard). With Ethernet, the setup is very simple since it doesn’t require any drivers, and you need to use the IP address 168.192.1.1 for the Livebox modem-router.
I wrote a tutorial for installing the Livebox via Ethernet on several Linux distributions. It is intended to be published in the Linux+ DVD magazine, but I will try to summarize it to make a FAQ.
If anyone is already interested, just give a shout ;-)))
--
Toco y se gausos !!!
Thank you, that's nice :-)
Are you really keen on using the Wifi?
Well, yeah, the box is one floor below. At that point, either I run cables to add a second phone socket or I set up an RJ45 installation. That's why I liked the Wifi ;)
Besides, I don't understand, the drivers are installed and all that, the card is recognized, activated, my network is set up (SSID, WEP...). But it just doesn't work :((. The card doesn't light up.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
Are you really keen on using the Wifi?
Well, yeah, the box is one floor below. At that point, either I run cables to add a second phone socket or I set up an RJ45 installation. That's why I liked the Wifi ;)
Besides, I don't understand, the drivers are installed and all that, the card is recognized, activated, my network is set up (SSID, WEP...). But it just doesn't work :((. The card doesn't light up.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
The start of the solution:
http://www.commentcamarche.net/forum/affich-1969822-Ndiswrapper-et-Livebox
I'm warning you, wifi is very tricky (see the end of the post above).
The basic plan:
1- grab the drivers from the Livebox CD
2- decompress them
3- install your source kernels
4- install ndiswrapper, along with some useful tools (usb tools...)
5- fix the faulty .inf
6- ndiswrapper the Windows drivers
7- insert the ndiswrapper module (modprobe ndiswrapper)
8- check that everything is okay:
I had to fix a part in the kernel sources
9- create the alias wlan0 (ndiswrapper -m)
10- configure the setup (iwconfig), essid, wep key... An installation of kwifimanager may help you. Personally, I'm at this stage.
11- automate the startup (script available on the lea linux site)
Another avenue that may help you since Debian and Ubuntu are related:
http://bwp-necromance.developpez.com/tutoriel/LiveBoxSagemDebianWifi/
Good luck
http://www.commentcamarche.net/forum/affich-1969822-Ndiswrapper-et-Livebox
I'm warning you, wifi is very tricky (see the end of the post above).
The basic plan:
1- grab the drivers from the Livebox CD
2- decompress them
3- install your source kernels
4- install ndiswrapper, along with some useful tools (usb tools...)
5- fix the faulty .inf
6- ndiswrapper the Windows drivers
7- insert the ndiswrapper module (modprobe ndiswrapper)
8- check that everything is okay:
lsusb ndiswrapper -l dmesg | tail lsmod | grep ndiswrapper
I had to fix a part in the kernel sources
9- create the alias wlan0 (ndiswrapper -m)
10- configure the setup (iwconfig), essid, wep key... An installation of kwifimanager may help you. Personally, I'm at this stage.
11- automate the startup (script available on the lea linux site)
Another avenue that may help you since Debian and Ubuntu are related:
http://bwp-necromance.developpez.com/tutoriel/LiveBoxSagemDebianWifi/
Good luck
I emailed Hercules again, their response:
Hercules does not currently offer technical support for any version of Linux.
However, what I can recommend is to check if your modem needs to be set to association mode. Also, check if the MAC address filtering function of your modem is enabled. In this case, you will need to either disable it or manually add the MAC address of your wireless device.
It doesn't provide me with much. Maybe the filtering, but I doubt it a lot since the card worked under Windows :(
--
The urgent is done, the impossible is in progress,
For miracles, please allow for a delay ...
Hercules does not currently offer technical support for any version of Linux.
However, what I can recommend is to check if your modem needs to be set to association mode. Also, check if the MAC address filtering function of your modem is enabled. In this case, you will need to either disable it or manually add the MAC address of your wireless device.
It doesn't provide me with much. Maybe the filtering, but I doubt it a lot since the card worked under Windows :(
--
The urgent is done, the impossible is in progress,
For miracles, please allow for a delay ...
IF your card is recognized, you should have an ethX or wlanX associated with it by typing /sbin/ifconfig.
Then you just need to configure the WEP key, the ESSID, whether it's a static IP or obtained via DHCP, etc. All of this is set up with ifconfig and iwconfig and is automated, in principle, in /etc/network/interfaces. For the WEP key, make sure to correctly paste the numbers and letters corresponding to the key in hexadecimal.
In the meantime, give us the results of:
Good luck
Then you just need to configure the WEP key, the ESSID, whether it's a static IP or obtained via DHCP, etc. All of this is set up with ifconfig and iwconfig and is automated, in principle, in /etc/network/interfaces. For the WEP key, make sure to correctly paste the numbers and letters corresponding to the key in hexadecimal.
In the meantime, give us the results of:
/sbin/ifconfig /sbin/iwconfig cat /etc/resolv.conf
Good luck
/sbin/ifconfig
lo --> Loopback adapter, I don't think it's useful.
ra0 --> Ethernet HWaddr 00:08:D3:05:13:D3
addr inet6: fe80::208:d3ff:fe05:13d/64 scope: link
MTU: 1500 Metric: 1
Packets received: 0
Packets transmitted: 8404 (430kb)
Interrupt: 5 Base address: 0X4000
/sbin/iwconfig
Everything seems fine here, I think, correct ESSID. Mode: Managed
RTS thr OFF. Fragment thr OFF
11Mbps. No packets received.
cat /etc/resolv.conf
nameserver 192.168.1.1
‘It seems to me that this matches quite well, doesn’t it?
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
lo --> Loopback adapter, I don't think it's useful.
ra0 --> Ethernet HWaddr 00:08:D3:05:13:D3
addr inet6: fe80::208:d3ff:fe05:13d/64 scope: link
MTU: 1500 Metric: 1
Packets received: 0
Packets transmitted: 8404 (430kb)
Interrupt: 5 Base address: 0X4000
/sbin/iwconfig
Everything seems fine here, I think, correct ESSID. Mode: Managed
RTS thr OFF. Fragment thr OFF
11Mbps. No packets received.
cat /etc/resolv.conf
nameserver 192.168.1.1
‘It seems to me that this matches quite well, doesn’t it?
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
Ok, here it is :-)
ifconfig
lo Link encap: Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:49100 errors:0 dropped:0 overruns:0 frame:0
TX packets:49100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3543786 (3.3Mb) TX bytes:3543786 (3.3Mb)
Interrupt:5 Base address:0x4000
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
ra0 RT2500 Wireless ESSID:"WANADOO-5703"
Mode:managed Frequency:2.412GHz Bit rate:11Mbps
Rx invalid nwid:0 Rx invalid crypt:0 Missed beacon:0
sit0 no wireless extensions.
It's curious, there are as many received packets as sent ones now, even though I haven't done anything at all..... :)
Thank you.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
ifconfig
lo Link encap: Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:49100 errors:0 dropped:0 overruns:0 frame:0
TX packets:49100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3543786 (3.3Mb) TX bytes:3543786 (3.3Mb)
Interrupt:5 Base address:0x4000
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
ra0 RT2500 Wireless ESSID:"WANADOO-5703"
Mode:managed Frequency:2.412GHz Bit rate:11Mbps
Rx invalid nwid:0 Rx invalid crypt:0 Missed beacon:0
sit0 no wireless extensions.
It's curious, there are as many received packets as sent ones now, even though I haven't done anything at all..... :)
Thank you.
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
Your wifi card is ra0 but it does not appear in your ifconfig. Normally you are supposed to configure it in /etc/network/interfaces or something like that, so that later you can run an ifup.
If for example your router is using DHCP (i.e., it automatically assigns an IP):
Be careful not to make a mistake with the case of the essid and not to forget the " ". However, no quotes, no '-', or ':' for the WEP key if you have one. Also check that the keywords are exactly as under Debian by typing in a console:
Having done this, type in a root console:
Normally your card should correctly appear by typing:
You then need to check the routes and DNS but theoretically, if the router is using DHCP, everything is already ready. To check, type:
If it doesn’t work, give me the output of each of these commands.
If it works, it means your /etc/network/interfaces file is correct and afterward, you can simply run in a root console:
There is a possibility to activate it at startup (keywords auto and hotplug I believe, I will leave you to search)
Good luck
If for example your router is using DHCP (i.e., it automatically assigns an IP):
iface ra0 dhcp wireless-essid "WANADOO-5703" wireless-key xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Be careful not to make a mistake with the case of the essid and not to forget the " ". However, no quotes, no '-', or ':' for the WEP key if you have one. Also check that the keywords are exactly as under Debian by typing in a console:
man wireless
Having done this, type in a root console:
ifconfig ra0 up
Normally your card should correctly appear by typing:
ifconfig
You then need to check the routes and DNS but theoretically, if the router is using DHCP, everything is already ready. To check, type:
cat /etc/resolv.conf /sbin/route -n
If it doesn’t work, give me the output of each of these commands.
If it works, it means your /etc/network/interfaces file is correct and afterward, you can simply run in a root console:
ifup ra0
There is a possibility to activate it at startup (keywords auto and hotplug I believe, I will leave you to search)
Good luck
man wireless
It gave me the "Linux Programmer's Manual", I didn't understand everything :/
ifconfig ra0 up
Nothing happened, but I think that's normal, right?
ifconfig
I now have the ra0 connection.
cat /etc/resolv.conf
name server 192.168.1.1
/sbin/route -n
Everything is empty, I have the columns:
Destination - Gateway - Genmask - Metric Ref - Use Iface
and that's it.
I tested ifup ra0
ifup: interface ra0 already configured.
:))
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
It gave me the "Linux Programmer's Manual", I didn't understand everything :/
ifconfig ra0 up
Nothing happened, but I think that's normal, right?
ifconfig
I now have the ra0 connection.
cat /etc/resolv.conf
name server 192.168.1.1
/sbin/route -n
Everything is empty, I have the columns:
Destination - Gateway - Genmask - Metric Ref - Use Iface
and that's it.
I tested ifup ra0
ifup: interface ra0 already configured.
:))
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
Furthermore, restarting changes nothing (I'm testing Windows methods, you never know :)) and the PC takes a very long time to start at :
configuring network interfaces
But it passes and marks "ok", it only fails when it tries to synchronize the clock.
I don't know if it's related, but the LED on my WiFi card doesn't light up, like when the drivers are not installed under Windows. However, the card is recognized with the correct name in the device manager...
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
configuring network interfaces
But it passes and marks "ok", it only fails when it tries to synchronize the clock.
I don't know if it's related, but the LED on my WiFi card doesn't light up, like when the drivers are not installed under Windows. However, the card is recognized with the correct name in the device manager...
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time ...
man wireless
It gave me the "Linux Programmer's Manual", I didn't understand everything :/
This is so you know how the file /etc/network/interfaces works because the structure can differ between Debian and Ubuntu (I think)
ifconfig ra0 up
Nothing happened, but I think that's normal, right?
Yeah, it creates ra0 which should then appear when you do an ifconfig
ifconfig
I now have the ra0 connection.
There you go :)
cat /etc/resolv.conf
name server 192.168.1.1
The DNS is okay, your router does DHCP and DNS
/sbin/route -n
Everything is empty, I have the columns:
Destination - Gateway - Genmask - Metric Ref - Use Interface
and that's it.
That's not good, you're missing the route to your router that should have appeared automatically after activating ra0. There must be something missing in /etc/network/interfaces, for example the network field.
Otherwise, you can do:
I tested ifup ra0
ifup: interface ra0 already configured.
That's normal, ifconfig ra0 up already did that. The ifup just brings ra0 up according to /etc/network/interfaces. It's just that later ifup can be done at startup.
Good luck
It gave me the "Linux Programmer's Manual", I didn't understand everything :/
This is so you know how the file /etc/network/interfaces works because the structure can differ between Debian and Ubuntu (I think)
ifconfig ra0 up
Nothing happened, but I think that's normal, right?
Yeah, it creates ra0 which should then appear when you do an ifconfig
ifconfig
I now have the ra0 connection.
There you go :)
cat /etc/resolv.conf
name server 192.168.1.1
The DNS is okay, your router does DHCP and DNS
/sbin/route -n
Everything is empty, I have the columns:
Destination - Gateway - Genmask - Metric Ref - Use Interface
and that's it.
That's not good, you're missing the route to your router that should have appeared automatically after activating ra0. There must be something missing in /etc/network/interfaces, for example the network field.
Otherwise, you can do:
/sbin/route add default gw 192.168.1.1 ra0
I tested ifup ra0
ifup: interface ra0 already configured.
That's normal, ifconfig ra0 up already did that. The ifup just brings ra0 up according to /etc/network/interfaces. It's just that later ifup can be done at startup.
Good luck
Thank you, I'm trying on Friday ;)
--
The urgent is done, the impossible is in progress,
For miracles, please allow time...
--
The urgent is done, the impossible is in progress,
For miracles, please allow time...
I just saw something. The WiFi diode should be lit (it activates via the interface http://192.168.1.1 ).
Moreover, when you connect to the WiFi network, you need to press the "synchronization" button on the WiFi (so that you can connect to it). At least on the Sagem LBs...
In practice, this should add the MAC addresses of the WiFi cards that manage to connect during this time frame thanks to their WEP key.
Moreover, when you connect to the WiFi network, you need to press the "synchronization" button on the WiFi (so that you can connect to it). At least on the Sagem LBs...
In practice, this should add the MAC addresses of the WiFi cards that manage to connect during this time frame thanks to their WEP key.
ifconfig
lo Link encap: Local loopback
inet addr:127.0.0.1 Mask:255.0.0.0
addr inet6: ::1/128 scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:49100 errors:0 dropped:0 overruns:0 frame:0
TX packets:49100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:21085 (20.5kb) TX bytes:21085 (20.5kb)
ra0 Link encap:Ethernet HWAddr 00:08:D3:05:13:D3
addr inet6: fe80::208:d3ff:fe05:13d3/64 Scope:Link
UP LOOPBACK RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0b) TX bytes:308412 (301.1kb)
Interrupt:5 Base address:0x4000
iwlist ra0 scanning
Scan completed:
Cell 01 - Address: 00:14:A4:34:4D:88
Mode:Managed
ESSID:"WANADOO-5703"
Encryption key:on
Channel:1
Quality:0/100 Signal level:-62dBm Noise level:-206dBm
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
lo Link encap: Local loopback
inet addr:127.0.0.1 Mask:255.0.0.0
addr inet6: ::1/128 scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:49100 errors:0 dropped:0 overruns:0 frame:0
TX packets:49100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:21085 (20.5kb) TX bytes:21085 (20.5kb)
ra0 Link encap:Ethernet HWAddr 00:08:D3:05:13:D3
addr inet6: fe80::208:d3ff:fe05:13d3/64 Scope:Link
UP LOOPBACK RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0b) TX bytes:308412 (301.1kb)
Interrupt:5 Base address:0x4000
iwlist ra0 scanning
Scan completed:
Cell 01 - Address: 00:14:A4:34:4D:88
Mode:Managed
ESSID:"WANADOO-5703"
Encryption key:on
Channel:1
Quality:0/100 Signal level:-62dBm Noise level:-206dBm
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
iwconfig
lo no wireless extension
eth0 no wireless extension
ra0 RT2500 Wireless ESSID:"WANADOO-5703"
Mode:Managed Frequency2.412GHz Bit rate:11Mbps
RTS thr:off Fragment thr:off
Enncryption key:XXXXXXXXXXXXXXXXX Security mode:open
Link quality:0/100 Signal level:-120dB Noise level:-206dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extension
/sbin/route -n
Kernel IP routing table
Destination - Gateway - Genmask - Flags Metric Ref - Use Iface
cat /etc/resolv.conf
nameserver 192.168.1.1
-------------------------------------------------------------
It still doesn't work :((
By the way, when should the access point be set to association mode?
Thank you :)
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
lo no wireless extension
eth0 no wireless extension
ra0 RT2500 Wireless ESSID:"WANADOO-5703"
Mode:Managed Frequency2.412GHz Bit rate:11Mbps
RTS thr:off Fragment thr:off
Enncryption key:XXXXXXXXXXXXXXXXX Security mode:open
Link quality:0/100 Signal level:-120dB Noise level:-206dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extension
/sbin/route -n
Kernel IP routing table
Destination - Gateway - Genmask - Flags Metric Ref - Use Iface
cat /etc/resolv.conf
nameserver 192.168.1.1
-------------------------------------------------------------
It still doesn't work :((
By the way, when should the access point be set to association mode?
Thank you :)
--
The urgent is done, the impossible is in progress,
For miracles, please allow some time...
- 1
- 2
Next
Oh! Cool!
I'm going to give it a try, thanks.
--
The urgent is done, the impossible is in progress,
For miracles, allow for a delay ...