[wisp-dist] can't get bridging working on build 2546
layer 2 bridging ... I see WDS interfaces show up but no connections or
traffic transfer
layer 3 bridging ... Not all the IP's make it into the arp table thus some
devices can talk across the bridge, others can't
Are there any known issues
We have found the Dlink900AP+ does not work as a station mode. The 900AP
did work if you cloned the MAC address from the 900AP on the NIC.
the 900+ uses a different chip set and firmware than the 900.
We also found the 900APs to lock up. Out of about 10 of them, we had 3 to
5 of them locking
: Vladimir I. [EMAIL PROTECTED]
To: wispdist [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, February 27, 2003 2:27 AM
Subject: Re: [leaf-user] wisp-dist - has anyone used the vtun features?
I do use them. :-)
The default vtun configuration in the latest images shows how to
bridging
I found that the zebra ripd only sends out routing info referencing the
source as the primary address / subnet on the interface it is running on.
therefore, if you connect two routers running just the ripd and they are
connected to each other on a subnet that is a secondary subnet on both
I will try the new release today or tomorrow.
I am trying to have the mail procedure in the POSIXness script send me an
email via the cron .
If I run mail from the command shell or directly from a script it works
fine. but when it is run in a script that is run by cron it does not.
I
I am still having problems with the zebra routing even when only using ripd
Does anyone know if there are issues with using more than one IP address per
interface. Does this confuse the routing software?
I had one unit that when assigned on one subnet, the routes propagated fine
but when I
I have build 2516 installed on two routers now and have found the wavemon
seems to be broken.
I get the following error
fatal error: could not get range information
let me know when this gets fixed and / or how to fix it.
thanx
J.
---
This
I am currently using the soekris two slot boards and when I run two radio
cards at once I see two problems.
1. sometimes I get the following error in the /var/log/messages
Feb 5 15:16:10 HiGu{GeRh}-GaGr-OrCo-Ca-bsr0-AP1 kernel: netcs1:
prism2_interrupt: hw not ready; skipping events 0x8000
Feb
I have been having some routing issues. I switched from ospfd to ripd
(wisp-dist bld 2348) and the routing stabilized.
however, I just put a couple routers on with build 2397 and started having
routes drop out again.
I found that the routers with 2397 on them were not communicating any routes
Are there any PCI wlan cards ( integrated as opposed to a pcmcia socket that
you still have to plug a radio card into ) that are supported by wisp-dist
in AP mode?
I tried the d-link dwl-520 and it worked using the host-plx driver but
infrastructure only. no AP support.
I am running build 2397 on some of our routers now. I have noticed that I
cannot ping them. They do not respond to a ping. I can ping from them and
through them though.
Anyone else seen this?
---
This SF.NET email is sponsored by:
I am running wisp-dist release 2002-09-21(2348)
I have been running the ospfd with zebra and it seemed to start out working
fine. however, over time one of the units will drop all learned routes and
all other routers on the system lose the learned routes from that router as
well.
usually if I
Where would I start if I wanted the client/station to attempt to find an AP to connect
to
from a list of several possible essid's?
I would have it try the first essid. If no connection then try the next one in the
list and
so on.
---
wisp-dist: The /proc/net/prism2/wlan device is duplicate when using
two wlan cards
On build 2341 - I have installed two wlan cards ( TT 100mW ) and
when I go to the /proc/net/prism2 directory, I find two 'wlan0' entries.
I am thinking it should show a wlan0 and a wlan1.
Is this a bug or am
wisp-dist: The /proc/net/prism2/wlan device is duplicate when using two wlan cards
On build 2341 - I have installed two wlan cards ( TT 100mW ) and when I go to the
/proc/net/prism2 directory, I find two 'wlan0' entries. I am thinking it should show
a
wlan0 and a wlan1.
Is this a bug or am
I have set up an two wisp-dists ... one as AP and one As Client ( managed mode ).
I double checked all the routes and subnets
the AP shows active association of the client.
The client shows association to the AP
I run tcpdump -i netcs0 and can see the AP is hearing the client but the client is
I have determined it is specifically build (2324) that is giving me the problem.
with build 2312 the AP mode worked. with build 2324 it did not ( I could not get any
cards including a lucent silver card to connect to the AP )
I created an .img and burned to flash with the latest build 2341
wisp-dist build 2312
I have loaded the 2312 flash image on the new TT board and also on the Soekris
board. I am using the new 100mW higher power card.
They pass traffic in infrastructure / client mode but not in AP mode. If I use
station-
server or TT firmware for AP, the wisp-dist
I am experiencing this ... When the wisp-dist is in AP mode, both the client and the
AP show they are associated. When I ping the AP from the laptop ( client ) The
Access Point Statistics for wlan0: show it is receiving the ping pkts, but are not
transmitting
eg.
xx:xx:xx:xx:xx:xx ():
19 matches
Mail list logo
