Hi everyone. I managed to get OpenWRT (kamikaze 8.09) to work on a Linksys WAG54G v2, after making the changes to the cpmac.c file as mentioned in this page https://dev.openwrt.org/ticket/3923.

Now, I would like to know how I can get PPPoE to work. ADSL seems to be working fine. Just need some instructions on how to get PPPoE to work.

I would also like to know how to fix the LEDs since they are not working correctly. After the firmware boots, the power LED is supposed to be steady green, but instead it blinks red and green. The ethernet LEDs are working fine and so is the DSL LED. But the Wifi and "Internet" LEDs aren't working.

Someone, please provide me instructions on how to get PPPoE to work and also how to fix the LEDs.

Thanks in advance.

Wow, just after posting this I managed to get PPPoE working after checking settings listed on many different pages on this site. My final configuration that worked is the following.

config 'atm-bridge'
        option 'unit'   '0'
        option 'encaps' 'llc'
        option 'vpi'    '0'
        option 'vci'    '32'
        option 'payload' 'bridged'

config 'interface' 'wan'
        option 'ifname'         'nas0'
        option 'peerdns'        '1'
        option 'defaultroute'   '1'
        option 'proto'          'pppoe'
        option 'username'       'xxxxxx'
        option 'password'       'xxxxxx'
        option 'keepalive'      '10'

Now I just need to know how to fix the LEDs and also how to get WPA2 to work. When I select encryption as "psk2" in /etc/config/wireless, it just appears unsecured. WEP is working fine though.

I just successfully installed X-WRT! And I also just found out that the acx driver doesn't support WPA/WPA2 PSK.

Anyway, I would now just like to know how to fix the LEDs. Can anyone help me with that? Thanks.

Hello! Have you configured the switch succesfully? what changes did you make to get a fully working openwrt over WAG54Gv2?
I have built my own openwrt image from an upper 16049 revision of svn without success.

Any recommendation?

Thank you.

Its not "fully" working. I later found out that the wireless wasn't working properly. I could see it in the list of available networks and could even connect to it if i leave encryption disabled but after that nothing. Couldn't ping the router or do anything else.

To get the switch to work, I had to make changes to the cpmac.c file as mentioned here --> https://dev.openwrt.org/ticket/3923

What release did you build with those changes?

Are you guys aware of this open project (pluto)?

http://sourceforge.net/projects/project-pluto/

It works really well for me for 2 years+

If you want open-wrt, there may be some good stuff in it for you.  Beware the POTS (modem) config in pluto though- it may not be right as it was specific to the Australian PSTN as that is where it was mainly tested.

I reckon there should be a link on the OpenWRT wiki WAG54g page  to that to that project.

(Last edited by plutonium on 17 Oct 2009, 01:23)

Hello everybody,

First i want to apology for my poor english.

I compiled the last version (kamikaze 8.09), but i am not sure of waht setting i need to use, to be able to flash my WAG54g v2.
I use the AR7 setting and i tried to be very close of all recommandation, but my WAG54g v2 always said "Wrong pattern" when i tried to send it with the tftp method.

ashketchum how did you managed to get OpenWRT to work on a Linksys WAG54G v2 ?
When you successfully compiled your OpenWRT which .bin file did you use ? There are so many, but never the right name device

Thanks a lot for all your idea and your help

Regards,

Hello everybody,

I successfully compiled the last trunk of (kamikaze 8.09)
I make changes to the cpmac.c file as mentioned here --> https://dev.openwrt.org/ticket/3923
I flash my WAG54G v2 with tftp method.

But now my wag54G is doing circle, He is starting again and again every minutes. I saw every minutes 4 ping successfull

I don't know wich setting i need to check in the make menuconfig section.

Does anybody can help me ?

Best Regards

The code pattern for WAG54G V2 is WA22 that's why you have to use openwrt-WA22-squashfs-code.bin or openwrt-WA22-jffs2-64k-code.bin file.

I think first try flash from here http://downloads.openwrt.org/kamikaze/8.09.1/ar7/

I played with a WAG54G V2 too but no succes with any other firmware than the original
My problem is the switch.It isn't working with openwrt maybe a bug or something missing etc. driver patch etc...I can't find the solution....

Could you write step by step how to make changes to the cpmac.c file ?

Thanks

Hi guys,

I have an European (UK) version of WAG54G V2, when uploading WA22 firmware it says: "Error code 4: Wrong Code Pattern", but when uploading WA21 it uploads successfully.

The problem is when firmware upload is done, it keeps blinking green (for about 30 seconds), then blinks once red, and then starts again blinking green (for about 30 seconds) and then blinks once red, and so on.

With other WA21 firmwares it blinks green for those 30 seconds, and then blinks insanely green-red.

With openwrt-WA22-jffs2-64k-code.bin from http://downloads.openwrt.org/kamikaze/8.09.1/ar7/ it actually works the best: the firmware loads, then blinks for 30 seconds green, then once red, seems to reboot, and blinks infinitely green. After that I'm able to ping it! But nmap 192.168.1.1 shows the host is down. Wifi

I tried to build my own image from SVN trunk, I used the resulting WA21 *.bin files, but after uploading them, router didn't even respond to pings. It's doing the blinking-green-for-30-secs-once-red-and-again loop.

Also, I'm not sure what's the real status of this bug: https://dev.openwrt.org/ticket/3923 . At that page it says it's closed, so do I have to patch the cpmac.c when using trunk or not?

I'm always flashing the  using tftp method after reboot. (When using "upload firmware" from web interface it just says "Upload failed" after about 5 seconds of upload).

I really want to get this router working with shell access. I don't even care the ADSL feature, I just want a nice ethernet-wifi bridge with cli access (and stuff like iptables).

I would be really happy if someone shares ANY working openwrt firmware for that device ;-).

(Last edited by Gabrys on 2 Feb 2010, 15:19)

Hello guy,

I think I have a WAG54Gv2-EU as yours. The unique code pattern that works for me is WA21. Builds after 8.09.1 works better and they have some patches applied related to ticket #3124. I had to rebuild it to add "cpmac.dumb_switch=1" option to the kernel command line to get the switch working.

However my adsl modem can't sync in routed mode. I've rebuilt older "working" versions without success. I don't know if is a hardware problem and I haven't tried anymore.

You can collaborate with the wiki page for this device if you consider. All will thank you.

http://nuwiki.openwrt.org/inbox/wag54g

(Last edited by SiNiESTrO on 2 Feb 2010, 21:44)

I have just tested my own build of 8.09.2 kamikaze with patched cpmac.Still cant get to work with acx100 driver.
shows me "auth algorithm mismatch: our:1 peer:0" in wep and wlan0: tx error 0x20, buf 06! (and so on) with no wep
can anyone could share his build ?
BTW. mine -EU version is WA21 code pattern.

(Last edited by nicefile on 28 Feb 2010, 00:05)

@Gabrys

In my case when it blinked red and green it meant that it had finished booting. After that I was able to log in to the router with SSH.

I managed to get wired lan and pppoe working and so was able to browse the web with it but since wireless lan was not working, I couldn't continue to use it.

Anyway, my WAG54G v2's switch stopped working a few months ago and I bought a WAG54G2 to replace it. The latset official firmware still has some bugs. For example UPnP doesn't work properly. Ports cannot be forwarded automatically using UPnP. So I can't recommend it.

@nicefile

I made the modifications to cpmac.c file ( as mentioned on the second post here - https://dev.openwrt.org/ticket/3923 ) to get the ethernet to work. Didn't manage to get wireless lan to work. Mine was the EU version also. And I also had the code pattern problem initially. I figured out the correct pattern by trying to upload all of the precompiled firmwares one by one.