[byronl]

I'm running Frodo 12.2 on two older ATVs (4.3 I think) and I was having some NFS issues to my Hanewin NFS Server some months back. The NFS Server is completely reliable with 12.2 on my windows HTPC so I was focussing on ATV2/XBMC as the problem.

One thing I did was force a fixed IP address on both ATVs to force NFS access to the server from a defined port range, rather than having it open.

This seemed to work fine.

Recently both ATVs were off whilst we were on holiday and after re-powering all of a sudden we are having NFS access issues to the Hanewin server. NFS to the NAS (ReadyNAS) is ok.

A bit of investigation shows that both ATVS have 2 IP addresses now. eth0 and eth1.

XBMC shows the correct address, but I'm guessing that somehow the wireless has been enabled again. I've repowered both ATVs multiple times but it persists.

I was under the impression that a wired connection automatically disabled the wireless?

Anyone know how to force wireless to be disabled?

NOTE: I'm not sure if this is the source of the issues, but it can't be helping.

I'll go in and revert to DHCP tonight and see if it helps.

Thanks

Byron

[Memphiz]

I was under the impression that a wired connection automatically disabled the wireless?

Yes i am under this impression too. Try to unplug and replug your ethernet cable when the ATV2 is running.

[byronl]

I reverted to DHCP thinking perhaps it was the cause, but no change.
I tried plugging/unplugging the Ethernet cable whilst running, but no change.

The NFS Access is working at appears to come en0 (sorry not eth0) only. So I'm not sure what the address on en1 is. It's definitely on both ATV2s and I can putty in on both.

Perhaps it's just a curiosity and nothing more.

Apple-TV-Kids:~ root# /sbin/ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.23 netmask 0xffffff00 broadcast 192.168.1.255
ether 28:e7:cf:e3:95:c6
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.60 netmask 0xffffff00 broadcast 192.168.1.255
ether 28:e7:cf:e3:95:c5



Apple-TV-Bed-1:~ root# /sbin/ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.49 netmask 0xffffff00 broadcast 192.168.1.255
ether b8:17:c2:c3:ee:92
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.48 netmask 0xffffff00 broadcast 192.168.1.255
ether b8:17:c2:c3:ee:91

[Memphiz]

Haveing to interface addesses in the same subnet is likely to give you even more issus. I wonder how the default route on that config would look like.

[byronl]

Everything seems stable since I went back to DHCP.

I'll have a fiddle with the default routes and see what I can find.

Ideally I could just disable en1, but I'm reluctant to fiddle too much.

B