Archived from groups: alt.internet.wireless (
More info?)
Jeff Liebermann <jeffl@comix.santa-cruz.ca.us> wrote in message news:<747mf0tict8k4sg6ggv3nd2bqhjatr20ns@4ax.com>...
> On 18 Jul 2004 17:19:37 -0700, forumemail@eircom.net (FE) wrote:
>
> >I'd like to connect my ADSL modem/router to my WIFI router, with the
> >WIFI router handling the DCHP. The WIFI router has a port for a
> >direct LAN connection with the modem. I've tried everything I can
> >think of, but I'm out of ideas at this point, can anyone help?
> >
> >The modem is a ZyXEL Prestige 623R-T1
> >(ftp://ftp.zyxel.com/P623R-T1/document/P623R-T1_v3-40_UsersGuide.pdf)
> >
> >and the WIFI router is a 3COM 3CRWE554G72
> >(http://support.3com.com/infodeli/tools/hubs/off-con/pdf/dua0055-4aaa01rev01.pdf)
>
> Well, it's a classic problem of two routers. I can see three ways to
> make it work.
>
> 1. This is called double NAT. Setup the Zyxel as a router with LAN
> port address at 192.168.1.1 (the default). Setup the 3Scum wireless
> router with a static IP:
> IP Address 192.168.1.2
> Gateway 192.168.1.1
> Netmask 255.255.255.0
> DNS1 (real DNS server IP address)
> DNS2 (the other real DNS serveri IP address)
> On the LAN port of the 3Scum router, setup:
> IP Address 192.168.5.1
> Netmask 255.255.255.0
> Have it dispense DHCP addresses starting at 192.168.5.100.
> The "5" can be any number to 254 except "1" which is already being
> used.
>
> Some routers complain if you re-use any Class B address, so an
> alternative would be:
> IP Address 10.0.0.1
> Netmask 255.255.255.0
> DHCP start 10.0.0.100
>
> The problem with this arrangment is that services that must come from
> the internet to the workstations need to drill through two routers.
> Configuration is easy enough but no fun.
>
> 2. Setup the Zyxel for a DMZ that points to the 3Scum WiFi router.
> This is exactly the same as #1 except that you don't have have to deal
> with all the services on the Zyxel, only on the 3Scum.
>
> 3. Setup the 3Scum router as if it were an access point (wireles
> bridge) and completely ignore the router (WAN) port. This is what I
> would prefer. Just plug a cable from a LAN port on the Zyxel to a LAN
> port on the 3Scum. You *MAY* need to use a reversing CAT5 cable.
> Make sure the lights show a connection. See:
>
http://kbserver.netgear.com/kb_web_files/n101236.asp
> for the basic setup and some clues on the settings. Just remember
> that the WAN port on the 3Scum goes nowhere.
>
> >Many thanks
>
> One thank is usually sufficient.
LOL, well I figured it was a big enough of a problem to need a few
thanks!
Appreciate all the advice ..what I've ended up doing (and after many
hours spent fiddling about)is configuring the modem to act as a bridge
(the setting for this was in the wizard ..things I usually stay well
away from, and why I didn't spot it sooner) this deactivates the DCHP,
allowing the WiFi router handle everything.
I've left the default IP for the router at 192.168.1.1 (when I changed
it, it wouldn't work!) with the WiFi on 192.168.1.2, everything else
falls in the 3-255 range.
Everything works as it should, with only one snag. I cannot access
the modem's web-based setup program. The solution to this is to
connect it directly to one of the workstations. However, this means
the workstation no longer receives an IP address (as the DHCP service
isn't active on the modem) and so it sets its own in the
169.xxx.xxx.xxx range. I cannot connect to the modem on 192.168.1.1,
so I have to manually reset the modem, restoring all its defaults. I
then have to make the changes I want to the settings and configure the
whole thing again!
Its not often admittedly you need to access the modem's setup utility,
but I was experiementing with dynamic dns (which the modem, but
unfortuately not the WiFi router, can handle) and was frustrated
everytime I had to do this. (incidently, I cannot get the dynamic dns
to work when the modem is bridged, maybe somebody knows more than
me??)
So that's the update, I'm not sure there's a solution as in bridge
mode, the ZyXEL modem is no longer part of the IP network it's
delivering the DSL connection and the ISP-assigned internet address to
the 3Com's WAN port, but it no longer has an IP address of its own.
(or am i wrong??)
I'm going to say "many thanks" again (it definitely needs it)