[Fwd: Re: Getting connected to Verizon 3G network -UPDATE]
-------- Original Message --------
Subject: Re: Getting connected to Verizon 3G network -UPDATE
Date: Thu, 31 Dec 2009 19:22:09 -0500
From: Wayne <linuxtwo@gmail.com> <linuxtwo@gmail.com>
To: debian-user@lists.debian.org
References: <4B3B7ECD.1080405@gmail.com> <20091230231525.GA9499@swansys>
<4B3BFCA8.9030605@gmail.com> <4B3C034F.4010400@gmail.com>
<4B3C14D2.8090907@hardwarefreak.com>
Stan Hoeppner wrote:
Wayne <linuxtwo@gmail.com> put forth on 12/30/2009 7:50 PM:
169.254.213.81 every time I get it connected.
A little IPv4 network education is in order:
http://tools.ietf.org/html/rfc3927
Your interface is auto self configuring a link local address because it is
unable to contact a DHCP server. Please read the RFC to better understand the
process.
Your next step is to troubleshoot why your interface isn't able to contact a
DHCP server.
Using the dhcpcd package, recommended b I get the 169.264 address range
again. :-(
Switching to dhcp3 results follow
The following are the results of trying to connect to the MiFI
Output id from the wicd.log
2009/12/31 18:38:21 :: iwconfig ath0 channel 11
2009/12/31 18:38:21 :: iwconfig ath0 ap 00:21:E8:B5:C4:B5
2009/12/31 18:38:21 :: WPA_CLI RESULT IS DISCONNECTED
2009/12/31 18:38:22 :: WPA_CLI RESULT IS SCANNING
2009/12/31 18:38:23 :: WPA_CLI RESULT IS SCANNING
2009/12/31 18:38:24 :: WPA_CLI RESULT IS COMPLETED
2009/12/31 18:38:24 :: Running DHCP
2009/12/31 18:38:24 :: /sbin/dhclient ath0
2009/12/31 18:38:24 :: Internet Systems Consortium DHCP Client V3.1.3
2009/12/31 18:38:24 :: Copyright 2004-2009 Internet Systems Consortium.
2009/12/31 18:38:24 :: All rights reserved.
2009/12/31 18:38:24 :: For info, please visit
https://www.isc.org/software/dhcp/
2009/12/31 18:38:24 ::
2009/12/31 18:38:24 :: wifi0: unknown hardware address type 801
2009/12/31 18:38:25 :: wifi0: unknown hardware address type 801
2009/12/31 18:38:25 :: Listening on LPF/ath0/00:26:5a:bb:e8:c5
2009/12/31 18:38:25 :: Sending on LPF/ath0/00:26:5a:bb:e8:c5
2009/12/31 18:38:25 :: Sending on Socket/fallback
2009/12/31 18:38:29 :: DHCPDISCOVER on ath0 to 255.255.255.255 port 67
interval 8
2009/12/31 18:38:30 :: DHCPOFFER from 192.168.1.1
2009/12/31 18:38:30 :: DHCPREQUEST on ath0 to 255.255.255.255 port 67
2009/12/31 18:38:30 :: DHCPACK from 192.168.1.1
2009/12/31 18:38:31 :: bound to 192.168.1.4 -- renewal in 41564 seconds.
2009/12/31 18:38:31 :: DHCP connection successful
2009/12/31 18:38:31 :: Connecting thread exiting.
2009/12/31 18:38:31 :: IP Address is: None
2009/12/31 18:38:31 :: Sending connection attempt result Success
From the above it seems to be connecting to the MiFi, but wicd say's
not connected.
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 ath0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 ath0
Can not connect to 192.168.1.1, which 'should be' the admin page of the
MiFi or to the internet.
Can connect to 192.168.1.4 which is my default homepage
(/var/www/index.html)
Reply to: