Can't connect to the internet via WLAN

Tiny Core Base > CorePlus

(1/2) > >>

r50e:
Hi there,

I run in the same problem as Trace. I have tried to setup a static IP for my WLAN device - without success. See: (http://forum.tinycorelinux.net/index.php/topic,16571.0.html).

I decided to activate DHCP for testing on the AP. And now I'm really confused:

1. Used wifi.sh and entered credentials for WPA
2. I get IP from AP (as expected)
3. But I can't connect to the Internet

In fact, if I get a IP from AP the connection (wpa_supplicant is correct konfigured).
I have a correct default gateway and a DNS Server (from DHCP)
But I can't connect to the internet - why???

I figured out, that there are some errors on the eth1 (my wlan device) in the RX queu (2 errors and 80 dropped). But why is dhcp working and the rest of the connection not?

The hardware I run TC is a IBM R50e and the firmware driver I load for WLAN is the ipw2020

gerald_clark:
Post the output of
ifconfig -a
ipconfig
route -n
cat /etc/resolv.conf

r50e:
Here the output

--- Code: ---ifconfig -a
dummy0 Link encap:Ethernet HWaddr 82:D0:B1:DF:DB:10
BROADCAST NOARP 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 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 00:0A:E4:3A:B7:23
inet addr:192.168.222.65 Bcast:192.168.222.255 Mask:255.255.255.0
UP BROADCAST MULTICAST 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 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth1 Link encap:Ethernet HWaddr 00:13:CE:8D:F7:46
inet addr:192.168.222.60 Bcast:192.168.222.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20233 errors:25 dropped:2510 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4304700 (4.1 MiB) TX bytes:5384 (5.2 KiB)

ip_vti0 Link encap:UNSPEC HWaddr 00-00-00-00-FF-00-00-00-00-00-00-00-00-00-00-00
NOARP 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 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:216 errors:0 dropped:0 overruns:0 frame:0
TX packets:216 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21944 (21.4 KiB) TX bytes:21944 (21.4 KiB)

tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 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 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

--- End code ---

--- Code: ---route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.222.1 0.0.0.0 UG 0 0 0 eth1
0.0.0.0 192.168.222.1 0.0.0.0 UG 0 0 0 eth0
127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo
192.168.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.222.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
--- End code ---

--- Code: ---cat /etc/resolv.conf
search fritz.box
nameserver 192.168.222.1
--- End code ---

I startet with syslog option, but I found nothing of interest (dmesg also not)

tinypoodle:
Use boot code "nodhcp".

gerald_clark:
Also, don't have two network interfaces up on the same subnet.

Navigation

[0] Message Index

[#] Next page

Go to full version