acidrayne

So I've got 2 WRT54G wireless routers. Both have Sveasoft's latest stable version (Satori 4). The one is working fine as an AP. The other one I have been trying to get to work as a client, but am not having much luck. Through my troubleshooting, I eventually turned off MAC filtering and WPA. At this point, I saw some improvement, but very minimal.

In the wireless section, the client was set to the same channel, etc. as the AP. I have the LAN IP of the AP as the IP of associating AP. This changed the LAN gateway on the Setup page of the client. I went ahead and set the LAN IP on the client and in the end, set the WAN IP also on the same network using the AP LAN IP as the Gateway for the client WAN.

It seems that when I power cycle the client, it will get one ping back from the AP, but then times out again. If I am looking at the AP, I see various situations on the wireless status. At times, I will see one of the client MAC addresses and other times, both. I'm sure I am doing something wrong or maybe it's just jacked up.

My intention is to eventually mount the client on the wall and connect it to my XBox so I can wirelessly connect it to my network. I would like to use this router because it is far cheaper than even the wireless game adapters and even cheaper still than the Linksys WET54G.

Any help or advice would be much appreciated. The Sveasoft guide is pretty sparse as to how to configure other settings for client mode.

Thanks

__________________
Rayne

acidrayne

So after messing with this thing again tonight, I still am not sure what's wrong. At one point I was able to ping the client from my laptop over wireless meaning according to documentation that I would have been routing through the AP first, then back out to the client. At this point, I have MAC filtering back on which is working just fine. I had to (or at least it seems that way) add 3 MAC addresses to my list. The two for the two interfaces and one virtual. I turned WPA back on and after power cycling, the wireless status on the AP shows the MAC of the client one time and then when refreshing, it is no longer there ... refresh again and it is there again. At no point am I able to ping it from either my laptop or the AP shell.

Note: My prrevious post notes using this for my XBox. I am using my laptop for testing and simply disabling the wireless card or normal NIC when using the other of the two.

Again, any advice would be helpful. I am using the free version of Sveasoft's firmware and would prefer not to pay just for the support as I am not likely to use the testing firmware. I have searched Google and am only finding information on how to setup WDS which is not what I want to do and other than that, an occasional success story stating it just worked.

__________________
Rayne

Thorn

Rayne,
Just out of curiousity, but did any of this work with the original firmware? I'm wondering if it's something with Sveasoft's version or if the problem lies elsewhere.

An Xbox will get picky about network setups under certain conditions, and my first thought was that was your problem. However, using the laptops should eliminate that as an issue, so now I'm wondering about the firmware.

__________________
Thorn
"Read Altas Shrugged. Compare it to today. Repeat as necessary"

acidrayne

Thorn ... Good to see you BTW. There is one problem. The Linksys firmware does not have a client/bridge mode or I would use it. Since my last post, I have loaded the linksys firmware back on to ensure that the wireless and wired connections both work fine. I then loaded the Sveasoft firmware on again.

Here's the part that gets me. The router has 2 interfaces. When putting it into client mode, you are eliminating the use of one. This should allow the router to function similarly to one which has no WAN connection. You should still be able to ping from a wired device to a wireless device connected to the same router.

Anyway ... If I don't have anything hard wired to the client router, I can ping to my heart's content. From my desktop to the client router and back. If I have something hard wired or more specifically data passing on the LAN ports, then it's as if the wireless connection drops. From my AP, I can see the MAC address of the client router, but cannot ping it nor can I ping my AP from the laptop. I can however ping the client router as I am directly connected to it. The reason I narrowed down to data on the LAN was because if I disable the wired NIC, then all is well on the wireless side.

I have also tried using a cross-over cable instead of the straight cable included. I have tried connecting to the WAN port just to be sure as well. When connected to the WAN port, the client router does not communicate on that port. I can ping that interface from the other interface in the client if I configure it so, but I cannot ping the client router from my laptop through hard wire.

I know I'm running on here, but this is driving me crazy. It seems there is some crazy conflict occuring when I try to pass data on the wired and wireless of the LAN interface.

I'm still trying, but if I can't figure this out by the end of the month, I am going to return the router within my 30 days and buy the WET54G from Amazon to get the $20 GC. Any more help you could provide is appreciated. I am going to see if I can get some free help on the Sveasoft forums, but I don't know if I can without paying them.

Thanks Again Thorn

__________________
Rayne

Thorn

Rayne,

For what it's worth, I finally gave up on using WET11's or even the WGA11 on my Xbox. The whole configuration was a pain. You need an Xbox plus a desktop or laptop to configure the device. Not a big deal at home, but if you travel to a LAN party, it can be a major PIA. You have three choices: 1)Either drag the laptop along with the Xbox, 2) Bring the software to install and use someone else's PC, or 3) Set it up before hand and hope you get all the details right.

I finally bought a Microsoft MN-740, the Xbox Wireless Adapter. ($80US at Target stores). It competely configures via the Xbox Dashboard, and is a dream.

__________________
Thorn
"Read Altas Shrugged. Compare it to today. Repeat as necessary"

mwb1100

For what it's worth, I'm running into exactly the same problem as Acidrayne. Not that I have any solutions, yet, but I'm working on it.

mwb1100

I think I found the solution to this problem. Just for reference, I'm using Satori Firmware version Satori-4.0 v2.07.1.7sv, which is the 'public' release of the Satori firmware. My access point is another WRT54G running HyperWRT v1.2 firmware which is a minor modification to the Linksys v2.04.3 firmware. In theory, the AP should not matter.

On the Satori Administration/Management page, there's a setting for 'Loopback' about halfway down the page.

I really have little idea what it's for, but on the Sveasoft forums there was some mention of it in regards to Client mode. It was set to Enabled by default, I changed it to Disabled and the Satori WRT54G in client mode started working just fine in both directions.

I am currently typing this on a laptop that's connected to the Client Mode WRT54G which is bridged to a WRT54G AP running HyperWRT 1.2 firmware.

Another thing that I found is that the MAC address that the Client Mode WRT54G presents to the AP is wildly different from what is displayed in the status page for the Client Mode WRT54G. This is only important if you have MAC Address restrictions set on the Access Point (which I do).

If you are using MAC addresses restrictions, then you should disable them when setting up the Client WRT54G, then once you get the Client WRT54G connected and working use whatever report mechanism the AP provides for listing currently connected MAC addresses on the Wireless interface. On the WRT54G (at least with the Satori firmware) that is done in the Status/Wireless page then press the 'Wireless Clients Table' button.

For example, the Wireless MAC address reported by my Client WRT54G in its status page was something like:

00:0F:66:B1:7C:98

But the MAC address that the AP was seeing was:

08:00:46:18:73:64

I suppose this is a bug in Satori.


I hope this helps you.

--
mwb1100

G8tK33per

Thank you...

__________________
"My mind is aglow with whirling, transient nodes of thought careening through a cosmic vapor of invention."

Sons of Confederate Veterans

wrzwaldo

That sounds normal for a router (a MAC for each interface). The "Status" page on one of my wireless routers has sub tabs for Router and Local Network. Each has their own MAC (see first sentence).

Could it be that "00:0F:66:B1:7C:98" is the WAN MAC and "08:00:46:18:73:64" is the LAN side MAC?

mwb1100

Later that evening I had a bit of a 'Doh!' moment...

The MAC address that the AP sees is the MAC address of the interface that is plugged into the WRT54G being used as a bridge instead of the MAC address of the bridge unit itself. No bug, no mystery.

--
mwb1100

kurkesmurfer

This is intended for Acidrayne,though it's probably to late to help him out...

Basically I stumbled onto this forum today while exploring the possibilities of this amazing firmware. I had no problems getting it to hook up to my internal network. The key thing I am missing in the posts is the name of the SSID that the linksys is joining. I've set both the static IP and The SSID to the one that my AP uses (incl. channel etc.).

I know I've read somewhere how to get it to simultaneously run in client mode AND run a local AP.... can't seem to find it though...

Good luck,

tuagej

I have two WRT54G's which one of them has original linksys firmware and it's connected to internet(DSL) and one wired PC.Second WRT54G has Sveasoft's Alchemy-pre5_3 firmware and i put it in client mode and two PC's wired to it.
Here is problem:
IP of the first wrt = 192.168.1.1
IP of PC wired to first wrt = 192.168.1.12
DHCP on 1st wrt is set to enable

IP of the second wrt(client) =192.168.1.2
IP of the two PC's = 192.168.1.11 and 192.168.1.15
DHCP is set to disable

I have the same SSid and channel so there shouldn't be any problems with it

I can see both PC's wired to second wrt on lan and ping it also but when i try to ping second wrt i receive time out's(
But when i survey for the first wrt i found it and also when i click renew dhcp i get gateway and dns ip's from it.
But what next???
It seems that i just can't get this bridge to work(
Is there anything i should do on first wrt??
How can i connect to first wrt???

Tnx for any help

tuagej

This is what i have now

I upgraded firmware on both routers.First one which is connected to internet has Sveasoft's Satori 4.0 firmware which enabled him to act as AP.Second WRT54G has Sveasoft's Alchemy pre 5.3 firmware and now i can use it as client.I could also use Satori firmware for this but supports only one PC in client mode, but i need support for two or even more later.
Here is what troubles me(
When i survey for AP from second WRT i find the first one. When i check status in first WRT i see that has one client.All MAC addresses match.
DHCP on first WRT is on, IP = 192.168.1.1
DHCP on second WRT is off, IP = 192.168.1.2

How can i now connect from one PC wirelessly to another???

wrzwaldo

You may want to spend some time over at Sveasoft's forums...

Swos

Could it be because the WRT in client mode with Alchemy-firmware only support more than one PC if they are in a different subnet!? (I don't know too much about subnets )
Check out post #6 here: http://www.broadbandreports.com/forum/remark,10755968