The firmware mentioned in the guide is compatible with WRT54G v2.2, but maybe not with newer versions. But I'm sure you can find a newer version of the sveasoft firmware which is compatible with your new v5 wrt54g. I have a v2.2 wrt54g working as a client to d-link di-624+ and the setup is working great. Other people mentioned they got v3 wrt54g to work, but I haven't yet heard of people using v5 wrt54g. But again, I'm sure there are firmware versions compatible with this new model.
hmm .... I found something .... that isn't encouraging :
Link : http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=9209
Date : oct 12, 2005
I guess I am sc##d.
Link : http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=9209
Date : oct 12, 2005
I guess I am sc##d.
maybe you could exchange your newly acuired v5 wrt54g for a v2.2 or v3 ?
The reason there are 3rd party firmwares is that these versions are based on linux and their original linksys firmware is open source. But I guess the new v5 is not linux based and is not open source, so it's basically a blackbox just like any other router on the market.
The reason there are 3rd party firmwares is that these versions are based on linux and their original linksys firmware is open source. But I guess the new v5 is not linux based and is not open source, so it's basically a blackbox just like any other router on the market.
Hi ! What I needed from my wrt54 was that to act like a complete transparent bridge , but connected to a AP .
In V23 Firmware (alpha) I have that acomplished with one big inconvenience :
It does something with the MAC addresses from computers conected to the WRT directly by cable . So, from wireless , I can see only one MAC address for all the computers conected to the LAN ports of the WRT .
It does a kind of MAC proxy (or MAC-NAT
) I guess ...
Does anyone knows if it's possible to get my WRT running exactly like a switch does on the ethernet ?
Stuff like D-Link DWL-2000 and others , does this by default running in Client mode.
In V23 Firmware (alpha) I have that acomplished with one big inconvenience :
It does something with the MAC addresses from computers conected to the WRT directly by cable . So, from wireless , I can see only one MAC address for all the computers conected to the LAN ports of the WRT .
It does a kind of MAC proxy (or MAC-NAT
) I guess ... Does anyone knows if it's possible to get my WRT running exactly like a switch does on the ethernet ?
Stuff like D-Link DWL-2000 and others , does this by default running in Client mode.
Didly squat, my main router is a WAG54G V2 and doesn't support CLI through Telnet only web-based GUI.
How to complete step 10?
How to complete step 10?
step 10 is done on the client router - the wrt54g with the alchemy firmware. So first complete this step.
Then, To set up port forwarding to any machine on your local network, you only need to use your main router's web interface and specifiy the port and IP address of the machine you want to forward to. This should work for any of your machines machines, wether they are attached to the main router or the client router.
:music:
Great router
Great firmware
Great application
I had been searching for this solution for a long time.
Installing the firmware took me 2 hours, the rest only 5 minutes.
Thanks !
Great router
Great firmware
Great application
I had been searching for this solution for a long time.
Installing the firmware took me 2 hours, the rest only 5 minutes.
Thanks !
I followed all the steps 1-9 and sucessfully connected my WRT54 G V2.0. The only thing that does not work is logging in via Telnet or SSH. The router password does not work. Any ideas?
Ipontific8 -- sure need to have this working:-(
Ipontific8 -- sure need to have this working:-(
make sure that telnet and SSHD are enabled in Administration->Management screen. Log in username is "root", password is "admin" or whatever you changed it to (same as the web interface)
awesome! i didin't type the username root - was using the router username. duh! Thanks for helping me through this spot!
ipontific8
ipontific8
Return it. Ask for Version 4 or older.
Version 5 uses VxWorks Operating System, NOT LINUX! (like the older models)
This is why you cannot update the firmware.
Its the same for WRT54GS model, DO NOT BUY THE LATEST ONE!
(If you want to use third-party firmware!)
Linksys is well aware of enthusiasts wanting to install custom firmware with their Linux
based routers, so to cater for that market, Linksys will introduce WRT54GL
=> The L = Linux
It will have large RAM and Flash RAM storage.
^^^ oh man , I tohught my V2.2 will become a collectors item so I could sell it on ebay for $200......
I bought my second belkin(F5D7230-4) 5 months ago but never succeeded to make the 2 belkin working in this way. (tried to configure wireless bridge and worked but PCs connected to 2nd belkin can't go online. I must missed something) so this 2nd belking has been sitting there in the dust all these days.
After google and found this thread today, i tried again. worked immediately! no any change about subnet mask or gateway in the wireless bridge belkin. so i don't need to worry about the PC communication between 2 different subnet.
and yes! one of the best thing
the belkin(F5D7230-4) is $10-20 each after rebate.
I am so happy now. finally i fixed this long-existing problem and i am watching video from my livinging room computer and LCD TV.
After google and found this thread today, i tried again. worked immediately! no any change about subnet mask or gateway in the wireless bridge belkin. so i don't need to worry about the PC communication between 2 different subnet.
and yes! one of the best thing
the belkin(F5D7230-4) is $10-20 each after rebate.
I am so happy now. finally i fixed this long-existing problem and i am watching video from my livinging room computer and LCD TV.
I have a question on getting this to work on my setup. Currently my set up is as follows:
Room 1: Cable Modem <====> BEFSR41 <===> WAP54G and PC 1
Room 2: WRT54G <===> PC2, PC3, PC4
Settings as follows:
BEFSR41:
IP: 192.168.1.1
Gateway: 255.255.255.0
IP Range 192.168.1.100 to 192.168.1.199
Set as local DHCP server
WAP54G:
IP: 192.168.1.245
Subnet: 255.255.255.0
Gateway: 192.168.1.1
SSID broadcast enabled, 128bit WEP security
No MAC addres filters
WRT54G:
Firmware upgrade to Free-man/basic 1.0.4
Device is V3.1
IP: 192.168.1.225
Subnet: 255.255.255.224
Gateway: 192.168.1.1
SSID matches
Wireless mode is Client-bridge
WEP key entered correctly
Set as DHCP server
Problem is no connection to the WAP54G device which i think is due to my lack of understanding on how to customize the settings to my network set up. If you could shed some light on what changes i need it would be greatly appreciated.
Thanks in advance
Room 1: Cable Modem <====> BEFSR41 <===> WAP54G and PC 1
Room 2: WRT54G <===> PC2, PC3, PC4
Settings as follows:
BEFSR41:
IP: 192.168.1.1
Gateway: 255.255.255.0
IP Range 192.168.1.100 to 192.168.1.199
Set as local DHCP server
WAP54G:
IP: 192.168.1.245
Subnet: 255.255.255.0
Gateway: 192.168.1.1
SSID broadcast enabled, 128bit WEP security
No MAC addres filters
WRT54G:
Firmware upgrade to Free-man/basic 1.0.4
Device is V3.1
IP: 192.168.1.225
Subnet: 255.255.255.224
Gateway: 192.168.1.1
SSID matches
Wireless mode is Client-bridge
WEP key entered correctly
Set as DHCP server
Problem is no connection to the WAP54G device which i think is due to my lack of understanding on how to customize the settings to my network set up. If you could shed some light on what changes i need it would be greatly appreciated.
Thanks in advance
user 1234...Thanks for the info on a great project! What additional steps would be needed to configure the AP(main wireless router) behind a wired router. (the AP will be located a distance from the cable modem, router, and pc and connected via cat5)
I am creating a 1 mile wireless link using 2 WRT54G routers. #1 in AP mode and #2 in client mode. There will be multiple PCs connected to #2 clientmode router. The purpose is for internet sharing only. No file sharing between locations.
The #1 AP router is connected to an external antenna and is mounted outside. The cable modem and wired router are inside near the PC. The wired router IP 192.168.2.1
Any help on the configuration of the 3 routers would be greatly appreciated.
I am creating a 1 mile wireless link using 2 WRT54G routers. #1 in AP mode and #2 in client mode. There will be multiple PCs connected to #2 clientmode router. The purpose is for internet sharing only. No file sharing between locations.
The #1 AP router is connected to an external antenna and is mounted outside. The cable modem and wired router are inside near the PC. The wired router IP 192.168.2.1
Any help on the configuration of the 3 routers would be greatly appreciated.
I have set this up and it works great. However I can only connect to the Internet through my wired network on the bridged side. I can connect trhough wifi but only directly to the Router.
Is there any way to connect to the bridge wirelessly? Thanks!
Is there any way to connect to the bridge wirelessly? Thanks!
No thst's not possible with this setup. Only WDS mode can do that but that requires completely different setup and compatible routers.
What firmware have you guys used? I am using DD-WRT and it has been great so far. What steps are you guys taking to secure your bridged connection? DD-WRT only supports WEP in bridged mode, no WPA. Does MAC filtering work with a bridged setup? Thanks
Any other ideas on what is the best secure method for this connection type would be greatly appreciated.
Any other ideas on what is the best secure method for this connection type would be greatly appreciated.
I set my wrt54g and wrt54gs through WDS so i could hookup my voip/xbox360/xbox to the internet in my room. But from what i have read WDS cuts the wireless transmission in half so would i be better off setting it up like the setup in this thread since im going to be only hooking up clients wired to the bridged router anyways.
two disadvantages to using WDS are:
*
Wireless throughput is cut approximately in half for each WDS repeating "hop", i.e. an AP that data flows through before hitting the wired network. This is because all transmissions use the same channel and radio and must be retransmitted to reach the wired LAN.
* Dynamically assigned and rotated encryption keys are not supported in a WDS connection. This means that Wi-Fi Protected Access (WPA) and other dynamic key assignment technology may not be used. Static WEP keys only may be used in a WDS connection, including any STAs that associate to a WDS repeating AP.
I hope this helps somebody. This will effectively allow you to add the 4 wired ports on the WRT54G to your existing router. It should work on Linksys WRT54G v1 - v4 routers. What I used/did is in parentheses.
1. Download DD-WRT from http://www.dd-wrt.com/. (I got v2.3 Mini)
2. Flash your Linksys WRT54G with a connected PC (wired). (I used the web interface)
3. If you have Wireless MAC Filtering enabled on your main router, then you need to add the MAC address for the Wireless to your list of allowed clients. (Get this from Wireless->Status, MAC Address)
4. Disable the Firewall. (Security->Firewall, Disable)
5. Change the Wireless Mode. (Wireless->Basic Settings, Wireless Mode=Client Bridged, Wireless Network Mode=Same as your Main Router, Wireless Network Name (SSID)=Same as your Main Router)
6. If you have security on your Main Router, set it the same. (Wireless->Wireless Security NOTE: I have WEP, so I know that works. I'm unsure about anything besides that)
7. Set the Local IP Address and Subnet Mask. (Setup->Basic Setup, Local IP Address=Unused IP in the same net block. For example, my Main Router is at 192.168.7.1 and is set up to use DHCP starting at 192.168.7.100. I set the WRT54G to 192.168.7.2. Subnet Mask=Same as Main Router. Mine is 255.255.255.0)
That should do it. Just set up whatever you hook into the WRT54G to use DHCP and it should obtain an IP from your Main Router. Also, one thing that may seem odd is it will say your WAN IP is 0.0.0.0.
1. Download DD-WRT from http://www.dd-wrt.com/. (I got v2.3 Mini)
2. Flash your Linksys WRT54G with a connected PC (wired). (I used the web interface)
3. If you have Wireless MAC Filtering enabled on your main router, then you need to add the MAC address for the Wireless to your list of allowed clients. (Get this from Wireless->Status, MAC Address)
4. Disable the Firewall. (Security->Firewall, Disable)
5. Change the Wireless Mode. (Wireless->Basic Settings, Wireless Mode=Client Bridged, Wireless Network Mode=Same as your Main Router, Wireless Network Name (SSID)=Same as your Main Router)
6. If you have security on your Main Router, set it the same. (Wireless->Wireless Security NOTE: I have WEP, so I know that works. I'm unsure about anything besides that)
7. Set the Local IP Address and Subnet Mask. (Setup->Basic Setup, Local IP Address=Unused IP in the same net block. For example, my Main Router is at 192.168.7.1 and is set up to use DHCP starting at 192.168.7.100. I set the WRT54G to 192.168.7.2. Subnet Mask=Same as Main Router. Mine is 255.255.255.0)
That should do it. Just set up whatever you hook into the WRT54G to use DHCP and it should obtain an IP from your Main Router. Also, one thing that may seem odd is it will say your WAN IP is 0.0.0.0.
I'm sorry for adding to this nice DIY but i'm stuck. I've tried for a while to get it going and i'm so close yet so far. Here's the scoop.
Main router is a WRT54GC with IP of 192.168.1.1 mask of 255.255.255.0
Client Router is a V3 WRT54G with IP of 192.168.1.129 mask of 255.255.255.128
My client router picks up the main router, i'm able to ping from a computer hooked into the main router to the bridge, so the connection between main router and bridge are ok. But when I try to ping from a computer hardwired into the bridge, I can not. The computer does get an IP (192.168.1.177) ok through DHCP with a 255.255.255.128 mask. When I try to ping anything from 192.168.1.177 i don't get any reply's. Did I miss something? Here is the commands ifconfig and route from when i telneted into the wrt54g(brdige)
Freeman 1.0.4 ----I'm using this firmware because it's a V3
wrt54g:~#ifconfig
br0 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:247 errors:0 dropped:0 overruns:0 frame:0
TX packets:281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22733 (22.2 KiB) TX bytes:105720 (103.2 KiB)
eth0 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:250 errors:0 dropped:0 overruns:0 frame:0
TX packets:775 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:29217 (28.5 KiB) TX bytes:138460 (135.2 KiB)
Interrupt:5 Base address:0x2000
eth1 Link encap:Ethernet HWaddr 00:13:10:EB:4E:A0
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:544 errors:0 dropped:0 overruns:0 frame:6517
TX packets:366 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:40563 (39.6 KiB) TX bytes:70144 (68.5 KiB)
Interrupt:4 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vlan0 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:249 errors:0 dropped:0 overruns:0 frame:0
TX packets:775 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24661 (24.0 KiB) TX bytes:138460 (135.2 KiB)
vlan1 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wrt54g:~#route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.128 * 255.255.255.128 U 0 0 0 br0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
wrt54g:~#
Please give me a hand, and definately nicely done user12345, I appreciate your work here.
Thanks,
Joe
Main router is a WRT54GC with IP of 192.168.1.1 mask of 255.255.255.0
Client Router is a V3 WRT54G with IP of 192.168.1.129 mask of 255.255.255.128
My client router picks up the main router, i'm able to ping from a computer hooked into the main router to the bridge, so the connection between main router and bridge are ok. But when I try to ping from a computer hardwired into the bridge, I can not. The computer does get an IP (192.168.1.177) ok through DHCP with a 255.255.255.128 mask. When I try to ping anything from 192.168.1.177 i don't get any reply's. Did I miss something? Here is the commands ifconfig and route from when i telneted into the wrt54g(brdige)
Freeman 1.0.4 ----I'm using this firmware because it's a V3
wrt54g:~#ifconfig
br0 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:247 errors:0 dropped:0 overruns:0 frame:0
TX packets:281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22733 (22.2 KiB) TX bytes:105720 (103.2 KiB)
eth0 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:250 errors:0 dropped:0 overruns:0 frame:0
TX packets:775 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:29217 (28.5 KiB) TX bytes:138460 (135.2 KiB)
Interrupt:5 Base address:0x2000
eth1 Link encap:Ethernet HWaddr 00:13:10:EB:4E:A0
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:544 errors:0 dropped:0 overruns:0 frame:6517
TX packets:366 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:40563 (39.6 KiB) TX bytes:70144 (68.5 KiB)
Interrupt:4 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vlan0 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:249 errors:0 dropped:0 overruns:0 frame:0
TX packets:775 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24661 (24.0 KiB) TX bytes:138460 (135.2 KiB)
vlan1 Link encap:Ethernet HWaddr 00:13:10:EB:4E:9F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wrt54g:~#route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.128 * 255.255.255.128 U 0 0 0 br0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
wrt54g:~#
Please give me a hand, and definately nicely done user12345, I appreciate your work here.
Thanks,
Joe
Gillbot
Lifer
- Jan 11, 2001
- 28,830
- 17
- 81
I'm trying to get my WRT54G v2 to take the firmware. Every time I try to flash it, it just says "Upgrade are Failed" but it took the Linksys firmware fine. When the flash fails, I just unplug it and plug it back in and it works fine with the Linksys stuff. No need to reset or anything. Any suggestions?
TRENDING THREADS
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 11K
-
Discussion Speculation: Zen 4 (EPYC 4 "Genoa", Ryzen 7000, etc.)- Started by Vattila
- Replies: 13K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 8K
-
Facebook
Twitter