D'oh! The first thing you need to do, if your [secondary] router is NOT getting it's IP address via a DHCP lease from the primary, is set it to a non-colliding address! It should have the same netmask, unless you've already got some routing plan in mind to over-ride the default bridging (leave the rest alone).... but the two routers should definately not have the same IP on the same subnet -- no two devices ever should, shall I say "under normal circumstances".
Ben PS - did I get thread-jacked too? (...or aid & abet this jacked thread?) I just reply to the most recent thread that interests me; I might've missed some of the other dd-wrt thread(s), sorry if so. On Sat, Feb 14, 2009 at 2:40 PM, dooger watts <[email protected]> wrote: > This all reminds me of another quirk in my setup--namely that I can NOT > communicate with my own router (to check configuration) when the client > bridge connection is working. When I lose my internet connection, THEN I > can log onto my router and get the dd-wrt config panels. > Which means of course that I can't just "switch" to repeater bridge mode > from client bridge. (Only way I can get to repeater bridge mode is to set it > up from scratch, after a 30-30-30--and then it does not work). > Have tried connecting to the default dd-wrt address of 192.168.1.1 while > online--but I get my neighbor's (primary) router--which kinda feels like a > major invasion of privacy and which I log off of instantly. Hell I can even > log into his printer--but I can't log into my own router when I'm online. > > Weird, huh? > > Ben Barrett wrote: > >> Cool beans. I used the latest stable DD-WRT firmware, v24-sp2 dated >> 10/22/08, is what I'm using on the secondary. I don't think the primary has >> to change any settings to get the secondary to go from client bridge to >> repeater bridge, but I think it might just have to give up the connection >> for a while (I power cycled my primary right away and got it on). So you >> might try repeater bridge before you power cycle, if you have some time to >> hang around. I don't know if it is an issue of the DHCP lease expiring from >> the primary (which is my only dhcp server on this lan, and which extends to >> the bridged network). Make sure you're not just running out of leases (you >> might have connectivity but not get allocated a dhcp lease). >> >> Best of luck, >> >> _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug >
_______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
