It took me some time to figure out how to get the wireless device of my Amilo Li 2727 working with Windows 7. For the ones who stumble across the same problem I have describe how to solve it.
- Download the Windows XP Drivers For Amilo Li 2727 here
- Extract the contents of the compressed file
- Open ‘Control Panel’, click on ‘System’ and choose ‘Device Manager’
- Open the ‘Action’ menu item and click on ‘Add legacy hardware’
- Next -> Next -> Next and pick ‘Network Adapters’
- Choose ‘Have disk’ and Navigate into the ‘04 WLAN’ directory
- Select ‘Atheros AR5007EG Wireless Network Adapter’
- Install the FSC Launchmanager from the ‘05 FSC_LaunchManager’ directory by executing the setup.exe
- Reboot
Once you have rebooted you should have a working wireless device. To active the wireless device, you need to press the Fn+F1 button combination and choose WLAN. I can confirm this driver works on Windows 7.
Good luck!
Recently I had to use a laptop for a course I was doing. This Fujisu Siemens Amilo Li 2727 laptop came with Windows Vista pre-installed. Since the installed OS didn’t matter for the course I installed the latest Ubuntu which is 9.04 (Jaunty). All worked well except for the wireless card (Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 04)). The ath5k driver for the wireless card is being correctly initialised, as you can see:
[ 12.170260] ath5k_pci 0000:08:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 12.170274] ath5k_pci 0000:08:00.0: setting latency timer to 64
[ 12.170439] ath5k_pci 0000:08:00.0: registered as ‘phy0′
[ 12.355693] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0×70)
[ 264.864848] ath5k phy0: noise floor calibration timeout (2442MHz)
It appears that the wireless card is enabled but not activated, so you’ll need to turn it on. Using Windows you use the Fn-F1 key combination to activate the wireless card, but this doesn’t work with Linux. The easiest way to get wireless going is by activating a kernel module called acer_wmi. As soon as you execute the following line you’ll notice the wireless led will light up. There are other ways, but this is by far the most easy and elegant way to do it.
The wireless card is now active! Wait a moment and you’ll see wireless networks appear in the NetworkManager if you’re in range. Just for the record I am using Ubuntu kernel 2.6.28-11-generic at the moment of writing.
To make this solution last on a reboot, you’ll have to add the module name ‘acer_wmi’ to ‘/etc/modules’.
$ sudo echo "acer_wmi" >> /etc/modules
Today I decided it was time to introduce my iPhone to the campus wireless network, instead of using the slow GPRS network of my carrier. I’m still a happy user of the first generation iPhone, so I’m stuck with GPRS and that’s why I like WIFI.
So I downloaded the already made VU-iphone.mobileconfig file to my workstation and fired up my favorite MUA, what happens to be Mozilla Thunderbird to mail the configuration as a attachment, just like the way the online manual described. But as soon as I opened up the mail app on the phone the message looked like normal text and there was no attachment to open. I decided to use Mutt as an alternative and repeated the steps described above. This time the attachment showed up as it should be. So I was able to import the wireless configuration and finished the wireless setup.
Now I’m happy being wireless connected but still curious why the attachment send by Thunderbird did not show up correctly in the mobile mail app. So I compared both mail clients MIME behaviour and it appears that Thunderbird is not behaving correctly according to rfc2183. As you can see it uses Content-Disposition type ‘inline’ instead of the correct ‘attachment’ type.
I have stripped the irrelevant header and body information of the message.
Thunderbird:
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="————070008030904000701030203"
This is a multi-part message in MIME format.
————–070008030904000701030203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
————–070008030904000701030203
Content-Type: text/xml;
name="VU-iphone.mobileconfig"
Content-Transfer-Encoding: 7bit
<strong>Content-Disposition: inline;</strong>
filename="VU-iphone.mobileconfig"
Mutt:
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="WIyZ46R2i8wDzkSu"
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
–WIyZ46R2i8wDzkSu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
–WIyZ46R2i8wDzkSu
Content-Type: text/plain; charset=us-ascii
<strong>Content-Disposition: attachment;</strong> filename="VU-iphone.mobileconfig"
This looks like a bug..
As mentioned earlier I would post my wireless configuration of the Cisco 877W router as soon as I got it to work the way I like. In this setup the commonly used IRB bridge option is not used. This configuration will also work on the 857W model.
!
dot11 ssid <your ssid>
vlan 2
authentication open
authentication key-management wpa
guest-mode
wpa-psk ascii 0 <your password>
!
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.2.1
!
ip dhcp pool wireless
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
dns-server <dns server> <dns server>
!
interface Dot11Radio0
no ip address
!
encryption vlan 2 mode ciphers tkip
!
ssid <your ssid>
!
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
channel least-congested 2412 2442 2462
station-role root
no cdp enable
!
interface Dot11Radio0.1
description WLAN vlan2
encapsulation dot1Q 2
ip address 192.168.2.1 255.255.255.0
ip nat inside
ip virtual-reassembly
no cdp enable
!
interface Vlan2
no ip address
!
On the (outside) dialer0 interface I had to add the following line to enable NAT:
And at last you’ll need the next ip nat and access-list lines to make it work:
ip nat inside source list 103 interface Dialer0 overload
access-list 103 remark Traffic allowed to enter the router from the WLAN
access-list 103 permit 192.168.2.0 0.0.0.255
You can use the show dot11 or debug dot11 commands to troubleshoot. For example, the following output displays a associated device:
router#show dot11 associations
802.11 Client Stations on Dot11Radio0:
SSID [<your ssid>] :
MAC Address IP address Device Name Parent State
xxxx.xxxx.xxxx 192.168.2.2 unknown - self Assoc
router#
Enjoy being wireless!
This is how I configured my iPhone to connect to Eduroam 802.1x at SARA.
Download and install the Apple iPhone Configuration Utility. You can find this utility on the Apple support pages. Download the following certificates SURFnet-PCA-Root-CA and SARA-KA (check the Active Directory Certificate Services server).
Startup your browser after installing the iPhone Configuration Utility and open http://localhost:3000. Login with admin/admin and add some relevant information to the four fields at the General tab.
Next you need to install the two certificates on the Credentials tab. Maybe you need to rename the certificate file name extension to .cer.
Set the following on the Wi-Fi tab:
Service Set Identifier (SSID): eduroam
Security Type: WEP Enterprise
Protocols tab
select as accepted EAP type: PEAP
Authentication tab
username: your KA username
Inner Authentication: MSCHAPv2
Trust tab
Trusted Certificates:
select the two added certificates:
SURFnet-PCA-Root-CA
SARA Kantoorautomatisering
Allow Trust Exceptions: Checked
On the General tab use the ‘Export Profile’ button to export the just created configuration to a file. Sent this file by email to an email account you have configured on your iPhone. Open the email and install the profile and your’re done. You should now have a eduroam connection!
For more information look for the ‘Enterprise_Deployment_Guide.pdf’.