On Jan 07, shyamk @ eth . net wrote:
>
> I am in a precarious situation :
> One fine morning , my boss pulled out a cable to
> connect the 2 switches (1 switch for one LAN).
> This may be what it looks like :
>
> (machines (machines
> 10.10.1.*) 192.255.255.*)
> [switch1] -------------------- [switch2]
> | |
> LAN1's LAN2's
> computers computers
> connected connected
> to this switch to this switch
>
> This choice came out of the blue and I do not
> have time to work out my basics right !
>
> I am too tensed up to think. My thinking is
> I will have to get the 192.255.255.* LAN
> over to 10.something.something.something .
>
well firstly you shouldn't be 192.255.255.*. This address region is ment to
be 192.168.*.*, I would actually recommend 192.168.1.*. If this lan
(2) planned to connect to the internet there would of been trouble! Mainly
the firewall/proxy would of not fowarded the requests to the internet
resulting in LAN2 being unable to see the internet, and depending on how the
switches are set up LAN1 may not be able to see LAN2 and vice versa.
> One is Class A , the other is Class C ,
> so may be I will make all of them onto
> Class A.
>
> Well , my boss wants the Proxy (to the Internet)
> {and later the firewall which I will then ask you}
> to be on 192.255.255.1 . That means the
> 10.10.1.* guys will have to reach the other LAN
> via the switch and then use the Proxy.
>
> Is my line of thinking right ? ie: Converting the Class C
> -based LAN2 's IP Addresses over to the 10.*.*.* ,
> so that both Windoze and Linux can see LAN2 .
>
> Please share your views and experience on this.
>
I would recommend changing them all to the same address space. If it was a
home setup I would recommend 192.168.*.*, however as you are in a business
situation 10.*.*.* is best. Mainly so if you company is spread over several
physical *sites* you can use 10.*.0.0 to seperate the sites and on each site
allocate 10.<whatever>.*.*. I hope this is clear. Do e-mail me if you are
unsure, I will also give a quick explantation on the *official* ip address
talk ;)
If you want to be quick and simple and you have less than 254 (=256-2)
computers on the site then use 10.0.0.*. Then you will not need to be fusy
with routing tables or fancy addressing. The switches should be able to
handle all the hard work. This however is a Bad Thing (TM), mainly for the
reasons of management and the ARP tables could get upset on the network.
You may also find your switches become unessarily loaded due to broadcasting
messages will reach both LANs. I'm assume the client machines are running
Windoze, this usually means *lots* of NetBIOS messages. This gets nasty and
254 machines all broadcasting can have a nasty effect of system performance
:)
When you are thinking straight ;) and have some time to hand you then can
begin the *great* renumber. You may also want to consider using an old 486
box on each LAN to behave as a DHCP server to give out the addresses
automatically....this is another question all together though.
If the boss is screaming in your ears (and they can ;) ) then give everyone a
10.0.0.* address and renumber the machines at a later stage. Lucky for you
you don't have to do *every* machine at once, they can be done as you want at
a later date.
Do mail me if you need things to be cleared up.... :)
Alex
--
________________________________________
/ Waste not fresh tears over old griefs. \
| |
\ -- Euripides /
----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
Attachment:
pgp85BAdRks1n.pgp
Description: PGP signature