Also sprach Mark Thornton
I am having a problem where any static ip address I assign to a client gets the wrong netmask. The same thing happens if they get the ip address from the TCH. It is probably a result of my assigned ip range 63.90.208.0 - 63.90.223.0, but it always comes up as a class a network. Does this cause problems, or should I ignore it?
In the old classful concept of things, yeah, 63.x.x.x would be a Class A (a /8 in current parlance). So, if you're dealing with things that only understand old school classes, yeah, you're going to have this problem (either it will be handled as a host route for the individual IP address, or as a /8 network). This will be the problem if you're using RIPv1, or, if you're not specifying a netmask on things when you're setting up the IP address, it will likely default to /8. How is this being assigned? Is the netmask specified in the method that you're using to assign it? <voice="Bones from Star Trek">Good God, we need details, man!</voice> :) -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.