Re: ip address on lan getting hijacked



Derek Broughton wrote:
steve wrote:

I agree, static IPs are pretty much necessary for anyone who uses apache
on any box or several.

Well, no, not really. You need an _unchanging_ IP, or you need to be able
to address the server by name. Both can be handled on the Linksys by using
DHCP but making it give out specific addresses to specific MAC addresses.

say here, I have 3 webcams I use for home
monitoring (teenagers, gotta love em) every box has a static IP that
has a cam on it , apache listens on different port for each box. The
router directs to a certain LAN IP depending on what port (cam) I choose
to view. I also have a webserver on yet a different box with a static
IP. DHCP would wreak havoc on my setup.

No it wouldn't.

OR you do it the way I do it here...

You have a home router with DHCP. You set the router to a set address,
like 192.168.1.1. You tell the DHCP configuration part of the firmware
to hand out a bank of addresses at a particular point, like, say,
192.168.1.100 to 150 or 200. You *statically assign* addresses to key
devices...printers, your primary workstations, etc...in another "bank",
like 192.168.10 to 20 for printers, and 20 to 99 for your workstations,
only you don't use them in the DHCP server at all. You put them on the
devices themselves.

If you have more than 50 transient systems in your home network, you are
probably doing something like either LAN parties or you have people
hopping on that aren't in your home. If you have more than 10 network
printers in your home you probably should not be using a "home network"
setup because that's rather beyond the average home user's network
configuration (at least until the concept of a truly digital home
spreads and you need IP addresses for your washer, drier, and oven...)

The DHCP can handle just your transient devices. Keep organized banks of
IP's set aside to assign *on the devices* you're not going to change
so you can keep track of them and not have to reconfigure a new router
if something happens to them, as inevitably happens to home/SOHO
multifunction routers...you just drop in the new one with the old one's
address and set the old bank of DHCP addresses to the new one's DHCP range.

-Bart

--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... I've thrown quite a bit at them, and just have to disagree that they are inherently less secure than the netgear. ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... Yeah, maybe it's not that different from the Netgear, for all that. ... that when I first used the Netgear router with SBS 2003, ... tech spend 4+ hours on my system, and then tell me to enable DHCP ... more than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... OK, yes, I've struck a router which would only allow DHCP clients access to ... no internet connection from the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: FreeBSD workstation on Windows network?
    ... I have a home network w/ DSL and a wireless router. ... is connected to a cable modem and does DHCP. ... Perhaps I could use the FreeBSD machine to make my home network more secure. ... If you want to play SYSV again, ...
    (comp.unix.bsd.freebsd.misc)