I converted the SCO system to the linux box, and when I did, I just
copied over the ipalias config file that was used by the guy who set it
up. He wrote his ipalias script in shell though and I didn't like it
much, so I rewrote it. The guy who added new virtual domains just kept
doing things the same way, so all the new ones got added with that
netmask. When I tested the ability to use those addresses I did it by
hand and so the netmask was entered correctly and it worked. I'm
guessing SCO must have some kind of weird ipalias restriction that
requires /29 subnets for ipaliasing or something. Sheesh, I'm glad it
didn't bite me. ;-)
Thanks guys, I appreciate your help in this...
-----Original Message-----
From: Glynn Clements [mailto:glynn@sensei.co.uk]
Sent: Monday, August 03, 1998 10:42 PM
To: Mark Bainter
Cc: 'linux-net@vger.rutgers.edu'; 'isp-tech@isp-tech.com'
Subject: RE: IP Aliasing under Red Hat 5.0 (Weird problem)
Mark Bainter wrote:
> eth0:1 Link encap:Ethernet HWaddr 00:80:5F:5C:F1:1F
> inet addr:208.226.220.133 Bcast:208.226.220.128
Mask:255.255.255.248
In your previous post, you stated that you had a /26 subnet from .128
to .191. This output indicates a /29 subnet, which would explain why
you can't use any IP address where the bottom 3 bits are either 000 or
111.
Also, 208.226.220.128 isn't a valid broadcast address.
The same applies to all of the other 42 alias interfaces.
-- Glynn Clements <glynn@sensei.co.uk> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu