Over the LAN? No.
--
Jack
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Wed, 4 Feb 2009 21:29:12 -0600
Jack wrote:
> As it would happen, the computer I'm currently using to write this
> email (along with several others in our house) are successfully
> connected to the router, though none others are running Linux.
> I think I may have to try a different wireless ad
As it would happen, the computer I'm currently using to write this
email (along with several others in our house) are successfully
connected to the router, though none others are running Linux.
I think I may have to try a different wireless adapter... thanks for
the help anyways though
--
Jack
On Wed, 4 Feb 2009 18:24:58 -0600
Jack wrote:
> Im not sure if there's a better way to test the connection on port 80,
> or even if this method will do that, but I tried:
> wget 192.168.2.1:80
>
> which hung on "Connecting to 192.168.2.1:80..."
>
> So I don't think anything is getting through o
Im not sure if there's a better way to test the connection on port 80,
or even if this method will do that, but I tried:
wget 192.168.2.1:80
which hung on "Connecting to 192.168.2.1:80..."
So I don't think anything is getting through on port 80 either
--
Jack
--
To UNSUBSCRIBE, email to deb
On Tue, 3 Feb 2009, Jack wrote:
> As for /etc/network/interfaces, I have attempted inserting
>
> auto wlan0
> iface wlan0 inet static
> address 192.168.2.138
> netmask 255.255.255.0
> gateway 192.168.2.1
>
> However, this results in the same problems as I am having. So
> currently, I have /etc/net
On Tue, 3 Feb 2009 22:53:19 -0600
Jack wrote:
> Right. As suggested, I manually added my router to the ARP table.
> Pinging the gateway now results with:
>
> PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
>
> --- 192.168.2.1 ping statistics ---
> 4 packets transmitted, 0 received, 100% pa
Right. As suggested, I manually added my router to the ARP table.
Pinging the gateway now results with:
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
--- 192.168.2.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3009ms
So perhaps the host in not unreachable
arp:
Address HWtype HWaddress Flags MaskIface
192.168.2.1 (incomplete) wlan0
--
Jack
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
On Tue, 3 Feb 2009 22:22:47 -0600
Jack wrote:
[Please reply only to the list, as per the code of conduct.]
> arp:
> Address HWtype HWaddress Flags Mask
> Iface
> 192.168.2.1 (incomplete)
> wlan0
Ok, so ar
To recap, pinging the gateway results in the following:
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
>From 192.168.2.138 icmp_seq=1 Destination Host Unreachable
>From 192.168.2.138 icmp_seq=2 Destination Host Unreachable
>From 192.168.2.138 icmp_seq=3 Destination Host Unreachable
>From 192.
On Tue, 3 Feb 2009 22:07:24 -0600
Jack wrote:
> To recap, pinging the gateway results in the following:
> PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
> From 192.168.2.138 icmp_seq=1 Destination Host Unreachable
> From 192.168.2.138 icmp_seq=2 Destination Host Unreachable
> From 192.168.2
On Tue, 3 Feb 2009 21:50:39 -0600
Jack wrote:
[Please respond on list.]
> ifconfig wlan0:
>
> wlan0 Link encap:Ethernet HWaddr 00:0F:B5:62:BD:27
> inet addr:192.168.2.138 Bcast:192.168.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
On Tue, 3 Feb 2009 17:14:23 -0600
Jack wrote:
> iwconfig wlan0:
>
> wlan0 IEEE 802.11g ESSID:"WEINSTEIN" Nickname:""
> Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:5B:0D:DC
> Bit Rate:24 Mb/s Tx-Power:18 dBm Sensitivity=1/1
> Retry:off RTS t
iwconfig wlan0:
wlan0 IEEE 802.11g ESSID:"WEINSTEIN" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:5B:0D:DC
Bit Rate:24 Mb/s Tx-Power:18 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:864E-3FBC
On Tuesday 03 February 2009 05:34:51 Celejar wrote:
> On Mon, 2 Feb 2009 22:13:46 -0600
>
> Jack wrote:
> > ifconfig wlan0 192.168.2.138 up
> > iwconfig wlan0 essid "" key
> > route add default gw 192.168.2.1
>
> At this point, what is the output of 'iwconfig wlan0'?
>
> Celejar
> --
And can you
On Mon, 2 Feb 2009 22:13:46 -0600
Jack wrote:
> I recently installed a base-install of Debian linux on an old laptop.
> I have a netgear WG511T wifi pci card, which I was successful in
> installing the madwifi drivers for. I'm almost certain that the
> drivers are working fine, because I am able
17 matches
Mail list logo
