Greetings Michael,
I think you have NAT turned on the AP - my thinking is that only the WRT54G acting as the router should have DHCP turned on and the bridge should act as a bridge -
I have NAT only running on the gateway AP (fw1 let's call it) ditto for DHCP. The second AP (fw2 no internet hookup) is not running a firewall, DHCP server and is not NATting (routing, etc is all turned off).
I am running the Sveasoft firmware too and could not get this scenario to work for me for other reasons and went back to a WET54g and WAP54g and that works for me fine (I have a linux DHCP server). I have a spare WET54g if you want to try that route.
The mesh has been working great for well over 1/2 a year, with my/friends/family's laptops picking up IPs and working fine...likewise for my tivo...from both APs...
Plus I find it strange that the SBs discover the .102 static DHCP lease and then once they are fully up, under settings->info->player info, it player IP is the .1 addy...the server is telling the SB something different than what I want as I notice it also picks up the slimserver-appointed name (family room) for this client too...
strange...still trying different things here...
jas
-MA
Jason Temple wrote:
I am on the same subnet (255.255.255.0)...with one little twist...here's the story. I'm using a wireless bridge to connect one part of my house to the other. So I have two linksys wrt54g's and I'm running the Sveasoft firmware that allows one AP to be connected to the internet and the other to act as an AP and a wireless bridge to the first AP. It's been working great for more than 1/2 a year as I use my laptop in that room through this wireless bridge no problem, my hacked tivo also uses this (both on static leases just like the SB). Like I mentioned earlier, the SB can receive it's static DHCP lease fine, it's just when it's looking for the SB that it screws up (the SB static lease is .102, the slimserver is .100 static lease and the APs are .1 for uplink and .2 as AP/bridge to .1). So the issue is that during setup, it sees this SB and hands out .102, but once this machine connects to the slimserver, it sees it as .1 and udpates the SB that way also (as the info->settings menu reflects the SB as being .1 at that point). So is the slimserver re-writing the IP for the SB? Does this make sense to anybody?
jas
Marc Sherman wrote:
Jason Temple wrote:
Greetings All,
I was curious how the SB finds it's slimserver on a local subnet when
it's reset. I've got a situation where my router is handing out static
leases properly, the SB receives it, but when it searches for a
slimserver, it cannot find it and I have to enter it manually. What's
more is that when I do specify it manually it can connect to the
slimserver and stream music, but if I check it's settings, it has the
wrong IP (actually the ip of the router the slimserver is plugged into).
I'm running 6.0 (2/6 build).
Are you sure you're on the same subnet? That sounds like two different subnets to me.
- Marc _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
