Citrix client under FreeBSD
After much faffing around, I’ve managed to get the Citrix client working under FreeBSD 7. Simply downloading the most current release of the Linux ICA client doesn’t seem seem to work anymore – so you will need an older version of linuxx86 client. Citrix don’t seem to carry old versions, so I’ve uploaded them for your convenience here:
http://www.phirebird.net/files/linuxx86-v7.00.tar.gz
or
http://www.phirebird.net/files/linuxx86-v10.tar.gz
Usual rules apply – I won’t be held responsible through any misuse of these, they’re provided as is with no support, etc given or implied.
Right, first you’ll want to enable Linux binary support (lang/linux_base). Adding linux_load=”YES” to your /boot/loader.conf will ensure that you have support next time you boot. As for the installation of the client:
- Save the client (above) into an empty directory and cd to it.
- gzip -d linuxx86.tar.gz (or whatever you’ve called it)
- tar -xvf linuxx86.tar
- cp /usr/bin/true /bin/true
- cp /usr/bin/fale /bin/false
- ./setupwfc
After running through the installation (pretty self explanitory), if everthing’s ok, you should now have the Citrix client located in /usr/lib/ICAClient/. CD to this location and run ./wfcmgr
Did you find this hint useful? Are you looking to learn more? Well, here’s a few books that I’ve found useful – have a goosie!
 Absolute FreeBSD: The Complete Guide |
 FreeBSD unleashed |
 Design and Implementation of FreeBSD |
 The Best of FreeBSD Basics |
EDIT 17th June 2009: I’ve just noticed that Thomas Abthorpe will be committing net/citrix_xenapp (v11) to the FreeBSD ports collection. Requires a bit of tweaking, but you can read up on it at his page here:
Thanks Thomas!
Wireless configuration under FreeBSD 7 wpi0
This is something that I keep coming back to and Googling for. After pieceing all the bits of information together last time, I thought I’d share what I’ve found. Using these modifications, I’ve successfully configured an Intel PRO/Wireless 3945ABG network interface in my IBM ThinkPad R60 to automatically associate with a wireless network on startup (via WPA authentication) and grab an IP address through DHCP. With slight modifications, you should be able to get PRO 2100/2200 working.
First off, you want to make sure that your wireless interface is picked up and the necessary kernel modules are loaded before anything. So, after making sure that you’ve read the Intel WPI license agreement, edit /boot/loader.conf and add:
if_wpi_load=”YES”
wlan_load=”YES”
wlan_amrr_load=”YES”
legal.intel_wpi.license_ack=1
wpifw_load=”YES”
Next, create yourself the file that contains your wireless config – /etc/wpa_supplicant.conf
network={
ssid=”YOURWIRESSLESSNAME”
psk=”YOURWIRELESSKEY”
}
Finally, you want to edit /etc/rc.conf to make sure that you’re device is configured and grabs an IP on startup. Add this line:
ifconfig_wpi0=”WPA DHCP”
You should be done! Time to reboot and see! If not, try first a quick ‘ifconfig’ to see if your interface has been detected (should be wpi0):
wpi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:13:02:6b:a9:03
inet 192.168.0.103 netmask 0xffffff00 broadcast 192.168.0.255
media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps)
status: associated
ssid <YOURSSIDHERE> channel 11 (2462 Mhz 11g) bssid 00:18:f8:33:f5:1f
authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit
TKIP 3:128-bit txpower 50 bmiss 7 scanvalid 60 protmode CTS
roaming MANUAL
Things to check for – an IP address and if it’s associated (or not!). If you’re not even seeing the wpi0 interface, check your /boot/loader.conf is correct.
If the interface is there, but not associated – check /etc/wpa_supplicant.conf (and /etc/rc.conf). Chances are though that your wireless configuration is wrong. Make sure you’ve spelt your SSID correctly and that your key is also right (case sensitive – remember!)
If you’re associated, but aren’t getting an IP address – first make sure that you’re key is correct, that rc.conf is trying to get you an IP and that (duh) a DHCP server is in operation on your network!
Did you find this hint useful? Are you looking to learn more? Well, here’s a few books that I’ve found useful – have a goosie!
Absolute FreeBSD: The Complete Guide |
FreeBSD unleashed |
Design and Implementation of FreeBSD |
The Best of FreeBSD Basics |
Enabling SSH under FreeBSD
Anyone that’s diddled around with SSH under FreeBSD will be all too familiar with this error message when trying to start the SSH daemon directly:
fbsd1# /usr/sbin/sshd
Could not load host key: /etc/ssh/ssh_host_dsa_key
Disabling protocol version 2. Could not load host key
sshd: no hostkeys available — exiting.
fbsd1#
To keep it happy, you could generate /etc/ssh/ssh_host_dsa_key
manually by using ssh_keygen (as you used to in previous FreeBSD releases) - but a much more straight forward way of
enabling it now exists. All you have to do is to edit /etc/rc.conf and tag on this line:
sshd_enable=”YES”
Next time the system starts, it’ll automatically generate any
necessary keys for you and start accepting SSH requests. If you’re
of the impatient type and want SSH to start right now, use this:
killall sshd
/etc/rc.d/sshd start
And that’s it!
Did you find this hint useful? Are you looking to learn more? Well, here’s a few books that I’ve found useful – have a goosie!
Absolute FreeBSD: The Complete Guide |
FreeBSD unleashed |
Design and Implementation of FreeBSD |
The Best of FreeBSD Basics |
