Re: home lan setup suggestions

On 01 Feb 2008 21:47:20 -0600, comphelp@xxxxxxxxx (Todd H.) wrote:

Ragga <look@xxxxxxxxxx> writes:

I'm a total noob at networking but I somehow managed to link a Netgear
DM111P to a Linksys WRT54G and make it work, thing is I have 2 working
configs and I'd like to know if one is better, or if both are stupid
and horribly vulnerable.

The latter is Sebastian G's opinion about... well, almost everything.

Please be kind.

I'll try.

Before you plug either into the internet, be aware of a current issue
with Flash that's making exploiting of UPnP rather common right now,
so whatever you do, you'll want to make sure you get updated firmware
for your router, set an administrative password, and disable UPnP
before you stand em up on the net and do a bunch of web browsing from
behind em.

1st config- modem is set to pppoe-bridging with dhcp on (in pppoe mode
it can't be turned off) , router's internet connection dialog set to
auto-dhcp.
Router internet config dialog shows:
Connection : Auto-dhcp
IP address : 192.168.1.1
Subnet : 255.255.255.0
Default gateway : xxx.xxx.xxx.N+1 , being the IP assigned by ISP
xxx.xxx.xxx.N
Modem manages the connection/disconnection to internet, being still
accessible trough browser at 192.168.0.1 (this puzzles me because i
though it wasn't going to work, since router's gateway is set to
another ip)


The router itself uses the gateway IP given to it by the ISP. It uses
it as the default next hop it's gonna send outgoing traffic to on the
WAN interface.

Your LAN devices will use your router's IP as their default gateway.

2nd config- modem is set to rfc-bridging, this turns off modem dhcp,
router internet connection set to pppoe.
This way router manages connection/disconnection to internet, and
modem is no longer accessible at 192.168.0.1
Router internet config dialog shows:
Connection : PPPoe
Ip address: ip assigned by ISP
Subnet: 255.255.255.255
Default Gateway : ISP's gateway

There's an option for connecting the router to a static Ip (which is
obviously not my case) but i tried to set static IP to 192.168.0.1
just to see what happened... didn't work.

I think that setup may have bridged your entire lan right onto the
internet. You'd have to get multiple-IP support from your broadband
provider for it to work, and your lan machines would contact the isp
dhcp server for addresses, if the multiple-ip broadband plan didn't
come with static IP's for you to assign your machines.

You probably really dont' want to be bridging your machines on the
internet.

My limited knowledge suggests me 1st is better (lan before router -
lan between router and modem - internet , maybe?), but i can't tell
the difference between a wan port and my butthole, so I confide in
your experience.
Thank you.

Your gut guides you well.

I probably know even less than the OP professes to, but my setup is
similar to his number 2 config. My flaky understanding is that the
broadband modem is effectively just presenting the broadband
connection to the router, which has its own firewall and NAT inbuilt
so that the baddies can't get in. Is that wrong?

The only issue I have with the arrangement is that I can't get at the
modem from a machine on the LAN to see stats, configure it, etc,
unless someone knows an easy workaround?
--
All the best
David Millen
Xativa, Valencia
www.fincacasablanca.com
please reply in group
if you have to email me, remove the obvious:
davidtheobvious@xxxxxxxxxx
.