I just got a Linksys WMP11 Wireless PCI Card and a Linksys WAP11
Access point. I have it working fine, but I can't figure out how to
make the configuration permanent. I'm using iwconfig from the
wireless-tools package to configure the wireless aspects of it (ssid,
encryption key,
"jcoppock1" == jcoppock1 writes:
jcoppock1> I just got a Linksys WMP11 Wireless PCI Card and a
jcoppock1> Linksys WAP11 Access point. I have it working fine,
jcoppock1> but I can't figure out how to make the configuration
jcoppock1> permanent.
Shyamal Prasad, 2002-Sep-27 17:32 -0500:
> It's been a while since I've done this, but with Debian you can put
> the entries in /etc/network/interfaces. Something like this works for
> me on eth1 (my PCMCIA wireless device):
>
> iface eth1 inet dhcp
> wireless_ess
Hi,
I'm plannig to buy a wireless access point and a
wireless PCMCIA network card. Both should work under Debian.
The nearest local store sells these:
http://www.trendware.com/products/TEW-301PC.htm
http://www.trendware.com/products/TEW-310APB.htm
Does anyone have experience with these
On Thu, Aug 29, 2002 at 04:17:41PM -0700, Rupa Schomaker wrote:
> I have a 1000AP and newer versions of it's firmware sport a web
> interface to configure the device.
Yes, and it works well. I have one. The problem is that you have to be
able to FIND the unit in order to configure it, and it co
On Thu, Aug 29, 2002 at 04:17:41PM -0700, Rupa Schomaker wrote:
> I have a 1000AP...
Were you also aware that it has a possible SNMP compromise? Search for
"D-Link DWL-1000AP can be compromised because of SNMP configuration" in the
BugTraq archives.
Basically, the admin password of the unit is
On Sun, 1 Sep 2002 17:59:05 -0700
Marc Wilson <[EMAIL PROTECTED]> wrote:
> Yes, and it works well. I have one. The problem is that you have to be
> able to FIND the unit in order to configure it, and it comes up using
> DHCP to get its IP address. I usually arp for it... I know its MAC
> prefi
On Sun, Sep 01, 2002 at 09:51:03PM -0500, Jamin W. Collins wrote:
> Why not just assign it a fixed IP via DHCP? Works beautifully here.
Pass me the stupid hat. I quite frankly never thought of doing that.
(/me goes and beats on the DHCP server)
--
Marc Wilson
[EMAIL PROTECTED]
--
To UNSUB
On Sat, Oct 12, 2002 at 11:54:09PM -0400, James Hughes wrote:
> I have PCIC=i82365, which, again, works. Can you explain why
> yenta_socket is the better option?
Based on your previously supplied output, it doesn't appear to be
working. I say this because the ds.o module fails to load claiming t
James Hughes wrote:
> On Sat, Oct 12, 2002 at 10:08:36PM -0500, Jamin W. Collins wrote:
> Sorry, should have noted in previous mail, but...
>
>>I'm no expert, but I believe this is because you don't have a socket
>>driver loaded. Based on the kernel listed in your output, you should
>>probably b
s situation very well. Here is
output from lsmod, immediately after logging in (before I run my hack
script that gets the wireless card working):
prism2_cs 57008 1
pcnet_cs 12704 1
83906384 0 [pcnet_cs]
ds 6632 2 [pris
On Tue, 15 Oct 2002 07:39:28 -0400 James Hughes <[EMAIL PROTECTED]> wrote:
> As you can see, all the elements are there for things to work:
I'll accept that.
> # Aliases to tell insmod/modprobe which module to use when bringing up
> # the wlan0 interface.
> alias wlan0 prism2_cs
>
> So, why is
On Tue, Oct 15, 2002 at 07:10:16AM -0500, Jamin W. Collins wrote:
>
> It may be that the system is trying to load the prism2_cs module to bring
> up the interface, which in turn trys to load the ds module, prior to
> pcmcia service being started. Do you have wlan0 in /etc/network/interfaces
> con
13 matches
Mail list logo