RE: [cobalt-users] Network Mask/Bit Question

[Brandon Wheaton <brandonw@xxxxxxxxxxxx>]

Hi.

Your message is a bit confusing but this is what I gather:

You have a /26 from your provider - that is 64 IP addresses 
minus two - one for the gateway and one for the network.

The subnet mask you have set for the Raq is set for a /14 
(255.255.252.0) which is 64 subnets of 262,144 IPs each - 
this is clearly an error. You try and fit 262,000 IPs onto 
a raq :^)

Change your main subnet mask to 255.255.255.192 and use that 
same mask for any additional IPs you add to the machine (within 
that /26). 

Brandon Wheaton
UNIX Systems Engineer 
ValiCert, Inc.
1215 Terra Bella Ave. 
Mountain View, CA 94043 
650.567.5430 
----
Computers are useless; they can only provide answers.
~Pablo Picasso

-----Original Message-----
From: David [mailto:david_dean@xxxxxxx]
Sent: Tuesday, September 05, 2000 8:50 PM
To: Cobalt User Group
Subject: [cobalt-users] Network Mask/Bit Question


Hi Group,

Can anyone help me with a network mask issue on an RaQ3(?), I'm stumped.

We just setup another new RaQ3 in a new co-lo facility. The colo facilities
setup the basic network settings (control panel -> network) when they
released
the machine. The *main* IP on the server has a subnet mask of 255.255.252.0
and is entered correctly on the network settings page.

-The colo assigned an additional 62 IP's to the machine, but they have a
different netmask of 255.255.255.192.

-We created/registered primary DNS using one of these additional 62 IP's
which
uses a different netmask than the main IP of the machine.

-Setup primary DNS under DNS Parameters... (control panel -> services -> DNS
Parameters...) with a PTR bit mask of 26 as that equals 255.255.255.192

The Problem - We're unable to connect to any of the additional IP's
installed
on the system. Support says:

>You should use 255.255.255.192 for any address
>you configure in the range 62 IP range.

Where...? Isn't a 26 bit PTR setting the same as 255.255.255.192?? While the
main IP has a mask of 255.255.252.0 (network settings), any domain/IP
entered
via DNS with a 26bit setting showing up with a mask of 255.255.252.0 as
well.
Shouldn't the 26bit setting be showing up in the adapter settings as
255.255.255.192?

The ethernet adapter settings:

eth0:0    Link encap:Ethernet  HWaddr 00:XXXXXXXXXX
          inet addr:64.xx.xx.xx  Bcast:64.xx.xxx.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:11 Base address:0x1000

eth0:1    Link encap:Ethernet  HWaddr 00:XXXXXXXXXX
          inet addr:64.xx.xx.xx  Bcast:64.xx.xxx.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:11 Base address:0x1000

eth0:1    Link encap:Ethernet  HWaddr 00:XXXXXXXXXX
          inet addr:64.xx.xx.xx  Bcast:64.xx.xxx.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:11 Base address:0x1000

Any ideas? Could this be a bug that's keeping DNS entries with a netmask
setting of 26 bits from not updating correctly with the adapter with the
correct network mask?

Thanks for any input.... I'm a bit lost on this one...

-David


____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1


_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users