But... The default route is where everything that is masked by your
network netmask should go! As such, a netmask on the default route
doesn't make any sense. Isn't it just a place-holder so that the tools
used to set the default route don't have to be special?
If you want to block a set of addresses from being accessed, you need
to use a router like the 'Cisco' or Linux "firewall". Lets say I don't want
anybody to access 123.321.321.321, I can't do this with a netmask without
preventing access to 254 other nodes (0xff - 1). You would have to "mask"
specific addresses. This is what routers can do for you.
Cheers,
Dick Johnson
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Richard B. Johnson
Project Engineer
Analogic Corporation
Voice : (508) 977-3000 ext. 3754
Fax : (508) 532-6097
Modem : (508) 977-6870
Ftp : ftp@boneserver.analogic.com
Email : rjohnson@analogic.com, johnson@analogic.com
Penguin : Linux version 2.1.40 on an i586 machine (66.15 BogoMips).
Warning : I read unsolicited mail for $350.00 per hour. Supply billing address.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-