OpenWrt Forum Archive

Topic: ad-hoc mode speed test.

The content of this topic has been archived on 29 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I have a kamikaze 7.07 running on a IXP422/5 machine and a AUSU router WL-500g running white russian.
I have two different settings to compare the speed.
Option 1: Asus WL-500g as an AP, and Kamikaze 7.07 as a sta (client) mode.
Option 2: Both run at ad-hoc mode.

And ping from one machine to another to test wireless link speed;

get result:

Option 1: Reply from 192.168.1.1 bytes=1500 time = 7ms TTL=64;
Option 2: Reply from 192.168.1.1 bytes=1500 time = 133ms TTL=64;

Why ad-hoc mode takes about 20 times (133ms vs 7 ms) longer?

Any comments on it?

I have the same problem when I use my Kamikaze Linksys WRT54GS v1.1 in client ad-hoc mode. The performance are really bad!

Thanks for the link!!!!!
Now the performances for adhoc are normal
Davide

What have you done to improve it? Just did not bridge Lan and WAN


davide_lenza wrote:

Thanks for the link!!!!!
Now the performances for adhoc are normal
Davide

I have created a new network.
I have bridged the wifi with this new network
I have launched the command found into the link.
Davide

Would you be able to post your codes here and share with us please?

Thanks.


davide_lenza wrote:

I have created a new network.
I have bridged the wifi with this new network
I have launched the command found into the link.
Davide

(Last edited by phuang on 23 Nov 2007, 16:34)

Sure. Here's the config files.
Davide


/etc/config/network

#### VLAN configuration
config switch eth0
       option vlan0    "1 2 3 4 5*"
       option vlan1    '0 5*'


#### Loopback configuration
config interface loopback
       option ifname   "lo"
       option proto    static
       option ipaddr   127.0.0.1
       option netmask  255.0.0.0


#### LAN configuration
config interface lan
       option type     bridge
       option ifname   "eth0.0"
       option proto    static
       option ipaddr   '192.168.2.1'
       option netmask  255.255.255.0

#### WIFI configuration
config interface wifi
       option type     bridge
       option ifname   "wl0"
       option proto    static
       option ipaddr   '192.168.3.1'
       option netmask  255.255.255.0
       option dns      '85.37.17.42'

#### WAN configuration
config interface        wan
       option ifname   "eth0.1"
       option proto    'dhcp'
       option ipaddr   ''
       option netmask  ''
       option gateway  ''


/etc/config/wireless


config wifi-device  wl0
       option type     broadcom
       option channel  5
       option disabled '0'
       option distance ''

       # REMOVE THIS LINE TO ENABLE WIFI:

config wifi-iface
       option device   wl0
       option network  wifi
       option mode     'adhoc'
       option ssid     'pippo'
       option encryption       'none'
       option hidden   '0'
       option isolate  '0'
       option bgscan   '0'
       option wds      '0'
       option key      '0'



/etc/init.d/custom-user-startup

#!/bin/sh /etc/rc.common
START=90
# place your own startup commands here
#
# REMEMBER: You *MUST* place an '&' after launching programs you
#   that are to continue running in the background.
#
#   i.e.
#   BAD:  upnpd
#   GOOD: upnpd &
#
# Failure to do this will result in the startup process halting
# on this file and the diagnostic light remaining on (at least
# for WRT54G(s) models).
#
iptables -I forwarding_rule -j ACCEPT

The discussion might have continued from here.