No wireless in Ubuntu :(
Fred Roller
froller at tnclimited.com
Fri Oct 16 18:13:04 UTC 2009
Christopher Lemire wrote:
>> The problem you have is worse than the title. I can't figure
>> out what your problem is. Please send a lot more about your
>> network.
>>
>
> That's what happened ever since I became a more experienced Linux
> user. I ask questions that are more difficult. Here's some output. Now
> I am in Windows again, so here it shows I can resolve dns.
>
> C:\>ping google.com
>
> Pinging google.com [74.125.67.100] with 32 bytes of data
>
> Reply from 74.125.67.100: bytes=32 time=54ms TTL=47
> Reply from 74.125.67.100: bytes=32 time=59ms TTL=47
> Reply from 74.125.67.100: bytes=32 time=47ms TTL=47
> Reply from 74.125.67.100: bytes=32 time=53ms TTL=47
>
> Ping statistics for 74.125.67.100:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 47ms, Maximum = 59ms, Average = 53ms
>
> C:\>
>
> Here is Linux output.
>
> chris at ubuntu:~$ ifconfig
> eth1 Link encap:Ethernet HWaddr 00:c0:26:7d:4c:df
> inet addr:192.168.1.1 Bcast:192.168.1.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)
> Interrupt:21 Base address:0xce00
>
> lo Link encap:Local 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:532 errors:0 dropped:0 overruns:0 frame:0
> TX packets:532 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:37240 (37.2 KB) TX bytes:37240 (37.2 KB)
>
> wlan2 Link encap:Ethernet HWaddr 00:01:f7:d8:f6:aa
> inet addr:192.168.1.225 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::201:f7ff:fed8:f6aa/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:69 errors:5 dropped:132 overruns:0 frame:0
> TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:10409 (10.4 KB) TX bytes:7300 (7.3 KB)
>
> chris at ubuntu:~$ route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
> 192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan2
> 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan2
> chris at ubuntu:~$ ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.058 ms
> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.049 ms
> 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.037 ms
> 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.037 ms
> ^C
> --- 192.168.1.1 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 2998ms
> rtt min/avg/max/mdev = 0.037/0.045/0.058/0.010 ms
> chris at ubuntu:~$ ping google.com
> ping: unknown host google.com
> chris at ubuntu:~$
>
> The routing table shows 0.0.0.0 as my gateway. That sounds like it
> could be the problem.
>
>
Assuming your router is set to default 192.168.1.1 ip and is issuing
dhcp, having your ip on eth0 set to 192.168.1.1 will conflict. Have you
tried setting the eth0 to 192.168.1.2 (or something other than
192.168.1.1) to see if this clears up the issue?
--
Fred
www.fwrgallery.com
"Life is like linux, simple. If you are fighting it you are doing something wrong."
More information about the ubuntu-users
mailing list