In article <3bdff542-cf2d-4a66-806a-
>, Ric says...
> Hi All,
> This might be a tad OT in two of these groups, but you're all
> knowledgeable people so hope it doesn't irritate anyone too much.
>
> quick sanity check:
>
> I've got a Sky-supplied Netgear D834GT router, and I want to use that
> solely as an ADSL modem, and plug it into my new D-Link DIR-655 draft-
> N gigabit cable router so I get gigabit speeds on wired, and draft-N
> wirelessly.
>
> Being Sky-supplied, the Netgear uses Sky's firmware which lacks the
> native half-bridge support I was planning to use. Being Sky, they
> hide the ADSL username and password, too. I *think* I've found this
> out, so I could flash it back to Netgear's standard firmware which
> offers half-bridging, but if I'm wrong, I'm going to lose my internet
> access for a while, so...
>
> I was originally going to connect a LAN port on the Netgear to the WAN
> port on the D-Link, put the public IP of the Dlink in the Netgear's
> DMZ and use it that way. However, it occurred to me that there might
> be an easier way avoiding potential double-NAT issues.
>
> Can anyone see any flaws in turning off the Netgear wifi, and plugging
> a DLink LAN port (i.e. not using the WAN connection at all on the
> Dlink) into the Netgear LAN port. I then get all clients to connect
> wirelessly at draft-N speeds to the Dlink, and any traffic moving
> around the LAN will presumably be handled by the switch built into the
> Dlink, i.e. at gigabit speeds when cabled. DHCP could come from
> either box, I figure it wouldn't matter. The Netgear would still
> handle firewall duties, and the QoS built into the Dlink would still
> work as it'd be regulating traffic connected directly to it. In
> effect the Dlink would be acting as a wireless switch rather than
> routing, I guess.
>
> Am I missing something that'd stop this working?
>
Just make sure that only one device has DHCP running.
--
Conor
I only please one person per day. Today is not your day. Tomorrow isn't
looking good either. - Scott Adams