madwifi driver on NanoStation2

[bitbucket]

Which driver (hal platform) works on NS2 ? Packet receiving works with ap61 platform from madwifi, but card can't transmit. Or may be madwifi needs some tweaks, to get it work on NS2 ?

[physical]

tweaks are necessary, if i remember correctly, I got it to compile right using the mipsisa32-be-elf version. Never did check see if that worked... but if i remember correctly, I needed to change a bit in the .inc file to make it compile right...

I've been busy with other projects recently, its been a few months since I played with it...

[bitbucket]

tweaks are necessary, if i remember correctly, I got it to compile right using the mipsisa32-be-elf version. Never did check see if that worked... but if i remember correctly, I needed to change a bit in the .inc file to make it compile right...
I have no problems with compilation. I need to know, what I have to do in madwifi or hal to get TX working (antenna controll tweaking, smth else). RX works right with madwifi hal ap61.

[physical]

which HAL are you using to compile?

[bitbucket]

which HAL are you using to compile?
ap61 from madwifi, version 0.9.18.0, 0.9.30.13.

[hiwu.tw]

Atherso WiSOC need TX descriptor SWAP. If you use mipsisa32-be-elf directly, your TX descriptor is not SWAP. You have to add
"#define AH_NEED_DESC_SWAP 1"
to make TX work correctly.

[bitbucket]

Atherso WiSOC need TX descriptor SWAP. If you use mipsisa32-be-elf directly
I'm using ap61.o hal - AFAIK, all swaps have to be done in HAL, because on DLink DWL2100 with ap43 hal all works fine.
When I add TX desc swap, I get 'AHB fatall error'.

UPD: with HAL from AirOS SDK 3.2 all works: it needs to swap TX desc. But why Ubiquity not use this reg ?
#define AR5K_CFG 0x0014 /* Register Address */
#define AR5K_CFG_SWTD 0x00000001 /* Byte-swap TX descriptor (for big endian archs) */

[nomaad]

can anybody tell me what the commands are for changing DNS on an NS2 via telnet? And please don't just say that i can use madwifi commands. I cannot find them. I also need the specific commands for turning on WPA and changing the key.

[physical]

nomaad, you're a bit off topic...

But, here's your answer

you can change those values by editing your config file

you'll see entries similar to
resolv.status=enabled
resolv.nameserver.2.ip=192.168.1.1
resolv.nameserver.2.status=enabled
resolv.nameserver.1.status=enabled
resolv.nameserver.1.ip=192.168.1.2

just change the values, reset the unit and it'll propagate.
there are no madwifi commands to handle that sort of thing... typically, the nameservers are listed in a file /etc/resolv.conf which will have contents similar to
nameserver 192.168.1.1
nameserver 192.168.1.2

changing the contents of the file will change the nameservers that the machine will query when it gets an uncached DNS request.

if you want a quick and easy command like
changedns 192.168.1.1 192.168.1.2
sadly, no such command exists that I know of... but you could easily script one to update your config files, and even the resolv.conf file (if AirOS uses such a thing)

for WPA, again its something you edit in the config file... try using the GUI and setting various values, and see what changes, its the most scientific approach to such a thing.

[nomaad]

Thanks for the valuable info, I'm not sure how I managed to post that question where I did. I thought I was starting a fresh thread. Apologies.

I have a follow up question. Should I ask it here or start a new thread?

[physical]

If your question involves a NanoStation, then you should post in the NS forum...

[lostjlock]

Thanks for the info ! :)

[umfo2]

thanks) i'm shocked)