HQPlayer's Network Audio Adapter

[sonata]

Are you planning to use the 32-bit system strictly as a NAA/MPD. For NAA you do not need any of the desktop management options so you could potentially strip it down even further but uninstalling unnecessary packages/services which will free up some additional resources.

 

I have followed a similar path. My DAC was natively supported by Ubuntu, not Debian. So I used a already minimised/slimmed down install of Ubuntu 14.04 available from https://help.ubuntu.com/community/Installation/MinimalCD

Then I followed the steps given by Miska here Index of /naa-install. This Linux installation has no GUI, but it runs fine on my old and slow 32Bit PC laptop.

 

Rob

[MikeJazz]

So if Miska's comment means that HQP 3.6.x is going to allow direct input of IP address (easy to see at boot time of NAA--even the text-only optimized Linux/NAA images for ARM and Intel from Miska--the lease IP shows in the last lines of the boot before the prompt), then that would be VERY good news for me and others who have been frustrated to date with NAA discovery.

 

Thant is also very good news to me that I would love to give HQ Player and NAA on Cubox another Go!

 

And now some lyrical wishful thinking:

 

1) Jesus decides to distribute Rendu on Europe with CE certification...

2) Jussi and Jesus talk and collaborate to find a way to make Rendu also a NAA. I know already that Rendu is not a computer, that is way this is such a good chalenge - those guys are up to the task!

[Miska]

I know that with GUI and such it's not as ideal, but Lubuntu 32-bit is all I have at the moment, apart from Raspbian on ARM. 32-bit Windows is not supported.

 

Now with NAA 3.x, you can use either Debian Jessie netinstall following roughly these instructions (a bit outdated, for older networkaudiod and Wheezy):

Index of /naa-install

Or alternatively you can go with Ubuntu Server 14.04 LTS, select nothing or at most OpenSSH when asked here:

and then go on to first do "sudo apt-get update ; sudo apt-get dist-upgrade". And then either do "sudo apt-get install linux-image-lowlatency linux-headers-lowlatency linux-tools-lowlatency" or install my kernel and libasound2 packages for native DSD support.

 

Then do "sudo apt-get install libasound2" to make sure you have necessary dependencies installed.

 

After this point, you can just install the relevant networkaudiod package using "dpkg -i networkaudiod_..."

 

Now you are ready to go, with either 32-bit or 64-bit version of the OS and networkaudiod.

 

 

P.S. OpenSSH server is useful for remotely performing the remaining steps or other maintenance tasks after initial installation. SSH client is included in Linux and OS X, for Windows one can find a client here.

[victor]

Thanks for the extra comments.

 

Hi Viktor,

I'm afraid we need to use port to see all multicast and traffic in both directions.

But her it looks like the naa don't receive the multicast request.

 

Cheers

Johan

 

I tried exactly as you did replacing your interface with mine (sudo tcpdump -n -i eth0 port 43210) and I got no output at all.

 

Then I followed shadowlight advise:

 

Victor,

 

Try changing the tcpdump command and remove the "not" before the host. It's been awhile with using tcpdump but if you use "not" option you are basically saying give me all information other than what is after the "not". So your command

 

tcpdump -i eth0 not host 192.168.1.11 is basically giving you all traffic generated and any traffic from 192.168.1.11 is not being displayed.

 

Personally, I prefer to run the tcpdump command with out any option and then review the result.

 

tcpdump -i eth0

 

Can you confirm that you have ip connectivity between the two system. Are you able to ping NAA from HQP and HQP from NAA.

 

Thanks for the extra information about tcpdump.

 

Both PCs have static IPs and the gateway set to the other PC's IP address (this time I changed the static ip addresses to the same that my DHCP gave me when connected to the router).

HQP IP: 192.168.1.45

NAA IP: 192.168.1.47

Both PCs are interconnected using an ethernet cable and I confirm that I am able to ping NAA from HQP and HQP from NAA using the IP addresses.

 

Hiding ssh output as I am accessing the NAA PC from the HQP PC using ssh, this is what I got:

 

0: Stop networkaudiod

 

1: Execute tcpdump in the NAA PC

 

tcpdump output in the NAA PC:

 

root@voyage:~# tcpdump -i eth0 port not 22

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

 

2: Execute tcpdump in the HQP PC

 

tcpdump output in the HQP PC:

 

victor@hqplayer:~$ sudo tcpdump -i eth0 port not 22

[sudo] password for victor:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

 

3: Start networkaudiod manually as root in the NAA PC to see log (no log appears apart from initial message saying that it started )

 

tcpdump output in the NAA PC:

 

08:01:33.863116 IP 192.168.1.47 > 224.0.0.22: igmp v3 report, 1 group record(s)

08:01:33.864725 IP 192.168.1.47.52247 > localhost.domain: 59789+ PTR? 22.0.0.224.in-addr.arpa. (41)

08:01:37.935160 IP 192.168.1.47 > 224.0.0.22: igmp v3 report, 1 group record(s)

08:01:38.868274 IP 192.168.1.47.52247 > localhost.domain: 59789+ PTR? 22.0.0.224.in-addr.arpa. (41)

08:01:43.873694 IP 192.168.1.47.50631 > localhost.domain: 23697+ PTR? 47.1.168.192.in-addr.arpa. (43)

08:01:48.878771 IP 192.168.1.47.50631 > localhost.domain: 23697+ PTR? 47.1.168.192.in-addr.arpa. (43)

08:02:35.510015 IP 192.168.1.45.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)

08:02:35.510476 IP 192.168.1.47.49643 > localhost.domain: 61907+ PTR? 251.0.0.224.in-addr.arpa. (42)

08:02:36.678940 IP6 fe80::1ec1:deff:feb2:7eb8.mdns > ff02::fb.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)

08:02:40.515585 IP 192.168.1.47.49643 > localhost.domain: 61907+ PTR? 251.0.0.224.in-addr.arpa. (42)

08:02:40.527113 ARP, Request who-has 192.168.1.45 tell 192.168.1.47, length 28

08:02:40.527349 ARP, Reply 192.168.1.45 is-at 1c:c1:de:b2:7e:b8 (oui Unknown), length 46

08:02:45.520975 IP 192.168.1.47.50684 > localhost.domain: 39995+ PTR? 45.1.168.192.in-addr.arpa. (43)

08:02:50.526151 IP 192.168.1.47.50684 > localhost.domain: 39995+ PTR? 45.1.168.192.in-addr.arpa. (43)

08:02:55.531819 IP 192.168.1.47.37306 > localhost.domain: 40381+ PTR? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)

08:03:00.536998 IP 192.168.1.47.37306 > localhost.domain: 40381+ PTR? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)

08:03:00.540228 ARP, Request who-has 192.168.1.47 tell 192.168.1.45, length 46

08:03:00.540255 ARP, Reply 192.168.1.47 is-at 00:27:0e:10:a9:08 (oui Unknown), length 28

08:03:05.542510 IP 192.168.1.47.35914 > localhost.domain: 25005+ PTR? 8.b.e.7.2.b.e.f.f.f.e.d.1.c.e.1.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)

08:03:10.547687 IP 192.168.1.47.35914 > localhost.domain: 25005+ PTR? 8.b.e.7.2.b.e.f.f.f.e.d.1.c.e.1.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)

 

tcpdump output in the HQP PC:

 

00:26:33.071632 IP 192.168.1.47 > 224.0.0.22: igmp v3 report, 1 group record(s)

00:26:33.073266 IP 192.168.1.47.52247 > localhost.domain: 59789+ PTR? 22.0.0.224.in-addr.arpa. (41)

00:26:37.143819 IP 192.168.1.47 > 224.0.0.22: igmp v3 report, 1 group record(s)

00:26:38.076959 IP 192.168.1.47.52247 > localhost.domain: 59789+ PTR? 22.0.0.224.in-addr.arpa. (41)

00:26:43.082562 IP 192.168.1.47.50631 > localhost.domain: 23697+ PTR? 47.1.168.192.in-addr.arpa. (43)

00:26:48.087829 IP 192.168.1.47.50631 > localhost.domain: 23697+ PTR? 47.1.168.192.in-addr.arpa. (43)

00:27:34.720544 IP 192.168.1.45.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)

00:27:34.721219 IP 192.168.1.47.49643 > localhost.domain: 61907+ PTR? 251.0.0.224.in-addr.arpa. (42)

00:27:35.889451 IP6 fe80::1ec1:deff:feb2:7eb8.mdns > ff02::fb.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)

00:27:39.726551 IP 192.168.1.47.49643 > localhost.domain: 61907+ PTR? 251.0.0.224.in-addr.arpa. (42)

00:27:39.738061 ARP, Request who-has 192.168.1.45 tell 192.168.1.47, length 46

00:27:39.738085 ARP, Reply 192.168.1.45 is-at 1c:c1:de:b2:7e:b8 (oui Unknown), length 28

00:27:44.732106 IP 192.168.1.47.50684 > localhost.domain: 39995+ PTR? 45.1.168.192.in-addr.arpa. (43)

00:27:49.737502 IP 192.168.1.47.50684 > localhost.domain: 39995+ PTR? 45.1.168.192.in-addr.arpa. (43)

00:27:54.743528 IP 192.168.1.47.37306 > localhost.domain: 40381+ PTR? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)

00:27:59.748905 IP 192.168.1.47.37306 > localhost.domain: 40381+ PTR? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)

00:27:59.751629 ARP, Request who-has 192.168.1.47 tell 192.168.1.45, length 28

00:27:59.751925 ARP, Reply 192.168.1.47 is-at 00:27:0e:10:a9:08 (oui Unknown), length 46

00:28:04.754569 IP 192.168.1.47.35914 > localhost.domain: 25005+ PTR? 8.b.e.7.2.b.e.f.f.f.e.d.1.c.e.1.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)

00:28:09.759961 IP 192.168.1.47.35914 > localhost.domain: 25005+ PTR? 8.b.e.7.2.b.e.f.f.f.e.d.1.c.e.1.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)

 

4: Start HQP in the HQP PC (ALSA mode by default)

 

No extra tcpdump log appears.

 

5: Select NAA in HQP

 

No extra tcpdump log appears.

 

6: Wait and wait and wait and nothing happens

 

7: Ctrl+C in both tcpdumps

 

tcpdump output in the NAA PC:

 

^C

20 packets captured

20 packets received by filter

0 packets dropped by kernel

 

tcpdump output in the HQP PC:

 

^C

20 packets captured

20 packets received by filter

0 packets dropped by kernel

 

 

Are you able to see what is happening?

 

I guess you haven't seen his comments and replies when I provided him the way to find more information about what Superdad and John Swenson are currently building as one of their next product?

 

Suit yourself.

 

I have not seen those comments, I just saw that I asked for help and he is trying hard to help me.

 

Cheers,

 

Victor.

[johann]

Are you able to see what is happening?

 

Rather what seem to not happen. It looks to me like the hqplayer never makes the multicast call to get hold of NAAs.

 

2 potential reasons spring to mind

 

1. Your interface(s) on your an host does not have multicast setup

 

2. You have some setup in iptables (or similar) blocking multicast

 

Can you do an ifconfig -a and sudo iptables -list -verbose on bot nodes?

 

Cheers

Johan

PS As for YashN, you can it judge it yourself by reading his posts if you want to waste your time.

[Miska]

So if Miska's comment means that HQP 3.6.x is going to allow direct input of IP address (easy to see at boot time of NAA--even the text-only optimized Linux/NAA images for ARM and Intel from Miska--the lease IP shows in the last lines of the boot before the prompt), then that would be VERY good news for me and others who have been frustrated to date with NAA discovery.

 

No, adding that would be big change on how NAA works, because it is now found based on it's high-level name instead address (address can change).

 

But I think I can add a "hidden" configuration option to the config XML that can be added manually to force HQPlayer to hook to a particular network interface since there seem to be some multicast routing issues with multiple network adapters.

[shadowlight]

Miska,

Any plans to add a 64-bit version of HQPlayer (for all OS) and NAA?

 

Edit:

I just looked at the 3.0 download directory and see Windows directory and I also see packages for 64bit related to NAA. Hopefully HQPlayer 64-bit is next.

[victor]

Rather what seem to not happen. It looks to me like the hqplayer never makes the multicast call to get hold of NAAs.

 

2 potential reasons spring to mind

 

1. Your interface(s) on your an host does not have multicast setup

 

2. You have some setup in iptables (or similar) blocking multicast

 

Can you do an ifconfig -a and sudo iptables -list -verbose on bot nodes?

 

Cheers

Johan

PS As for YashN, you can it judge it yourself by reading his posts if you want to waste your time.

 

Output from the NAA:

root@voyage:~# ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:27:0e:10:a9:08

inet addr:192.168.1.47 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: fe80::227:eff:fe10:a908/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:414 errors:0 dropped:0 overruns:0 frame:0

TX packets:319 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:54669 (53.3 KiB) TX bytes:36289 (35.4 KiB)

 

lo Link encap:Local Loopback

LOOPBACK MTU:65536 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

 

root@voyage:~# iptables --list --verbose

Chain INPUT (policy ACCEPT 128 packets, 13731 bytes)

pkts bytes target prot opt in out source destination

 

Chain FORWARD (policy ACCEPT 16 packets, 1104 bytes)

pkts bytes target prot opt in out source destination

 

Chain OUTPUT (policy ACCEPT 57 packets, 8404 bytes)

pkts bytes target prot opt in out source destination

root@voyage:~#

 

Output from the HQP:

 

victor@hqplayer:~$ sudo ifconfig -a

eth0 Link encap:Ethernet HWaddr 1c:c1:de:b2:7e:b8

inet addr:192.168.1.45 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: fe80::1ec1:deff:feb2:7eb8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:318 errors:0 dropped:0 overruns:0 frame:0

TX packets:487 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:36565 (36.5 KB) TX bytes:60369 (60.3 KB)

 

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:387 errors:0 dropped:0 overruns:0 frame:0

TX packets:387 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:28410 (28.4 KB) TX bytes:28410 (28.4 KB)

 

wlan0 Link encap:Ethernet HWaddr 00:26:82:b7:1d:75

BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:89 errors:0 dropped:0 overruns:0 frame:3904

TX packets:61 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:8933 (8.9 KB) TX bytes:10966 (10.9 KB)

Interrupt:17

 

victor@hqplayer:~$ sudo iptables --list --verbose

Chain INPUT (policy ACCEPT 231 packets, 29246 bytes)

pkts bytes target prot opt in out source destination

 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

 

Chain OUTPUT (policy ACCEPT 346 packets, 29122 bytes)

pkts bytes target prot opt in out source destination

victor@hqplayer:~$

 

Thanks again Johan, cheers

[Miska]

Miska,

Any plans to add a 64-bit version of HQPlayer (for all OS) and NAA?

 

Edit:

I just looked at the 3.0 download directory and see Windows directory and I also see packages for 64bit related to NAA. Hopefully HQPlayer 64-bit is next.

 

Linux version of HQPlayer is currently 64-bit only and 64-bit has been available as long as Linux version has been available.

 

OS X version has always been 64-bit only.

 

Windows version ships with both 32- and 64-bit versions and has been that way as long as I remember...

[johann]

Victor,

 

That looks ok.

 

Can you make sure you have a default route pointing to 192.168.1.1 and just any entry in /etc/resolv.conf,

for instance just:

 

nameserver 192.168.1.1

 

It doesn't matter if there is an DNS server responding or not.

 

Then I would need the output of netstat -rn & netstat -g

 

Cheers

Johan

[shadowlight]

I guess I missed the Windows x64 version. Will have to check which version I am evaluating.

[Superdad]

No, adding that would be big change on how NAA works, because it is now found based on it's high-level name instead address (address can change).

 

But I think I can add a "hidden" configuration option to the config XML that can be added manually to force HQPlayer to hook to a particular network interface since there seem to be some multicast routing issues with multiple network adapters.

 

That sounds good Jussi. Especially if it ultimately allows me to do an HQP/NAA setup between 2 Macs with just a straight Ethernet cable between them.

I guess you can now ignore the P.S. in the PM I sent you earlier this evening.

 

Best,

--Alex C.

[johann]

That sounds good Jussi. Especially if it ultimately allows me to do an HQP/NAA setup between 2 Macs with just a straight Ethernet cable between them.

 

There is nothing at all in the current implementation that prevents you from doing that already.

 

PS Your web site seems to be down

 

EDIT: Just tested, it works fine (without DNS and DCHP)

[shadowlight]

Just installed NAA 3.0.0 on a test system (minimal Ubuntu Server as mentioned earlier in the thread) and I see two instances of NAA showing up when I select name NAA. I guess one of the new feature is NAA instance listening on UDP.

[Superdad]

There is nothing at all in the current implementation that prevents you from doing that already.

 

PS Your web site seems to be down

 

EDIT: Just tested, it works fine (without DNS and DCHP)

 

Except that it has never worked for me. With OS X version of HQP on desktop, and either CuBox-i4Pro or i7 Mac mini as NAA (both using Linux/NAA images provided by Miska), the only way the player ever finds the NAA is if I run the NAA device's EN cable directly to my DSL router (though the desktop Mac can stay plugged into my Cisco EN switch). If both machines are plugged into my switch, the NAA boot (again the Linux provided by Miska) is too impatient to wait for a DHCP lease (to come from my DSL modem and through to the switch).

 

And as far as direct connection between HQP machine and NAA, I have tried both OS X's Internet Sharing (which essentially is just a GUI for "bootp"), and also bootp directly. Both work for me with other applications (i.e. the far device gets a lease from the desktop Mac), but HQ Player never finds the running NAA.

 

Miska has been aware of this for a while. I would love to find a simple solution to the issue, and I know that I am not alone in this. I will try again when the new version arrives.

 

I think your set up is different than mine in many ways.

[johann]

Except that it has never worked for me. With OS X version of HQP on desktop, and either CuBox-i4Pro or i7 Mac mini as NAA (both using Linux/NAA images provided by Miska), the only way the player ever finds the NAA is if I run the NAA device's EN cable directly to my DSL router (though the desktop Mac can stay plugged into my Cisco EN switch). If both machines are plugged into my switch, the NAA boot (again the Linux provided by Miska) is too impatient to wait for a DHCP lease (to come from my DSL modem and through to the switch).

 

The problem is not on HQP or NAA, it's either something you configured in the NAA or HQP device or something you missed to configure. So I don't think it's fair to ask for fixes in the application too solve problems in your setup.

 

So one problem problem is that your NAA device does not acquire an address from DHCP, right?

 

Just add a faster dhcp server somewhere in your network, add a sleep command in the naa startup script, login to the NAA device and re-start it or use fix ip addresses on your devices.

 

That should at least make things work in your normal network.

 

I think your set up is different than mine in many ways.

 

Not really, only difference is that my DHCP works and I get it to work as a complete standalone setup as well as in my normal network.

 

Is your target to:

 

1. Have both HPQ and NAA on a complete separate network (just a TP cable) without Internet?

 

2. Have a separate network (just a TP cable) between your HQP and NAA, where HQP is hooked up to your normal network.

 

3 Same as 2 but NAA also have Internet access via HQP device

 

4. All on your standard network

 

5 Something else

[Superdad]

The problem is not on HQP or NAA, it's either something you configured in the NAA or HQP device or something you missed to configure. So I don't think it's fair to ask for fixes in the application to solve problems in your setup.

 

So one problem problem is that your NAA device does not acquire an address from DHCP, right?

 

Just add a faster dhcp server somewhere in your network, add a sleep command in the naa startup script, login to the NAA device and re-start it or use fix ip addresses on your devices.

 

Is your target to:

 

2. Have a separate network (just a TP cable) between your HQP and NAA, where HQP is hooked up to your normal network.

 

 

Since #2 is my goal, the logical choice is to have the desktop Mac (the one running HQP) act as a DHCP server for the NAA. But while I CAN do that (the NAA gets an IP from the desktop Mac), HQP still does not "see" the NAA. And the Linux/NAA boot images I use are those provided to me preconfigured by Miska (for ARM and Intel). They just boot minimally to a prompt.

 

Alex C.

[jabbr]

Since #2 is my goal, the logical choice is to have the desktop Mac (the one running HQP) act as a DHCP server for the NAA. But while I CAN do that (the NAA gets an IP from the desktop Mac), HQP still does not "see" the NAA. And the Linux/NAA boot images I use are those provided to me preconfigured by Miska (for ARM and Intel). They just boot minimally to a prompt.

 

Alex C.

 

You do realize that you are doing very unusual things with your network and asking Miska to read your mind

 

Multi-homed is tricky and you may need to set up routing tables.

You are also asking your ADSL modem to be your DHCP server!

 

What I do at home is have a separate firewall/router device which acts as a DHCP server and ties together my distinct networks, including wireless.

[johann]

Since #2 is my goal, the logical choice is to have the desktop Mac (the one running HQP) act as a DHCP server for the NAA. But while I CAN do that (the NAA gets an IP from the desktop Mac), HQP still does not "see" the NAA. And the Linux/NAA boot images I use are those provided to me preconfigured by Miska (for ARM and Intel). They just boot minimally to a prompt.

 

I had tested case 1 & 4 before without any special config at all.

 

With fix IP addresses, for case 2, you just need to get MULTICAST route correct and for 3 you need to enable ip forwarding in the kernel of your HQP device as well as adding a route to your new network your default router (most likely your ISP-router).

 

Using Internet sharing in OS X creates a bridge to your new network so while you don't have to enable IP forwarding and routes in your router and multitask over bridges should work, it is more complicated to get the multicast route to work.

 

Apart from your lousy dhcp, which really is trivial to fix, why don't you want to go with case 4?

[johann]

Alright, solved for case 2 above using OS X Internet sharing.

 

Alex, what is worth to you?

[bibo01]

Now with NAA 3.x, you can use either Debian Jessie netinstall following roughly these instructions (a bit outdated, for older networkaudiod and Wheezy):

Index of /naa-install

Or alternatively you can go with Ubuntu Server 14.04 LTS, select nothing or at most OpenSSH when asked here:[ATTACH=CONFIG]16250[/ATTACH]

and then go on to first do "sudo apt-get update ; sudo apt-get dist-upgrade". And then either do "sudo apt-get install linux-image-lowlatency linux-headers-lowlatency linux-tools-lowlatency" or install my kernel and libasound2 packages for native DSD support.

 

Then do "sudo apt-get install libasound2" to make sure you have necessary dependencies installed.

 

After this point, you can just install the relevant networkaudiod package using "dpkg -i networkaudiod_..."

 

Now you are ready to go, with either 32-bit or 64-bit version of the OS and networkaudiod.

 

 

P.S. OpenSSH server is useful for remotely performing the remaining steps or other maintenance tasks after initial installation. SSH client is included in Linux and OS X, for Windows one can find a client here.

Are you going to prepare an ISO from it for the CuBox?

[victor]

I'm not at home. Tonight I will test the new suggestions and report back.

 

Thanks again!

[Miska]

Are you going to prepare an ISO from it for the CuBox?

 

At some point when I have time... It requires update to the kernel and libasound2 to have advantages over previous version (IOW, to support non-DoP DSD) and doing all that for the image takes some time.

[jabbr]

You do realize that you are doing very unusual things with your network and asking Miska to read your mind

 

Multi-homed is tricky and you may need to set up routing tables.

You are also asking your ADSL modem to be your DHCP server!

 

What I do at home is have a separate firewall/router device which acts as a DHCP server and ties together my distinct networks, including wireless.

 

How about trying something very simple like this: WRT54GL which could be run off a 12v/0.5A linear power supply. Uses Broadcom SOC and runs Linux. It will give you 4 Ethernet ports for your home router.

[jabbr]

At some point when I have time... It requires update to the kernel and libasound2 to have advantages over previous version (IOW, to support non-DoP DSD) and doing all that for the image takes some time.

 

Where can NAA 3.x be found -- the netaudiod is version 2.05?