Re: ral0 <--> wi0 (4.11) ?

Lystopad Oleksandr <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
 Hello, Sam Leffler!

On Tue, May 27, 2008 at 09:12:32AM -0700
[email protected] wrote about "Re: ral0 <--> wi0 (4.11) ?":
> Ian Smith wrote:
> >On Tue, 27 May 2008, Lystopad Oleksandr wrote:
> > > Hi!
> > >
> > > I need to build wireless link between FreeBSD 4.11 with wi0 (adhoc)
> > > interface and FreeBSD 7.0 with ral0 interface. I try many modes and
> > > mediaopts, but no luck. :(
> > > 
> > > Please, help me build wireless network with that environment.
> >
> >By omission, ral(4) implies that it won't do adhoc or hostap modes -
> >despite what ifconfig says below, perhaps what you told it? - so you
> >maybe can only use it in a BSS network, to an access point.  Boring.
> >  
> 
> ral should do ap mode and the driver claims to do ibss though I've not 
> tried it.  When in doubt
> 
> ifconfig ral0 list caps

I have two wireless nics on same host, I show two answers:

[root@pavilion /usr/home/laa]# ifconfig ral0 list caps
ral0=2181e500<IBSS,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,BGSCAN>
[root@pavilion /usr/home/laa]# ifconfig rum0 list caps
rum0=2181e500<IBSS,HOSTAP,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,BGSCAN>
[root@pavilion /usr/home/laa]#

 
> should show the supported operating modes (ifconfig -m ral0 on 7.x and 
> earlier).

Yes, it shows, but adhoc mode does not work with wi0 from FreeBSD 4.11 

> >That they both say 'associated' means they can 'see' each other, but
> >still have no common mode to talk in.  Been there, it's confusing ..
> >  
> 
> "associated" is a misnomer for anything but station mode.  In HEAD I 
> changed this status to say "running" for !sta mode.
> 
> To understand what's happening in 7.0 you can turn on debugging with 
> wlandebug and/or check the neighbor table with

[root@pavilion /usr/home/laa]# wlandebug -i rum0 scan+assoc+debug+input+output+state+dot1x
net.wlan.0.debug: 0x0 => 0x48ba0000<debug,input,assoc,scan,output,state,dot1x>
[root@pavilion /usr/home/laa]# wlandebug -i ral0 scan+assoc+debug+input+output+state+dot1x
net.wlan.1.debug: 0x0 => 0x48ba0000<debug,input,assoc,scan,output,state,dot1x>
[root@pavilion /usr/home/laa]#

> ifconfig ral0 list sta

[root@pavilion /usr/home/laa]# ifconfig ral0
ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:0f:66:74:8b:2b
        inet 192.168.126.2 netmask 0xfffffffc broadcast 192.168.126.3
        media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
        status: no carrier
        ssid 42bc9b channel 3 (2422 Mhz 11b)
        authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bgscan
        bgscanintvl 300 bgscanidle 250 roam:rssi11b 7 roam:rate11b 1
[root@pavilion /usr/home/laa]# ifconfig ral0 list sta
ifconfig: unable to get station information
[root@pavilion /usr/home/laa]#

> >Possibly the only way these two can talk is if your wi(4) card uses a
> >Prism chipset, and so may work in hostap mode.  Mine's a Cabletron with
> >Lucent chipset, which can't, but works fine in 11b adhoc or BSS modes. 
> >
> >Your best bet might be replacing one or the other with an Atheros card,
> >which can do all three of adhoc (IBSS), BSS client or hostap modes, so
> >should talk to either - or both, in hostap mode - of the others.
> >  
> Try getting some debug info.  It'd also be worth identifying which 
> ralink card is being used as the driver is actually a sandwich of N 
> drivers, one for each part, and each totally separate.
> 
>    Sam

My ral0 card is Linksys WMP54G, my rum0 card is 
rum0: <Ralink 802.11 bg WLAN, class 0/0, rev 2.00/0.01, addr 3> on uhub1

Both cant work with wi0 card from FreeBSD 4.11.

Please, help me to create adhoc network with any of wi0 (4.11), ral0 and 
rum0 on 7.0-STABLE. 

Thank you very much, Sam!!!

-- 
 Oleksandr Lystopad
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.