LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Wifi Connects, But No Network Access, But Wired Works (https://www.linuxquestions.org/questions/linux-wireless-networking-41/wifi-connects-but-no-network-access-but-wired-works-880213/)

gentisle 05-11-2011 10:19 PM

Wifi Connects, But No Network Access, But Wired Works
 
I tried to ask this question in the Linux Mint Forum, but either those who answered didn't read my post carefully, or I have forgotten how to write well in English. I'll assume the later.

Problem: I cannot use wifi to browse the internet, though Mint says it's connected. I have used this laptop and LM10 installation to get on other wifi networks. What's different about this network? I'm temporarily staying w/a friend, and his ISP provides the modem-router combo, and my friend doesn't know anything about the router settings. It's Verizon, and I tried pointing a browser to 192.168.1.1 and the GUI logon comes up, but my friend is oblivious to those settings. I get the feeling Verizon doesn't want customers change those settings.

I've got a Medion Laptop, 2007 vintage. AMD x2/4GB/Nvidia 6150 (shared), ZD1211 wifi, Nvidia wired network, Linux Mint 10/Gnome/amd64. All updates applied. The router gateway address is 192.168.1.1.

For info: I have another (old and too slow to be useful) HP laptop w/WinXP. Also, I have another HDD which I switch in/out of the Medion. The other HDD has WinXP, but it's contaminated or something and keeps crashing hard.

What I've tried:
1. Both of my laptops will correctly work with my friend's wifi UNDER Windows, but again, the Windows on the Medion keeps crashing, and right now, I don't have time to reinstall.
2. Under LM10, the Medion connects correctly and works correctly when WIRED to the modem-router. However, sitting hunched over on the floor to use the wired connection is not do-able for someone of my maturity.
3. LM10 reports that wifi connects, but I cannot ping any address (see ping results below), I cannot browse (see below).
4. I cannot access my friend's modem-router, nor change it (wouldn't that be impolite to mess w/other people's things when you visit them?)
5. When I put the mouse cursor over the wifi bar graph, it says,"Wireless network connection 'FriendsNet' active: FriendsNet (100%)".
6. This installation of Linux on this laptop has connected to other wifi networks.
7. I used siw.exe for Windows and PC Wizard on my old laptop to try to get info necessary for changing something, but alas, there is nothing there that makes sense to me except that it said the domain name is "home". Do I have to put the domain in or will LM10 in particular and Linux in general automatically connect?


Code:

/etc/resolv.conf
# Generated by NetworkManager
nameserver 208.67.222.222
nameserver 208.67.220.220

/etc/hosts
192.168.1.4        mycpuhostname        # Added by NetworkManager
127.0.0.1        localhost.localdomain        localhost
::1                mycpuhostname        localhost6.localdomain6        localhost6
127.0.1.1        mycpuhostname

# The following lines are desirable for IPv6 capable hosts
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
10.42.43.1 mycpuhostname


Code:

Ping reports:
ping -c 3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 169.254.10.41 icmp_seq=1 Destination Host Unreachable
From 169.254.10.41 icmp_seq=2 Destination Host Unreachable
From 169.254.10.41 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2003ms

Windows Vista (on my friend's PC) ipconfig reports:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\owner>ipconfig
Windows IP Configuration

Code:

Wireless LAN adapter Wireless Network Connection:
  Connection-specific DNS Suffix  . : home
  Link-local IPv6 Address . . . . . : fe80::bd99:b41:95d7:986e%11
  IPv4 Address. . . . . . . . . . . : 192.168.1.5
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.1.1
Ethernet adapter Local Area Connection:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : somewhere.xx.xx.whoever.com
[can't list actual address for security]
 
Tunnel adapter Local Area Connection* 6:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
Tunnel adapter Local Area Connection* 7:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
Tunnel adapter Local Area Connection* 11:
  Connection-specific DNS Suffix  . :
  IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:306e:35a9:b884:39de
  Link-local IPv6 Address . . . . . : fe80::306e:35a9:b884:39de%13
  Default Gateway . . . . . . . . . : ::

Here's the output of mintwifi:

Code:

-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0    IEEE 802.11bg  ESSID:"MyFriends-SSID" 
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: A6:B6:28:C5:D9:6A 
          Tx-Power=20 dBm 
          Retry  long limit:7  RTS thr:off  Fragment thr:off
          Encryption key:AF28-1AB9-DE78-FCD3-7AD7-48F7-43
          Power Management:off
         
vboxnet0  no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0      Link encap:Ethernet  HWaddr 00:16:d3:84:92:b8 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:60952 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35908 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:81411951 (81.4 MB)  TX bytes:3345103 (3.3 MB)
          Interrupt:20 Base address:0x2000

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:1998 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1998 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:138091 (138.0 KB)  TX bytes:138091 (138.0 KB)

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00 
          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:457 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:28296 (28.2 KB)

vboxnet0:avahi Link encap:Ethernet  HWaddr 0a:00:27:00:00:00 
          inet addr:169.254.1.79  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

wlan0    Link encap:Ethernet  HWaddr 00:60:b3:37:d7:27 
          inet6 addr: fe80::260:b3ff:fe37:d727/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:56461 (56.4 KB)

wlan0:avahi Link encap:Ethernet  HWaddr 00:60:b3:37:d7:27 
          inet addr:169.254.7.139  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

-------------------------
* V. querying DHCP...
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:16:d3:84:92:b8
Sending on  LPF/eth0/00:16:d3:84:92:b8
Listening on LPF/vboxnet0/0a:00:27:00:00:00
Sending on  LPF/vboxnet0/0a:00:27:00:00:00
Listening on LPF/wlan0/00:60:b3:37:d7:27
Sending on  LPF/wlan0/00:60:b3:37:d7:27
Sending on  Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 2
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-------------------------
* VI. querying nslookup google.com...
;; connection timed out; no servers could be reached

Firefox reports:
Code:

Unable to connect
Firefox can't establish a connection to the server at google.com
*  The site could be temporarily unavailable or too busy. Try again in a few
          moments.

*  If you are unable to load any pages, check your computer's network
          connection.
*  If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.


john test 05-12-2011 07:03 AM

Have you set up your encryption to match the encryption on fios router?

mrmnemo 05-12-2011 08:49 AM

hi,
it does not look like your getting any DHCP offers from your router. This may sound odd, but are you running a firewall? Did you set it up or download a script or something? The wired connection is working on the LM10 machine to the EXACT same router/AP as the wireless point? Are you trying to forward DHCP request from a wireless AP to a router?


Also, the tunnels you have may be causing you routing issues. try shutting off your vm. In my experience, if the tunnel is not taken down correctly, routing problems can come up.

For example: you posted
Quote:

Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::bd99:b41:95d7:986e%11
IPv4 Address. . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Which does not make sense when I see :
Quote:

Ping reports:
ping -c 3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 169.254.10.41 icmp_seq=1 Destination Host Unreachable
From 169.254.10.41 icmp_seq=2 Destination Host Unreachable
From 169.254.10.41 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2003ms
For some reason your system is not using the ipv4 address your pulling down from the router. Your host is pinging on a 169 ip ( thats what you get when your NOT connected); however, your iwconfig clearly shows an ip in the 192.168.1.0/24 range. So, I would have to say that your tunnel / tap devices are causing you some problems. I am not sure what your running / why your running the tunnel / tap devices. However, you can bring them down. Just man page ifconfig for that. Also, vboxnet makes me think your running virtualbox, am I correct? Perhaps you could take a look at that.

gentisle 05-12-2011 11:09 AM

To john test:
No, I haven't done anything to encryption, because I don't know anything about that. The system is as LinuxMint 10 set itself up.

To mrmnemo:
Sorry, but most of what you said is above my head when it comes to Linux and Linux networking. Yes, I do have VirtualBox installed. I do agree that the results of my pinging were weird. I cannot verify it, and my friend says, "No", but I thought maybe his office might have configured some VPN stuff into the router. Perhaps his office Windows PC does that automatically.

If there is a firewall running in LM10, it must have been setup when I installed the system. I have no idea about any of that.

As far as bringing down the tunneling or tap or whatever that is, since I didn't set that up, and either LM10 or VirtualBox set it up, I don't know anything about it, and I haven't changed anything with regard to it.

One strange thing. I did chat w/a Verizon rep, and got the default login. I tried that, and not only can I not login, but when I type in the password field, each key press produces 4 characters. My friend doesn't know about computer stuff like that, so I'm wondering if someone in the apartment has hacked his router. Any ideas on how to investigate that would be appreciated. I guess surge could cause some weird behavior like that. I've seen strange things in cpu hardware because of electrical surge. Any other thoughts or ideas would be greatly appreciated. Thanks.

mrmnemo 05-12-2011 11:25 AM

Hi,
You cant log on to the router or anything outside of your local box because you dont have a valid route. You see, Network-Manager says " hey I got us an address from the router". However, your system seems to be getting conflagurated with the vboxnet stuff (maybe). Try this, turn off your virtualbox guest ( your VM ) , kill the virtualbox gui itself, then run
Code:

sudo service networking restart
Then connect to your wireless router. One more thing, Right-click on the network-manager icon ( the thing you uise to connect to the wireless), select "Edit Connections", select "Wireless", select the wireless connection your having issues with ( in your case it looks like "home") and click the "Edit " button. Now, you will see a tab at the far right that says " IPv6", select it and make sure the drop down menue says IGNORE as the method.

After all that, run the following and post the results.
Code:

ifconfig && route && ping -c5 8.8.8.8

Some things to consider:
1. Your computer IS gettting an IP address from your friends router. However, your routing table is kinda boogered up.
2. I have had this happen when using virtualbox.
3. You had ALOT of tunnel interfaces. I thinkn this maybe causing you some issues.
4. The problem you are having is YOUR computer, not the router. This is evident when you see the following:
Quote:

Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::bd99:b41:95d7:986e%11
IPv4 Address. . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Give that stuff a try and get back to us.

mrmnemo 05-12-2011 11:37 AM

Just a side note: once you get all that going you might want to see if your firewall(iptables) is configured.
rrun
Code:

sudo iptables -L
If you see just a few lines that say nothing but "accept" you kinda need to address that.
A good option for those getting started might be bastille. Its in the repos.
Code:

sudo apt-get update && sudo apt-get install bastille
LOL, i just noticed you been on here longer than me and you run opensolaris( i think that requires more smarts than I gots). 8))
Any way, I think the virtualbox might have caused your problems. If you have not set up any tunnels ( think your guests OS in virtualbox getting to the internet ) then I would think that is a good place to start.

mrmnemo 05-12-2011 11:43 AM

One more thing, you could run
Code:

sudo tail -f /var/log/daemon.log
then try and connect to the wireless. you should get some output from network manager that could help to weed out the problem.

mrmnemo 05-12-2011 12:04 PM

I just noticed your wlan0 connection is showing "Ad-Hoc", thats kinda fishy. Have you considered restarting the modem as well? Doing a hard reset? Your wireless connection should be showing "Managed" if your connected to an wireless ROUTER. Ad-HOc is usually between two machines. In addition to the other stuff to run: run iwlist scan and see what you get.

scheidel21 05-12-2011 09:56 PM

I bet your routing table isn't setting up properly I am very interested to see what the output of route is. Further are you setting the IP manually or pulling one from the router via dhcp? If you take down the other interfaces "ifconfig interface down" that are not actively being used does that help?

mrmnemo 05-12-2011 10:08 PM

@scheidle: have you noticed that his wireless interface is in Ad-Hoc mode? I am very interested in that. It is possible that the router is actually just acting as bridge for something else perhaps.

**from his opening post**
Code:

* III. querying iwconfig...
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0    IEEE 802.11bg  ESSID:"MyFriends-SSID" 
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: A6:B6:28:C5:D9:6A 
          Tx-Power=20 dBm 
          Retry  long limit:7  RTS thr:off  Fragment thr:off
          Encryption key:AF28-1AB9-DE78-FCD3-7AD7-48F7-43
          Power Management:off


Wyrm618 05-12-2011 11:07 PM

Is the router possibly a Linksys E2000 or similar model? I had a 10 hour run-in with one over the last weekend that yielded similar results. Though it appeared to be connected to the router (based on the network notification on the taskbar), the network information showed 169.x.x.x as the IP and mentioned something about ad-hoc which I knew was incorrect. Other computers on my network were online without a problem, so I was sure it was isolated to that single computer.

The way I was able to finally acquire a stable internet connection was by manually assigning my IP and DNS information; the router wasn't assigning them correctly for me even though the notification lead me to believe otherwise. I'm not sure how to manually assign the IP and gateway information via Mint (which I presume to be your distro since you made mention of it earlier) and I'm still in my Linux infancy stages so unfortunately I can't be much more help than giving you this new option to look into.

Hope this helps. Good luck!

Edit: just reread your initial post and realized you mention a Verizon router. My apologies there. Hopefully the information is still valid, though.

gentisle 05-12-2011 11:42 PM

@ everyone, thanks so much for the help, this is really driving me crazy since nothing makes sense.

Hi mrmnemo,

It's funny how this forum can make me look like I should know a lot about Linux/*nix. Yes, I've been trying to learn it for years. But most of the time, I've had such a hard time getting all or most all the hardware to work, that I haven't been able to "just use" Linux or OpenSolaris. And OpenSolaris is even more difficult as you know, and I've gotten almost nowhere on that. It was on my desktop, but that is packed away for my move, and I don't know when I'll have time to get it up and running again. And frankly, I haven't had the time (in recent years) to spend learning the *nix systems, and computers are my big hobby.

It sounds like you are assuming that VirtualBox is running, or either I don't know the VirtualBox technical lingo. Anyway, that VirtualBox stuff mentioned by the mintwifi command doesn't mean it's running -- unless it's always running from the time I boot, and I don't see "Virtual" anything listed in the processes under the System Monitor app. By "kill", I hope you didn't mean to unistall VirtualBox, as my only decent working Windows installation is there. I'm assuming you meant kill the process, but there is none running.

sudo service networking restart yeilds "restart: Unknown instance:" I guess that is a Linux Mint difference.

Code:

~ $ sudo iptables -L
Chain INPUT (policy ACCEPT)
target    prot opt source              destination       
ACCEPT    udp  --  anywhere            anywhere            udp dpt:bootps
ACCEPT    tcp  --  anywhere            anywhere            tcp dpt:bootps
ACCEPT    udp  --  anywhere            anywhere            udp dpt:domain
ACCEPT    tcp  --  anywhere            anywhere            tcp dpt:domain

Chain FORWARD (policy ACCEPT)
target    prot opt source              destination       
ACCEPT    all  --  anywhere            10.42.43.0/24
 
      state RELATED,ESTABLISHED
ACCEPT    all  --  10.42.43.0/24
 
        anywhere           
ACCEPT    all  --  anywhere            anywhere           
REJECT    all  --  anywhere            anywhere            reject-with icmp-port-unreachable
REJECT    all  --  anywhere            anywhere            reject-with icmp-port-unreachable

Chain OUTPUT (policy ACCEPT)
target    prot opt source              destination

I notice the 2 "REJECT"s and though I don't know what all that means, my gut is telling me it's showing problem is there (big surprise to me).

As for the ifconfig &&...
Code:

~ $ ifconfig && route && ping -c 5 8.8.8.8
eth0      Link encap:Ethernet  HWaddr 00:16:d3:84:92:b8 
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::216:d3ff:fe84:92b8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2420 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2067 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1512027 (1.5 MB)  TX bytes:310633 (310.6 KB)
          Interrupt:20 Base address:0x8000

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:176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:176 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12253 (12.2 KB)  TX bytes:12253 (12.2 KB)

wlan0    Link encap:Ethernet  HWaddr 00:60:b3:37:d7:27 
          inet addr:10.42.43.1  Bcast:10.42.43.255  Mask:255.255.255.0
          inet6 addr: fe80::260:b3ff:fe37:d727/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:138 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:32387 (32.3 KB)

Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
10.42.43.0      *              255.255.255.0  U    2      0        0 wlan0
192.168.1.0    *              255.255.255.0  U    1      0        0 eth0
link-local      *              255.255.0.0    U    1000  0        0 wlan0
default        192.168.1.1    0.0.0.0        UG    0      0        0 eth0
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8
 
: icmp_req=1 ttl=53 time=54.6 ms
64 bytes from 8.8.8.8
 
: icmp_req=2 ttl=53 time=54.8 ms
64 bytes from 8.8.8.8
 
: icmp_req=3 ttl=53 time=53.8 ms
64 bytes from 8.8.8.8
 
: icmp_req=4 ttl=53 time=55.7 ms
64 bytes from 8.8.8.8
 
: icmp_req=5 ttl=53 time=54.1 ms

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 53.869/54.658/55.777/0.710 ms

I didn't think that my friend's router was the problem because I could access it from Windows.

I don't like the idea of installing Bastille Linux, since things aren't working now, I'd be afraid that might really screw things up or just screw them up.

Code:

~ $ iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wlan0    Scan completed :
          Cell 01 - Address: 00:24:D2:4D:E9:4E
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=69/100  Signal level=69/100 
                    Encryption key:on
                    ESSID:"Router's SSID"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000d74df8181
                    Extra: Last beacon: 10ms ago
                    IE: Unknown: 00055746434D33
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030101
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0102
                    IE: Unknown: 32043048606C
          Cell 02 - Address: 00:24:D2:CA:8D:35
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=27/100  Signal level=27/100 
                    Encryption key:on
                    ESSID:"6H9MU"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000000f6342791
                    Extra: Last beacon: 30ms ago
                    IE: Unknown: 00053648394D55
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030101
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0102
                    IE: Unknown: 32043048606C
          Cell 03 - Address: 00:24:D2:39:C6:9D
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=16/100  Signal level=16/100 
                    Encryption key:on
                    ESSID:"KF5M5"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000112c3d8181
                    Extra: Last beacon: 10ms ago
                    IE: Unknown: 00054B46354D35
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030101
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0102
                    IE: Unknown: 32043048606C
          Cell 04 - Address: 00:24:D2:46:91:A1
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=16/100  Signal level=16/100 
                    Encryption key:on
                    ESSID:"8CXDG"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000086e1b36a
                    Extra: Last beacon: 10ms ago
                    IE: Unknown: 00053843584447
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030101
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0102
                    IE: Unknown: 32043048606C
          Cell 05 - Address: 3A:EB:62:4D:22:23
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality:0  Signal level:0  Noise level:0
                    Encryption key:on
                    ESSID:"Router's SSID"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Ad-Hoc
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 3107850ms ago
                    IE: Unknown: 00055746434D33
                    IE: Unknown: 010882840B160C121824
                    IE: Unknown: 030101
                    IE: Unknown: 06020000
                    IE: Unknown: 32043048606C

vboxnet0  Interface doesn't support scanning.

Cell 02-04 are the neighbor's network's. I find it strange that my friend's router shows up twice on the same channel, but I don't know what that means - other than seeing the Master and Ad-hoc modes.

the tail command:
Code:

# tail -f /var/log/daemon.log
May 12 23:13:54 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
May 12 23:14:07 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
May 12 23:14:27 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
May 12 23:14:28 picowave dhclient: No DHCPOFFERS received.
May 12 23:14:28 picowave dhclient: No working leases in persistent database - sleeping.
May 12 23:17:25 picowave ddclient[2097]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
May 12 23:21:03 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
May 12 23:21:06 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
May 12 23:21:13 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
May 12 23:21:25 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
May 12 23:21:43 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
May 12 23:21:51 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
May 12 23:22:03 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
May 12 23:22:04 picowave dhclient: No DHCPOFFERS received.
May 12 23:22:04 picowave dhclient: No working leases in persistent database - sleeping.
May 12 23:22:25 picowave ddclient[2097]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
May 12 23:27:25 picowave ddclient[2097]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
May 12 23:29:08 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
May 12 23:29:11 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
May 12 23:29:19 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
May 12 23:29:33 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
May 12 23:29:41 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
May 12 23:29:53 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
May 12 23:30:05 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
May 12 23:30:09 picowave dhclient: No DHCPOFFERS received.
May 12 23:30:09 picowave dhclient: No working leases in persistent database - sleeping.
May 12 23:32:25 picowave ddclient[2097]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
May 12 23:35:59 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
May 12 23:36:08 picowave dhclient: last message repeated 2 times
May 12 23:36:08 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
May 12 23:36:16 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
May 12 23:36:31 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
May 12 23:36:45 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
May 12 23:36:57 picowave dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
May 12 23:37:00 picowave dhclient: No DHCPOFFERS received.
May 12 23:37:00 picowave dhclient: No working leases in persistent database - sleeping.
May 12 23:37:25 picowave ddclient[2097]: WARNING:  file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''

The tail command wanted to keep trying, but I'm not waiting all night. I've got it connected to wired anyway, and that might keep it from working correctly with the commands.

@scheidel21 As far as I know every thing is automatic, I mean I haven't changed anything except to add DNS addresses for OpenDNS to /etc/resolv.conf (through the GUI interface).

@Wyrm618 No, this is a Westel A90-9100EM15-10.

Hope that helps.

scheidel21 05-13-2011 06:36 PM

Well if everything is automatic it appears that you are not getting a DHCP address from his router. I would try manually adding an IP address and see if you can get to his router, if you still can't that means you are not actually connecting to his router.

It is odd that the connection is showing as ad-hoc but it appears it is broadcasting in both master and ad-hoc which is very odd. Are there 2 -radios on it? Can you force connection to the master mode broadcast?

gentisle 05-13-2011 08:38 PM

OK, here's something else weird that I found. I edited the hosts file...

Code:

192.168.1.4        picowave        # Added by NetworkManager
127.0.0.1        localhost.localdomain        localhost
::1        picowave        localhost6.localdomain6        localhost6
127.0.1.1 picowave

# The following lines are desirable for IPv6 capable hosts
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
10.42.43.1 picowave

... and I changed the last line's address to 192.168.1.15, rebooted and there was no connection either wired or wifi. So I changed it back to the 10... address, rebooted, and the network came back up. Then I clicked on the network icon in the system tray, clicked disconnect for eth0, then did these pings with the results you see below.

Code:

~ $ ping -c 3 192.168.1.1
connect: Network is unreachable
me@picowave ~ $ ping -c 3 www.telkom.net
PING www.telkom.net (125.160.17.26) 56(84) bytes of data.
64 bytes from netkuis.telkom.net (125.160.17.26): icmp_req=1 ttl=51 time=258 ms
64 bytes from netkuis.telkom.net (125.160.17.26): icmp_req=2 ttl=51 time=258 ms
64 bytes from netkuis.telkom.net (125.160.17.26): icmp_req=3 ttl=51 time=260 ms

--- www.telkom.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 258.528/259.291/260.585/0.919 ms
me@picowave ~ $ ping -c 3 www.google.com
PING www.l.google.com (74.125.227.48) 56(84) bytes of data.
64 bytes from 74.125.227.48: icmp_req=1 ttl=54 time=10.3 ms
64 bytes from 74.125.227.48: icmp_req=2 ttl=54 time=7.85 ms
64 bytes from 74.125.227.48: icmp_req=3 ttl=54 time=8.14 ms

--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 10073ms
rtt min/avg/max/mdev = 7.858/8.789/10.363/1.124 ms

Given that, I am wondering if this internet does have ipv6 up and running. If so, is that something that can easily be added/started to an existing system, or do I need to reinstall?

Does this mean my laptop is controlled by The Devil? :))

I think I'll install my other HDD, reinstall OpenSolaris and select ipv6 as well as 4 when I install, then reboot and see what happens.

To add to that I opened the "Network Tools" icon, and selected wlan0.
It lists that ipv4 has address 0.0.0.0, w/a netmask of the same, but ipv6 has a hex address and a netmask of 64.

Furthermove when I iwconfig wlan0, there is only the ipv6 address. So it's not connecting to the ipv4 router. I don't know.
g

mrmnemo 06-18-2011 12:19 AM

Hey,

I have been tied up. Did you get this all sorted out?


All times are GMT -5. The time now is 12:38 PM.