installation on a laptop w/ wireless

[asid777]

After install HDA was not working and the DHCP/DNS was broken for the network. I did some reading/troubleshooting and I believe the cause of my problem could be the networking on my laptop.

Laptop has a wireless (eth0) and wired (eth1)
Integrated 2wire DSL/Wireless router

During fedora install I picked eth1 and I was able to install the os and the amahi software/scripts from the repo.

After reboot, I turned the dhcp/dns of my DSL/Wireless router -- and rebooted all devices. Internet connectivity stoped working as I could not resolve dns.

Did some research and I read that Amahi is not supported on eth1

Question : Is it possible to run Amahi on a wireless eth0 ? Any possible options/alternatives for me try ??

[kdoswald]

Just reverse eth0 and eth1.

Go into /etc/sysconfig/networking/devices

Will be two files ifcfg-eth0 and ifcfg-eth1
rename 1 0 and 0 1
Edit the files and change the line
device=eth1 to eth1 and visa versa.

It links the eth0 by the line HWADDR.

I had to do this on centos because nic died at work few weeks ago.

[cpg]

exactly. that is the simplest.

except this may or may not work, depending on the device. you may also need to change

Code: Select all

/etc/udev/rules.d/70-persistent-net.rules

otherwise, you may (*may*) only need to change /usr/bin/hdactl, line 21:

Code: Select all

my $device = "eth0";

and change that to eth1, then reboot.

obviously not the two things at the same time.

[asid777]

Should I rebuild the system/fedora os and do this before running amahi-installer? I have tinkered with the network-manager and tried to change eth1->eth0...but even though it looked like it would work, it did not when I did ifconfig

So I take it eth0/wireless is not supported ?

[cpg]

well, eth0 *is* supported.

i did an install once with a network adapter that showed as eth0 but it was bridging to the network transparently via a wireless link, so it was transparent to amahi/fedora.

usually, "wireless" means wifi and usual comes up at wlan0 ... so we need more details ...

if you can reinstall armed with this information (turn off the wireless part perhaps to make it easier?), that's best.

[asid777]

I rebuilt fedora12. There were no files in /etc/sysconfig/networking/devices.

Just reverse eth0 and eth1.

Go into /etc/sysconfig/networking/devices

Will be two files ifcfg-eth0 and ifcfg-eth1
rename 1 0 and 0 1
Edit the files and change the line
device=eth1 to eth1 and visa versa.

It links the eth0 by the line HWADDR.

I had to do this on centos because nic died at work few weeks ago.

[asid777]

MyHDA has a wireless (WIFI) that shows up as eth0 in ifconfig
and a Ethernet network that shows up as eth1 by default.

well, eth0 *is* supported.

i did an install once with a network adapter that showed as eth0 but it was bridging to the network transparently via a wireless link, so it was transparent to amahi/fedora.

usually, "wireless" means wifi and usual comes up at wlan0 ... so we need more details ...

if you can reinstall armed with this information (turn off the wireless part perhaps to make it easier?), that's best.

[cpg]

I rebuilt fedora12. There were no files in /etc/sysconfig/networking/devices.

weird. my server has a file there called ifcfg-eth0.

[asid777]

I changed the /usr/bin/hdactl to eth1 and its progress... HDA came up with the correct (static) IP and I am able to access the HDAdashboard.


I believe this setup is not supported... Not sure why.... if all the code uses the defined variables... it should be good.

Thanks for your help.

exactly. that is the simplest.

except this may or may not work, depending on the device. you may also need to change

Code: Select all

/etc/udev/rules.d/70-persistent-net.rules

otherwise, you may (*may*) only need to change /usr/bin/hdactl, line 21:

Code: Select all

my $device = "eth0";

and change that to eth1, then reboot.

obviously not the two things at the same time.

[cpg]

it's not supported because we are a small team, it would have to be documented and it would have to be autodetected or somehow code would need to be added to change that. if you would like to help document and test this configuration, it would be very useful and much welcome.
(99% of users have only one NIC (eth0) ...)