Re: 16 bit subnet segmentation



I'll try that segmentation, but what is the best way to do that? By bridges
or by router segmentation.

How about the L2TP/IPSEC for VPN on ISA 2004? Right now, I'm only using the
PPTP protocol. Is it advisable to go to ipsec?

Thanks,
Ricky




"Phillip Windell" wrote:

You can add two 24bit segments alongside of the existing ones and migrate to
the new segments over a period of time. If you can wittle down the 16bit
segment to less than 254 Hosts and have them grouped into IP#s that fall
into a 24bit range,...then all you have to do is change the mask. At that
point even the mask can be changed over time because both a 16 and 24 bit
mask would work for those simultanously.

Once the original 16 segment is split into 24bit segments you could even get
rid of the new ones you created that aren't needed anymore. It is up to you
how to deal with that.

Once you are out of the woods with all this,...always keep your segment at
254 hosts or less (24bit mask). Ethernet looses effieciency after about 300
hosts per segment. It is even true with gigbit however it just isn't as
noticable to "humans".

IPSec is not meant for running between every Host on a LAN. That is
horrible. IPSec has a high overhead. It was intended to be used in a
"point-to-point" situation like maybe a WAN link between two sites.

IPSec's primary purpose is to prevent "eavesdropping" by Sniffers by
encrypting the packets. On the Local LAN your Switches already do that by
isolating the session between a pair of "talking" hosts to its own "virtual
circuit". You have to specifically configure the Switch with a Monitoring
Port to use a Sniffer. So you don't need IPSec for that.

You can do "firewall-like" filtering with IPSec too, but you can do that
without IPSec anyway, so what's the point? Plus the LAN has to be almost
"wide open" just to function normally, so there isn't a lot of filtering
even possible there.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com




"RickyVene" <RickyVene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9596A79B-CDFF-4E5A-A9D1-B269091F5224@xxxxxxxxxxxxxxxx
Hi,

I have a 16 bit subnet which is hard to administer especially with Network
speed.

I disable my ghost because it's a network killer.

Can I do segmentation with 16 bit subnet with another router?

I need also to implement IPSEC. Does this going to be a big impact on it?

Can't change my subnet, it's a big task and additional fees because our
integrated VOIP, UNIX and others are already in-placed.

Please advise.

Thanks,
Ricky



.



Relevant Pages

  • Re: 16 bit subnet segmentation
    ... IPSec provides stronger encryption, ... or by router segmentation. ... Bridges are just another name for Switches. ... Once you are out of the woods with all this,...always keep your segment ...
    (microsoft.public.windows.server.networking)
  • Re: 16 bit subnet segmentation
    ... Bridges are just another name for Switches. ... Phillip Windell ... Once the original 16 segment is split into 24bit segments you could even ... IPSec is not meant for running between every Host on a LAN. ...
    (microsoft.public.windows.server.networking)
  • Re: Configuring Port range in IPsec
    ... IPSec is intended to validate traffic between two trusted peers, ... each port (what did you want for ports 20k-64k?) both tcp and udp. ... > Ports from 10000-20000 are open for all connections from segment 10.4.90.* ... > can specify a port range and a specify a segment. ...
    (microsoft.public.win2000.security)
  • Re: Running out of IPs...what to do?
    ... Ethernet segments need to stay below 250-300 hosts. ... LAN when the number of Hosts is allowed to climb higher than that. ... segment that is full of hosts ... Microsoft Internet Security & Acceleration Server: Partners ...
    (microsoft.public.windows.server.networking)
  • Re: Expanding Subnet
    ... You just add a LAN Router into the system and create the new ... segment off of the router's other interface. ... You would then move Hosts to the new segment ... need to stay below 250-300 hosts for ethernet to remain efficient. ...
    (microsoft.public.windows.server.networking)