Re: Networking Problem - yup
Jonathan Barnes wrote:
Alvin Oga wrote:
yup ... your mask 255.255.255.0 says use only the last octet ..
10.0.0.x is NOT in the same network as 10.1.1.x
it's doing what you told it ... maybe not what you want
if you want to use 10.0.0.2 ... don't... "0" is best used for network
name
use 10.1.1.2 and your troubles is over
if you insist on using 10.w.y.x ... use 255.0.0.0 for your mask
and change anything you like except 10
if you insist on using 10.0.y.x ... use 255.255.0.0 for your mask
and only change y.x
if you like a "class c" of 10.0.0.x ..... use 255.255.255.0 for your
mask
and only change "x"
c ya
alvin
Thanks for the reply, I was wondering what a good way of subnetting my
networks would be.. What would be be advisable for someone with a DMZ
and a LAN, and another LAN inside the first LAN
(basically, I live upstairs from where i work, and I've set up a DMZ
and LAN downstairs for work, then I have my own personal server
upstairs (the one with the problem) with my own personal LAN behind it.)
Currently I'm just using 10.0.0.* for the LAN, 10.0.1.* for the DMZ,
and 10.1.1.* for my upstairs LAN, with 255.255.255.0 as the mask for all.
However, I had no problem with the network before my server had a hard
shutdown, but I still was interested in bettering my network.
I use 192.168.x.x address coz I started back when we had class A, B, C and some other network classes,and the default netmasks for these are 255.255.255.0.
Over time I"ve moved up from 0.x and 1.x as I've had networks come and go.
At the moment I have a powermac running as a firewall. Its inside network is 7.x. Currently the only other box on that network is my test server which is also the gateway to my next LAN.
ts has four (I just counted them) NICs in it. When the mood takes me, I can configure that box as an ADSL server.
At one point I had my office LAN on 8.x; the last vestige of that is a NIC in one box, called my New Server.
ns came about when I was at an auction, and I bid "because it was too cheap." For my pains I won a Pentium III with 256 Mbytes ECC RAM, 2x SCSI disks, onboard SCSI, a DDS2 tape. Its price was comparable with other Pentium IIIs at the time, maybe a little cheaper than average. Since the average has on ATA disk, 128 Mbtes (maybe) etc, it was quite a buy.
I installed Sarge on it, but Sarge kept segfaulting. Eventually I moved the disks into my PII 233 system which also has SCSI onboard, and merged my office server with my new server, and that's why that box sits on two networks.
I later downloaded and ran memtes86. Bloody RAM. one of the sticks was bad, and that's all that was wrong with it.
I also connect several LANs by VPN - mine and some of my employers'. I'm keeping them all on their own IP address ranges so there are no routing issues. Shorewall can block undesirable routing.
Work LANs currently use 0.x, 1.x, 4.x, 6.x, 9.x (conflicts with mine but doesn't matter: if I mustm, I can get route it).
Routing for printers & such can be an issue: they don't necessarily know how to get to some of the LANs.
--
Cheers
John
-- spambait
1aaaaaaa@computerdatasafe.com.au Z1aaaaaaa@computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Reply to: