Change Details

Both UDP tests require `ping` to be able to send UDP packets, which is supported on Solaris but not on FreeBSD. So use a `perl` scripts instead. Change the shebang to allow finding the shall outside of /usr/bin, which is the case on FreeBSD, where the shell lives in /usr/local/bin. The remote test relies on a feature avaliable in ksh93, so use that shell instead. I could change the extension of the remote test to .ksh93 and extend dtrace.sh to support it. Just let me know, if this is preferred. We keep the remote test disabled, since it requires other machines to exists on the LAN. This is not always the case...

Both UDP tests require `ping` to be able to send UDP packets, which is supported on Solaris but not on FreeBSD. So use a `perl` scripts instead. Change the shebang to allow finding the shell outside of /usr/bin, which is the case on FreeBSD, where the shell lives in /usr/local/bin. The remote test relies on a feature avaliable in ksh93, so use that shell instead. I could change the extension of the remote test to .ksh93 and extend dtrace.sh to support it. Just let me know, if this is preferred. We keep the remote test disabled, since it requires other machines to exists on the LAN. This is not always the case...

Both UDP tests require `ping` to be able to send UDP packets, which is supported on Solaris but not on FreeBSD. So use a `perl` scripts instead. Change the shebang to allow finding the shashell outside of /usr/bin, which is the case on FreeBSD, where the shell lives in /usr/local/bin. The remote test relies on a feature avaliable in ksh93, so use that shell instead. I could change the extension of the remote test to .ksh93 and extend dtrace.sh to support it. Just let me know, if this is preferred. We keep the remote test disabled, since it requires other machines to exists on the LAN. This is not always the case...