Bigfoot65 at 01:42, 18 May 2016

2016-05-18T01:42:20Z

Duke at 21:03, 27 June 2010

2010-06-27T21:03:41Z

Duke: Created page with 'It is not recommended to run an Amahi server over a wireless network connection. Quick response times are important when all the computers on a network are relying on your serve…'

2010-06-27T20:57:49Z

Created page with 'It is not recommended to run an Amahi server over a wireless network connection. Quick response times are important when all the computers on a network are relying on your serve…'

New page

It is not recommended to run an Amahi server over a wireless network connection. Quick response times are important when all the computers on a network are relying on your server for DNS queries and other functions, and wireless connections are not known for their reliability and optimal connection speeds. Many aspects of Amahi are not tested to run exclusively wireless.

If you would still like to experiment with running your server over a wireless connection, open a terminal as root and try the following steps once your HDA is installed.

'''Note:''' This assumes your wireless device is already working in Fedora. Make sure you can connect to your wireless network before you move on to installing Amahi, as it disables wireless networking during that process. For some devices, you may need to find special drivers or do other troubleshooting.

1. Make a backup copy of <tt>/etc/sysconfig/network-scripts/ifcfg-eth0</tt> and <tt>/etc/sysconfig/network-scripts/ifcfg-wlan0</tt> in your home folder in case you'd like to return to Amahi defaults later.

2. Tell Amahi that you're using wlan0 instead of eth0 so that it doesn't try to overwrite your changes.

Edit the file <tt>/usr/bin/hdactl</tt> and change the line

<tt>my $device = "eth0"</tt>

to

<tt>my $device = "wlan0"</tt>

3. Your wireless device is likely disabled for reliability reasons when Amahi is installed. Let's turn wlan0 on and eth0 off by default:

Edit your <tt>/etc/sysconfig/network-scripts/ifcfg-eth0</tt> file to read:

<tt>ONBOOT=no</tt>

(it will say <tt>ONBOOT=yes</tt> by default.)

Edit your <tt>/etc/sysconfig/network-scripts/ifcfg-wlan0</tt> file to read:

<tt>ONBOOT=yes</tt>

(it will say <tt>ONBOOT=no</tt> by default.)

4. Set up the appropriate settings in <tt>/etc/sysconfig/network-scripts/ifcfg-wlan0</tt>

You will probably want to copy the following lines over from the <tt>/etc/sysconfig/network-scripts/ifcfg-wlan0</tt> file:

<tt>IPADDR=192.168.0.10
GATEWAY=192.168.0.1
DNS1=192.168.0.10
DNS2=192.168.0.10
SEARCH=mynetworkname.com
DOMAIN=mynetworkname.com
NM_CONTROLLED=no</tt>

5. You likely need to configure a password to sign on to your wireless network - unless you are a serious exhibitionist and don't protect your network.

Edit <tt>/etc/wpa_supplicant/wpa_supplicant.conf</tt> to make sure the following is in it with your appropriate details:

<tt>ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="mynetwork"
key_mgmt=WPA-PSK
psk="mypassword"
}</tt>

Edit <tt>/etc/sysconfig/wpa_supplicant</tt> to make sure that the lines

<tt>INTERFACES="-iwlan0"</tt>

and

<tt>DRIVERS="-Dwext"</tt>

have been changed to the appropriate settings for your wireless card. The above lines will likely work unless you need special drivers.

To make these settings stick, go back to the command line and enter

<tt>service wpa_supplicant restart</tt>

and

<tt>chkconfig wpa_supplicant on</tt>

6. Restart your network services.

Type

<tt>service network restart</tt>

Hopefully at this point you see a list of lines ending with [ OK ] and you can access web pages and other servers over your wireless connection.

If you are getting a [ FAIL ] result when interface wlan0 restarts, you may need to back up a few steps and work out how to connect to your wireless network using DHCP instead of static or without encryption enabled and then start working forward from there. Most of the steps on this page were worked out from one great resource, so it might be where you should start looking if you have further complications or need to start configuring at a more elementary level:
http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch13_:_Linux_Wireless_Networking

← Older revision		Revision as of 01:42, 18 May 2016
Line 1:		Line 1:
		+	{{NeedsUpdate}}
		+
		+
		+	{{MessageBox\|
		+	backgroundcolor = #faa\|
		+	image =Warning.png\|
		+	heading =WARNING\|
		+	message = This guidance was contributed for Fedora 14 '''ONLY'''! It will likely not work on any other Amahi version. Proceed at your own risk as we cannot provide any support}}
	It is not recommended to run an Amahi server over a wireless network connection. Quick response times are important when all the computers on a network are relying on your server for DNS queries and other functions, and wireless connections are not known for their reliability and optimal connection speeds. Many aspects of Amahi are not tested to run exclusively wireless.		It is not recommended to run an Amahi server over a wireless network connection. Quick response times are important when all the computers on a network are relying on your server for DNS queries and other functions, and wireless connections are not known for their reliability and optimal connection speeds. Many aspects of Amahi are not tested to run exclusively wireless.

@@ Line 9: / Line 9: @@
-. Tell Amahi that you're using wlan0 instead of eth0 so that it doesn't try to overwrite your changes.
+. Change a couple of config files so that Amahi knows what you're up to.
 Edit the file <tt>/usr/bin/hdactl</tt> and change the line
@@ Line 18: / Line 18: @@
    <tt>my $device = "wlan0"</tt>

Amahi over wlan0 - Revision history

Bigfoot65 at 01:42, 18 May 2016

Duke at 21:03, 27 June 2010

Duke: Created page with 'It is not recommended to run an Amahi server over a wireless network connection. Quick response times are important when all the computers on a network are relying on your serve…'