Hello list!

I use a WRT54GL v1.1 with the RC5 firmware and I have a question...

My WRT is automaticly generating new unique cell-IDs - random every 6 seconds!

What is wrong with mit WRT? This can not be reliable!

Here is an report from iwconfig:

eth1      IEEE 802.11-DS  ESSID:"rsm-hotspot-olsr"
          Mode:Ad-Hoc  Frequency:2.432 GHz  Cell: 3A:CD:1C:A7:1C:C7
          Tx-Power:19 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off

eth1      IEEE 802.11-DS  ESSID:"rsm-hotspot-olsr"
          Mode:Ad-Hoc  Frequency:2.432 GHz  Cell: C6:EE:48:27:70:8B
          Tx-Power:19 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off

eth1      IEEE 802.11-DS  ESSID:"rsm-hotspot-olsr"
          Mode:Ad-Hoc  Frequency:2.432 GHz  Cell: C6:EE:48:27:70:8B
          Tx-Power:19 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off

i took a look to my NetStumbler, my accesspoint was listed lots of hundred times!

Thank you very much in future.

Kind regards,
Michael Rack
Germany

AFAIK this is the normal behavior until at least two nodes form a cell.

How did you do that? I always wanted to make an OpenWRT "FakeAP".

Sorry, but i don´t understand this I'm so sorry - i'm confused!

the pings from my notebook to the WRT54GL router are higher then 100ms! What can it be?

My pings look like this:

Antwort von 10.200.0.100: Bytes=32 Zeit=3ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=2ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=3ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=3ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=2ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=1210ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=47ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=2ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=14ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=3ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=2ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=1036ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=55ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=4ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=4ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=4ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=4ms TTL=64
Zeitüberschreitung der Anforderung.
Antwort von 10.200.0.100: Bytes=32 Zeit=396ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=5ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=3ms TTL=64
Antwort von 10.200.0.100: Bytes=32 Zeit=3ms TTL=64

I think these high pings are results of the dynamic changing of the CELL ID?!?

My Notebook is paired with the SSID rsm-hotspot-olsr on Channel 5 - 2.432 GHz and is operating in Ad-Hoc Mode.

Netstumbler shows the following:
http://www.rsm-freilassing.de/netstumbler.png

I think this can not be correct!

@star882: Don´t ask me i'm very afraid that my WRT is generating faked Cell IDs.

(Last edited by RcRaCk2k on 31 Aug 2006, 21:54)

I had a similar experience when I messed around with a WA840G (that was before I knew about OpenWRT) trying to make it into a client. I tried to just change the mode from "AP" to "sta" in the CFE. It then went into adhoc mode and showed up several times on Netstumbler. It was interesting but not very useful.
Just try using it as a normal AP. But that isn't terribly useful for mesh networking, so I hope someone figures out how to get adhoc to work.

Tomorrow i will setup a little test-connection beetween two Windows XP running Clients, starting both wireless-interfaces in Ad-Hoc mode and watch to the 802.11 available cells by Netstumbler.

I'm very anxious to see the results while the first Ad-Hoc running client is waiting for an node to be connected.

Hi!

Few minutes ago, the tests were successfully completed.

Microsoft Windows XP creates only one CellID when the wireless LAN Adapter is running in the AdHoc mode.

My secondary notebook was scanning for new beacons every 4 seconds. Windows doesn't change the CellID along 10 minutes!

Anything on my WRT have to be wrong in the configuration!

How can i make the CellID static?

Can anyone create a setup of an WRT in Ad-Hoc mode, and send a screenshot of the scan results from a Netstumbler?

(Last edited by RcRaCk2k on 1 Sep 2006, 09:42)