Stan Hoeppner wrote:
Wayne put forth on 1/2/2010 6:28 PM:
Yes and I can connect to the internet with and without the firewall up.
I have more to do on the firewall though. I can't connect to the MiFi
admin page at 192.168.1.1 with the firewall on. So, you are right on
all points. Get the f
Wayne put forth on 1/2/2010 6:28 PM:
> Yes and I can connect to the internet with and without the firewall up.
> I have more to do on the firewall though. I can't connect to the MiFi
> admin page at 192.168.1.1 with the firewall on. So, you are right on
> all points. Get the firewall working
Stan Hoeppner wrote:
Wayne put forth on 1/2/2010 1:53 PM:
As soon as you said firewall, I remembered having this problem before. I
had meant to disable the firewall last night when testing the MiFi
connection, but forgot.
First rule of thumb: Network problem? Disable all firewalls before a
Wayne put forth on 1/2/2010 1:53 PM:
> As soon as you said firewall, I remembered having this problem before. I
> had meant to disable the firewall last night when testing the MiFi
> connection, but forgot.
First rule of thumb: Network problem? Disable all firewalls before additional
troublesh
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 5:31 PM:
Hope this helps!!
Best I can tell all the subnet masks are correct.
I was just thinking... (smoke rises). dmesg shows a small amount of packet
traffic to/from the MiFi WLAN interface, basically the DHCP setup handshake
packets, and
Wayne put forth on 1/1/2010 5:31 PM:
> Hope this helps!!
Best I can tell all the subnet masks are correct.
I was just thinking... (smoke rises). dmesg shows a small amount of packet
traffic to/from the MiFi WLAN interface, basically the DHCP setup handshake
packets, and nothing more. Yet, you
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 2:57 PM:
I think I am missing something but don't know what other then a missing
route statement.
It's not a route issue because the PCs are all on the same class C subnet (or
should be). I looked at a previous route table you posted and it w
Wayne put forth on 1/1/2010 2:57 PM:
> I think I am missing something but don't know what other then a missing
> route statement.
It's not a route issue because the PCs are all on the same class C subnet (or
should be). I looked at a previous route table you posted and it was fine.
Speaking of
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 1:43 PM:
This is a good sign:
/var/log/wicd# ifconfig
ath0 Link encap:Ethernet HWaddr 00:26:5a:bb:e8:c5
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Wayne put forth on 1/1/2010 1:43 PM:
This is a good sign:
> /var/log/wicd# ifconfig
> ath0 Link encap:Ethernet HWaddr 00:26:5a:bb:e8:c5
> inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX p
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 10:43 AM:
Current settings of all info is on the site WICD2 is the file. No
changes will be made here for 2 days.
The requested URL /~huntbrittany/linux/WICD2.info.gz was not found on this
server.
The requested URL /~huntbrittany/linux/WICD
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 10:43 AM:
Current settings of all info is on the site WICD2 is the file. No
changes will be made here for 2 days.
The requested URL /~huntbrittany/linux/WICD2.info.gz was not found on this
server.
The requested URL /~huntbrittany/linux/WICD
Wayne put forth on 1/1/2010 10:43 AM:
> Current settings of all info is on the site WICD2 is the file. No
> changes will be made here for 2 days.
The requested URL /~huntbrittany/linux/WICD2.info.gz was not found on this
server.
The requested URL /~huntbrittany/linux/WICD2 was not found on th
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 8:56 AM:
http://www.intergate.com/~huntbrittany/linux/WICD.info.gz
If that data is accurate...
1. Your wired ethernet card is using 192.168.1.11
2. Your Atheros card is being assigned 192.168.1.3
The wired NIC is first in the binding order a
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 8:56 AM:
http://www.intergate.com/~huntbrittany/linux/WICD.info.gz
If that data is accurate...
1. Your wired ethernet card is using 192.168.1.11
2. Your Atheros card is being assigned 192.168.1.3
The wired NIC is first in the binding order a
Stan Hoeppner wrote:
Wayne put forth on 1/1/2010 8:56 AM:
http://www.intergate.com/~huntbrittany/linux/WICD.info.gz
If that data is accurate...
1. Your wired ethernet card is using 192.168.1.11
2. Your Atheros card is being assigned 192.168.1.3
The wired NIC is first in the binding order
Wayne put forth on 1/1/2010 8:56 AM:
http://www.intergate.com/~huntbrittany/linux/WICD.info.gz
If that data is accurate...
1. Your wired ethernet card is using 192.168.1.11
2. Your Atheros card is being assigned 192.168.1.3
The wired NIC is first in the binding order and thus first in the ro
Stan Hoeppner wrote:
Wayne put forth on 12/31/2009 10:18 PM:
Stan Hoeppner wrote:
Are you able to ping the IP address of the Windows laptop that is
properly
communicating with the MiFi?
]
No. I can ping the admin page (192.168.1.1) from the Laptop that is
running XP.
Please show output of
green wrote:
Stan Hoeppner wrote at 2009-12-30 21:04 -0600:
Wayne put forth on 12/30/2009 7:50 PM:
169.254.213.81 every time I get it connected.
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 understa
Stan Hoeppner wrote at 2009-12-30 21:04 -0600:
> Wayne put forth on 12/30/2009 7:50 PM:
> > 169.254.213.81 every time I get it connected.
>
> 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 th
Wayne put forth on 12/31/2009 10:18 PM:
> Stan Hoeppner wrote:
>> Are you able to ping the IP address of the Windows laptop that is
>> properly
>> communicating with the MiFi?
>> ]
>
> No. I can ping the admin page (192.168.1.1) from the Laptop that is
> running XP.
Please show output of ifconf
Stan Hoeppner wrote:
Are you able to ping the IP address of the Windows laptop that is properly
communicating with the MiFi?
]
No. I can ping the admin page (192.168.1.1) from the Laptop that is
running XP.
--
Stan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with
Are you able to ping the IP address of the Windows laptop that is properly
communicating with the MiFi?
--
Stan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Stan Hoeppner wrote:
Wayne put forth on 12/31/2009 7:57 PM:
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 RESUL
Wayne put forth on 12/31/2009 7:57 PM:
> 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 DISCONN
Original Message
Subject: Re: Getting connected to Verizon 3G network -UPDATE
Date: Thu, 31 Dec 2009 19:22:09 -0500
From: Wayne
To: debian-user@lists.debian.org
References: <4b3b7ecd.1080...@gmail.com> <20091230231525.ga9...@swansys>
<4b3bfca8.9030...@gmail
Original Message
Subject: Re: Getting connected to Verizon 3G network
Date: Thu, 31 Dec 2009 17:21:29 -0500
From: Wayne
To: debian-user@lists.debian.org
References: <4b3b7ecd.1080...@gmail.com> <20091230231525.ga9...@swansys>
<4b3bfca8.9030...@gmail.com&
Stan Hoeppner wrote:
Wayne 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 ser
Wayne 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 R
Wayne wrote:
green wrote:
Wayne wrote at 2009-12-30 10:24 -0600:
Brief history. I am now using a D-Link DWA-556 PciE card. It has
an Atheros AR5008 chip and I am using the mad-wifi ath5k driver
code. I can connect to the Verizon MiFi , using wicd, get a ip
address for the
ath0 interf
Wayne wrote at 2009-12-30 10:24 -0600:
> Brief history. I am now using a D-Link DWA-556 PciE card. It has an
> Atheros AR5008 chip and I am using the mad-wifi ath5k driver code. I
> can connect to the Verizon MiFi , using wicd, get a ip address for the
> ath0 interface, and stay connected
Hi guys
I an still working on getting connected to the 3G network. Actually
I am connected but I can't connect to the net.
Brief history. I am now using a D-Link DWA-556 PciE card. It has an
Atheros AR5008 chip and I am using the mad-wifi ath5k driver code. I
can connect to the Verizon
32 matches
Mail list logo
