Hi,

It looks like that openwrt is based on wrt54gs gpl code version 2.07.1 released earlier this year. last month, linksys released the wrt54g version 2.04.4. Although the linux kernel is still 2.4.20, it adds quite a few things. Most noticablely, it has more protocol specific connection tracks in netfilter, e.g. SIP. It probably makes more sense to use this as the base.

Thanks,

Hi,

    I see that linksys has put the sources for their 2.09 firmware online <http://www.linksys.com/support/gpl.asp>.
It looks it has the 3.60 series wireless drivers in it.  What steps does one need to go through to switch over from 2.07?  I'm sure that some of the current patches to 2.07 will need tweaking.  Has anyone tried 2.09 code with openwrt yet?  Thanks.

--
Ajax

Seen it.

The 2.04 release shortly before also featured the exact same wireless driver. Support for wireless tools (iwconfig, etc) is in a separate file that's missing from the 2.09 release, at the very least this will break some startup scripts openwrt uses to detect the wireless interface.

The real question will be if there's any killer features that make the upgrade worthwhile.

Yes it is, this killer feature is ap_isolation. I just hacked 2.04.4 source into openwrt buildroot tree and compiled new firmware. Sad story, seems to that wireless extensions in wl driver are gone away.

One of Estonian wifi activist asks me to build firmware for WRT54G with two major features, wireless clients isolation (wl0_ap_isolate=1) and separate firewalled network for hotspot management sharing same uplink with wireless or wired customers. I realized this using another VLAN and set up another subnet using openwrt's standard ifup scripts. lan3_ifname=vlan3 etc..

One feature I love is SIP ALG (application layer gateway). It mangles the SIP messages and make voip phones behind NAT much easier.

Richard

is it true that there is some iptables module in the cooking for SIP ALG ? Don't know if it has been done yet.

It is not in kernel development yet, i believe. However linksys wrt54g ver 2.04.4 has its own implementation. That's why I suggest to use this as the code base.

A quick diff shows as a few dozens of new files are in wrt54g code.

Richard

Seems that some nvram settings does not work anymore. Example WEP. After wlconf eth1 up wep remains disabled. Only way turn wep on is using wl utility 'wl wep on' but currently this not works on centrino chipset.

I continue investigation

simple solution, not using wl0_ settings. wl_ settings works fine.

Q: It this related with wlconf ?

after nvram set wl_ifname=eth1 and wl0_ifname=eth1 everything works.

Does anybody happend to download the 2.09.1 source code? I just found it was a broken link, I guessed, and changed it to:

http://www.linksys.com/support/opensour … 1.etsi.tgz

and it is downloading.  I will take it a look too.

I tried to port the wl.o module from 2.04.4 source to OpenWrt. In fact I copy all the *.o files in the WRT54G/release/src/wl/linux/ directory of the new sources to the OpenWrt sources. I modified the /linux/linux/driver/net/wl/Makefile to include the new .o files and run make. But I had no success.
I don't know how to port this feature to the OpenWrt firmware. Can someone help me?

That's not porting at all. To port means to recode some part of some code to make it run on another environment. What you are trying is just to save a work that normally must be done. A kernel module needs some symbols that maybe are or ar not exported when it gets compiled. Those people at broadcom are releasing privative drivers that we do not know how they really work, though a lot of work could be done via reverse engeenering.

Try to focus on 3.17.4 -etsi and 'port' the 'new' 2.4.20 kernel + modules to the openwrt filesystem, that would be a better aproach.