Re: DSL



J,

Haven't had the problem with any clients using Dynamic with those modems.
Some older routers do require setting their IP to the same subnet that the
modem is in, but most newer ones don't require that, handling separate
LAN-side WAN-side subnets quite well. (That said, the BEFSR41 is one of the
older designs, a PITA, and I replace them at every opportunity, usually
because the client wants wireless).

In fact, most routers will now pass-thru the modem's IP address, even if in
a different subnet. That, for example, permits configuring the modem in
192.168.1.x subnet from a system on a router in the 192.168.2.x subnet.

The only cautions are 1) there can be only one PPPoE client, and 2) if the
two do have to be in the same subnet, one must have its DHCP server turned
off (else both may respond to a DHCP request), and the remaining DHCP
server's address pool must not include the other's IP address. As the
Westell is typically 192.168.1.254, setting the router's DHCP to 50 or so
addresses somewhere in the .100 range, with a 12 to 24 hour lease-time, is
usually quite adequate.

As a side note, running the Westell in Bridge Mode disables its DHCP server.
That's what solves most issues with routers. Where the PPPoE client resides
is of little importance. In fact, you can run the Westell in Bridge Mode
without any router at all - just configure the connection in XP using XP's
PPPoE client [1].

The problem with running the Westell in Bridge Mode is the same, regardless
of reason. Because they do not support routers not sourced from them,
BellSouth Support will have the customer recable around the router and reset
the modem, putting it back in Router/PPPoE mode. Afterward, the customer
must then recable and reconfigure.

Allan

[1] Control Panel, Network Connections, New Connection Wizard, Connet to the
Internet, Setup Manually, Connect Using Broadband Requiring a Userid and
Password.

--
One asks, many answer, all learn - Plato, on the 'Forum
--
True civility is when every one gives to every other one every right
that they claim for themselves.

"Janice" <noway@xxxxxxxxx> wrote in message
news:T02oi.336239$p47.227043@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Derf wrote:
On Fri, 20 Jul 2007 01:23:43 GMT, Janice <noway@xxxxxxxxx> wrote:

Yeah it is, if you follow directions. It's just a matter of following
the steps but..why do you need a router? Unless you have more than one
computer either laptop or otherwise you don't need it.

Placing your computer(s) on a private, nonroutable LAN makes them more
secure. The machines can't (easily) be addressed from the Big
Internet Cloud, only from your LAN, so having a router helps keep out
all sorts of strange background packets flying around the Internet.

The modem I received from Bellsouth has it's own Firewall (Westell 2100).
You can't access it from the *big* internet cloud. It's as good as having
a router though I do have one because my neice was living with me.


And I run my setup the same way Allan does, use the PPPoE in the
modem, and have the router get the public IP via DHCP from the modem.

With Bellsouth's Westell 2100 you have to set it up to Bridged if you want
the modem to work with a separate router. If you use PPPoE it will won't
work. Believe me, I've tried. I have a WRT-54G router. The site Wally
mentions knows what they are talking about in regards to the Westell
Wirespeed 2100/2200/6100.



.



Relevant Pages

  • Re: IE Routing Problem
    ... The router will accomodate the modem. ... > SonicWall when setting up a VPN. ... >> subnet, which your internal subnet uses as a gateway, has its other ...
    (microsoft.public.win2000.dns)
  • Re: IE Routing Problem
    ... The router will accomodate the modem. ... > SonicWall when setting up a VPN. ... >> subnet, which your internal subnet uses as a gateway, has its other ...
    (microsoft.public.win2000.networking)
  • RE: RWW Issues w/SBS2003
    ... I reconfigured the routers on the LAN, placing them on the same subnet. ... This fixed the RWW connect to clients/server issues, ... From your description, we know, the issue relate to the router between ... please connect a client on the subnet A with the same ...
    (microsoft.public.windows.server.sbs)
  • Server in a NAT subet?
    ... connection from outside the subnet to a node in the subnet. ... Basically, the router is what it says on the tin, an IP router? ... server somewhere on the internet: ... The client in the subnet opens a TCP connection to the server,eg, ...
    (comp.os.linux.networking)
  • Limited or no connectivity (tried everything on pchucks, out of ideas)
    ... D-link WBR-2310 wireless router ... computers on the network. ... When I connect the modem directly there is no ... wanted to make sure I still had a connection. ...
    (microsoft.public.windowsxp.network_web)