Can't connect to internet with Wifi
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
Can't connect to internet with Wifi
Hi all, I just started using Puppy, and I love it! I am almost totally new to Linux, but I have already managed to try out several puplets as well as the new kernel (2.6.25). However, I have been unable to connect to the internet via wireless. I can connect via LAN at work, but at home I have to connect wireless to the modem that is nextdoor in my landlord's flat.
I have been searching this forum for solutions, but most suggestions are over my head, as the total noob I am. Also, the process is really slow since I use Windows to get on the internet, then I have to reboot into Puppy to try the solution, then go back to find another solution etc.
Using the network wizard the scan button finds the network, and I enter the key (for the WEP encryption) and hit "save", and "use this profile", but when I try to open a webpage I immediately get "page not found". I have tried a large number of variations on the various options in the wizard over the last couple of days, with no luck. I tried the same with the new kernel, and with a puplet based on the 3.01 version of Puppy.
I have an HP pavilion zt3000 laptop, 1.6 Ghz, 512 Mb ram, Intel PRO/Wireless 2200/2915 network, Puppy Linux 4.00.
I would like to mention also that I can connect wirelessly without any problems from Xubuntu and Linux mint. But I like Puppy because of the incredible speed, and the ease with which I can remaster my USB-installation to try new versions. Please help me to solve this problem!
I have been searching this forum for solutions, but most suggestions are over my head, as the total noob I am. Also, the process is really slow since I use Windows to get on the internet, then I have to reboot into Puppy to try the solution, then go back to find another solution etc.
Using the network wizard the scan button finds the network, and I enter the key (for the WEP encryption) and hit "save", and "use this profile", but when I try to open a webpage I immediately get "page not found". I have tried a large number of variations on the various options in the wizard over the last couple of days, with no luck. I tried the same with the new kernel, and with a puplet based on the 3.01 version of Puppy.
I have an HP pavilion zt3000 laptop, 1.6 Ghz, 512 Mb ram, Intel PRO/Wireless 2200/2915 network, Puppy Linux 4.00.
I would like to mention also that I can connect wirelessly without any problems from Xubuntu and Linux mint. But I like Puppy because of the incredible speed, and the ease with which I can remaster my USB-installation to try new versions. Please help me to solve this problem!
I also have this problem, I have managed once to get wireless working, then I turned it off, saving my settings, but next time I booted up, nothing, nada, nil, zip, zero!
In resolv.conf its showing the right name server, and the domain to search, but it just keeps giving me the wrong ip address and not connecting.
In resolv.conf its showing the right name server, and the domain to search, but it just keeps giving me the wrong ip address and not connecting.
I managed to get it networking working again! see here
Is your network ssid hidden?
try un-hiding it and see if you can connect that way!
Is your network ssid hidden?
try un-hiding it and see if you can connect that way!
Re: Can't connect to internet with Wifi
Haven't fiddled with that chip for a bit but have used it plug & play wep 64 hex with many vers of pup.astrogreek wrote:PRO/Wireless 2200/2915 network, Puppy Linux 4.00.
A search of 2915 (Check off > Display results as: Posts) brings up quite a bit including this..
How to configure wifi from the commandline
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
Is that something you do with the modem? I don't own the modem nor have access to it.Is your network ssid hidden?
try un-hiding it and see if you can connect that way!
This morning I quickly tried the guide for manual configuration, but I had a few problems.How to configure wifi from the commandline
The first line gave me an error along the lines of "directory not found", I'm guessing the * needs to be replaced with something, but as a total beginner I have no idea.rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth1
The second command gave an output that seemed to indicate it was not successful. I'll keep trying when I get back home tonight.
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
I already tried both the the new kernel and the earlier, as well as the previous version of Puppy, I mentioned that in my first post.HairyWill wrote:Puppy 4.00 with the 2.6.25 kernel is distributed from the test area. If you are having problems, it would be sensible to try the earlier kernel version to see if that works.
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
How do I copy text from the terminal? I saw somewhere here to use shift+delete, but that did not work. At the moment I don't have the patience to write down the whole output.so what do you get for
iwconfig
iwlist scan
Edit: I could give you the results I get from Xubuntu, where I can connect, and I can copy text from the terminal window, if that would be any help.
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
OK here is what I get:HairyWill wrote:so what do you get for
iwconfig
iwlist scan
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 unassociated ESSID:"OTE CONNX"
Mode:Managed Frequency=2.437 GHz Access Point: 00:0E:35:64:2D:A5
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:0000-0000-0000-0000-0000-0000-00 Security mode:restricted
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 00:13:33:0A:80:9E
ESSID:"OTE CONNX"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=71/100 Signal level=-57 dBm
Extra: Last beacon: 100ms ago
jonyo thanks for the tip!
possible solution to astrogreek's problem
Once you boot open the /etc/wpa_supplicant.conf and make it look like this:
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="OTE CONNX"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="Your Password in Quotes"
pairwise=TKIP
group=TKIP
}
save this and close.
After that open the terminal and write:
wpa_supplicant -s -D ipw -i eth1 -c /etc/wpa_supplicant.conf -dd
after this write dhcpcd eth1
that's it.
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="OTE CONNX"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="Your Password in Quotes"
pairwise=TKIP
group=TKIP
}
save this and close.
After that open the terminal and write:
wpa_supplicant -s -D ipw -i eth1 -c /etc/wpa_supplicant.conf -dd
after this write dhcpcd eth1
that's it.
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
You could try the following.
1. Check which modules are needed for your card. This can be done in a terminal executing the command
I expect the output would contain something similar to ipw2200.
2. Then, always in a terminal, write the following sequence of six commands (substitute ipw2200 with the output in step 1, and YOUR_WEP_KEY by your key):
NOTE: The command iwconfig ends at YOUR_WEP_KEY and must be entered in a single line
3. You can test if the network works issuing the command
4. In case the network works, the sequence of commands in step 2 can be written in a script file and executed automatically at every boot.
5. If the network still fails, you can try to repeat the sequence of commands in step 2 by BUT interchanging the order of the iwconfig and ifconfig commands.
Hope that helps
1. Check which modules are needed for your card. This can be done in a terminal executing the command
Code: Select all
lsmod | grep ipw
2. Then, always in a terminal, write the following sequence of six commands (substitute ipw2200 with the output in step 1, and YOUR_WEP_KEY by your key):
Code: Select all
rmmod ipw2200
modprobe ipw2200
rm /var/run/dhcpcd-eth1.pid
iwconfig eth1 essid "OTE CONNX" freq 2.437G channel 6 mode managed ap 00:13:33:0A:80:9E key YOUR_WEP_KEY
ifconfig eth1 up
dhcpcd -d eth1
3. You can test if the network works issuing the command
Code: Select all
ping www.google.com
5. If the network still fails, you can try to repeat the sequence of commands in step 2 by BUT interchanging the order of the iwconfig and ifconfig commands.
Hope that helps
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
No luck... here is what I get:
# lsmod | grep ipw
ipw2200 134576 0
ieee80211 33864 1 ipw2200
firmware_class 9600 1 ipw2200
# rmmod ipw2200
# modprobe ipw2200
# rm /var/run/dhcpcd-eth1.pid
# iwconfig eth1 essid "OTE CONNX" freq 2.437G channel 6 mode managed ap 00:13:33:0A:80:9E key 1234567890xxx
# ifconfig eth1 up
# dhcpcd -d eth1
Info, eth1: dhcpcd 3.1.8 starting
Info, eth1: hardware address = 00:0e:35:64:2d:a5
Info, eth1: DUID = 00:01:00:01:0f:d9:1f00:0e:35:64:2d:a5
Info, eth1: broadcasting for a lease
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: waiting on select for 20 seconds
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Error, eth1: timed out
Info, eth1: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth1.info'
Debug, eth1: sending ARP probe #1
Debug, eth1: sending ARP probe #2
Debug, eth1: sending ARP probe #3
Debug, eth1: sending ARP claim #1
Debug, eth1: sending ARP claim #2
Warning, eth1: using IPV4LL address 169.254.112.20
Info, eth1: adding IP address 169.254.112.20/16
Debug, eth1: no dns information to write
Debug, eth1: exec "/etc/dhcpcd.sh" "/var/lib/dhcpcd/dhcpcd-eth1.info" "new"
Debug, eth1: forking to background
# ping www.google.com
ping: bad address 'www.google.com'
# lsmod | grep ipw
ipw2200 134576 0
ieee80211 33864 1 ipw2200
firmware_class 9600 1 ipw2200
# rmmod ipw2200
# modprobe ipw2200
# rm /var/run/dhcpcd-eth1.pid
# iwconfig eth1 essid "OTE CONNX" freq 2.437G channel 6 mode managed ap 00:13:33:0A:80:9E key 1234567890xxx
# ifconfig eth1 up
# dhcpcd -d eth1
Info, eth1: dhcpcd 3.1.8 starting
Info, eth1: hardware address = 00:0e:35:64:2d:a5
Info, eth1: DUID = 00:01:00:01:0f:d9:1f00:0e:35:64:2d:a5
Info, eth1: broadcasting for a lease
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: waiting on select for 20 seconds
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Debug, eth1: sending DHCP_DISCOVER with xid 0x66906f1e
Error, eth1: timed out
Info, eth1: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth1.info'
Debug, eth1: sending ARP probe #1
Debug, eth1: sending ARP probe #2
Debug, eth1: sending ARP probe #3
Debug, eth1: sending ARP claim #1
Debug, eth1: sending ARP claim #2
Warning, eth1: using IPV4LL address 169.254.112.20
Info, eth1: adding IP address 169.254.112.20/16
Debug, eth1: no dns information to write
Debug, eth1: exec "/etc/dhcpcd.sh" "/var/lib/dhcpcd/dhcpcd-eth1.info" "new"
Debug, eth1: forking to background
# ping www.google.com
ping: bad address 'www.google.com'
Hi astrogreek.
In some forum, someone claimed having solved the problem adding a -T flag to the dhcpcd command:
It may be worth giving it a try...
In some forum, someone claimed having solved the problem adding a -T flag to the dhcpcd command:
Code: Select all
dhcpcd -d -T eth1
searching for
man dhcpcd
shows
man dhcpcd
shows
so I would be surprised if the -T parameter helps-T
Test case, when dhcpcd goes through the DHCP negotiation sequence but doesn't actually configure the interface. It does however write the <ConfigDir>/dhcpcd-<interface>.info and <ConfigDir>/dhcpcd-<interface>.cache files and it does attempt to execute <ConfigDir>/dhcpcd.exe script. The pathname of dhcpcd.exe executable script can be changed with -c <ExecFilePath> option. -T option is used primarily for testing DHCP servers, for obtaining multiple IP addresses for the same dummy interface, and/or configuring virtual interfaces in conjunction with -L <ConfigDir> and -I <ClientID> options.
-
- Posts: 29
- Joined: Wed 21 May 2008, 14:12
I have followed the steps in this guide: http://www.murga-linux.com/puppy/viewtopic.php?t=22469, including the troubleshooting part further down, with no luck.
from same thread:
from same thread:
I need a bit help to understand this part. I have found an resolv.conf, that contains (from memory) info related to the LAN network at my workplace (I can connect easily from Puppy to that network). I also have a bunch of files named resolv.conf.xxxx where x is some number. I am not sure how to modify this file or what exactly my nameserver is. Is it the same as DNS server?or to obtain a static IP address,
modify /etc/resolv.conf to include your nameservers, then Code:
ifconfig eth1 192.168.0.xx broadcast 192.168.0.255 netmask 255.255.255.0
route add default gw 192.168.0.1 eth1