# # SCO Unix OSR5 DHCP
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

SCO Unix OSR5 DHCP

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© May 2011 Anthony Lawrence

Early SCO Unix had no DHCP client capability. That perhaps was somewhat reasonable; these machines were servers and could be expected to have a static IP address. However, as DHCP can do much more than simply provide an IP address, having DHCP would have been advantageous at times.

SCO first added DHCP client support in their 5.0.6 release and released a TLS 711 supplement for 5.0.5. That had some issues, as noted here. The DHCP server (first seen in the 5.0.5 release) had its issues to, though mostly just confusion with older protocols; SCO folk weren't used to this new-fangled DHCP stuff.

The older protocols got confused too. The HP Printer manager defaulted to bootp, and that caused unexpected problems for folks who did not realize that they were configuring an inactive protocol.

SCO's DHCP server could handle multiple subnets (something still beyond the capability of many inexpensive routers). You put each subnet in /etc/dhcpd.conf:


subnet 192.168.2.0 {
        comment Main
        mask 255.255.255.0
        pool DotTwoPool
        routers router.somedomain.com
        dns_servers dns.somedomain.com
        domain main.somedomain.com
}
 

SCO's DHCP server was also a bit confusing because it had two separate "managers": - the Address Allocation Manager, which defined the range(s) of addresses the server could hand out, and the DHCP Server Manager, which defined options. Running these produced to files that youa could hand edit: /etc/aasd.conf and /etc/dhcpd.conf.

Here are examples of what those files look like: Sco dhcp configuration example.

Windows 98 machines could cause mysterious "ping sendto failed messages" in syslog. The fix to /etc/dhcpd.conf was easy enough.

Apparently SCO IPX (old Netware) could confuse things also.

SCO expected hostnames to be no more than 8 characters. That caused problems for this person as their ISP insisted on a longer name.

Another bug/feature had to do with static ip's forced onto machines not updating.


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> SCO Unix OSR5 DHCP


Inexpensive and informative Apple related e-books:

Take Control of iCloud

Sierra: A Take Control Crash Course

Take Control of Apple Mail, Third Edition

Take Control of Pages

Photos: A Take Control Crash Course





More Articles by © Anthony Lawrence





Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





The psychological profiling [of a programmer] is mostly the ability to shift levels of abstraction, from low level to high level. To see something in the small and to see something in the large. (Donald Knuth)




Linux posts

Troubleshooting posts


This post tagged:

DHCP

Networking

SCO_OSR5



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode