On Sat, May 22, 2010 at 11:15:35PM +0200, fons@email-addr-hidden wrote:
> On Sat, May 22, 2010 at 01:39:55PM -0700, Grant wrote:
>
> > > Well, you could put an extra nic in each computer and use netjack over that
> > > while keeping the traffic off of the normal local network.
> >
> > That would require setting one of the systems up as a router right?
>
> No, you just have to configure the interfaces, and add a route
> to make the netjacks use them instead of following the default
> route via the existing interface.
> There's no traffic being routed between the two interfaces on
> each machine, so they are not routers. The audio connection is
> just an isolated network.
>
Actually, if you have two interfaces on a local, private network, there's no need to configure the routing at all.
i.e.
Machine 1: 192.168.77.1
Machine 2: 192.167.77.2
You don't have to set up any special route in order to ping machine 1 from machine 2, or vice versa. So audio-only won't require a route.
If the regular internet address of machine 1, is, say, 192.168.1.100, and its default route is 192.168.1.1, all internet traffic will still work perfectly. This of course assumes you're using Class C addresses as above.
However, you'd require setting up a route if either of the machines doesn't have an internet connection of its own, also turningon ip_forward, setting up /etc/resolve.conf, etc etc.,.
-ken
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Mon May 24 08:15:02 2010
This archive was generated by hypermail 2.1.8 : Mon May 24 2010 - 08:15:02 EEST