22 Sep
2010
22 Sep
'10
11:02 p.m.
Hello again!
Sorry, there's stilltrouble. Here's my setup:
on my sstem I opened and forwarded port 19000 as a UDP port. (I think it's
open to tcp as well).
Then I started jackd:
jackd -R --timeout 4500 -dnetone -i1 -o1 -r 48000 -l 19000
I'm running jack 1.9.7.
The other party is running Ubuntu's jack 0.116.1 and does:
jack_netsource -h ip -p 19000
But he can't connect to my system. I suggested -H, but it seems, he had
success with -h while testing on his local network. Any suggestions?
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
22 Sep
22 Sep
11:18 p.m.
New subject: Even more netjack trouble (although setup seems as described)
On Wed, Sep 22, 2010 at 5:02 PM, Julien Claassen <julien(a)c-lab.de> wrote:
Hello again!
Sorry, there's stilltrouble. Here's my setup:
on my sstem I opened and forwarded port 19000 as a UDP port. (I think it's
open to tcp as well).
Then I started jackd:
jackd -R --timeout 4500 -dnetone -i1 -o1 -r 48000 -l 19000
I'm running jack 1.9.7.
The other party is running Ubuntu's jack 0.116.1 and does:
jack_netsource -h ip -p 19000
But he can't connect to my system. I suggested -H, but it seems, he had
success with -h while testing on his local network. Any suggestions?
firewall on your or his system?
11:22 p.m.
New subject: Even more netjack trouble (although setup seems as described)
In Sep 22 A.D. 2010 Paul Davis scripsit:
On Wed, Sep 22, 2010 at 5:02 PM, Julien Claassen
<julien(a)c-lab.de> wrote:
Firewall on my system. Does he have to forward and open specific other ports
on his router/firewall as well? I thought, as I am the one waiting for a
connection, not initiatng it, I would be the one, taking care of this.
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
Hello again!
Sorry, there's stilltrouble. Here's my setup:
on my sstem I opened and forwarded port 19000 as a UDP port. (I think it's
open to tcp as well).
Then I started jackd:
jackd -R --timeout 4500 -dnetone -i1 -o1 -r 48000 -l 19000
I'm running jack 1.9.7.
The other party is running Ubuntu's jack 0.116.1 and does:
jack_netsource -h ip -p 19000
But he can't connect to my system. I suggested -H, but it seems, he had
success with -h while testing on his local network. Any suggestions?
firewall on your or his system?
28 Sep
28 Sep
12:25 p.m.
New subject: Even more netjack trouble (although setup seems as described)
On 09/22/2010 11:22 PM, Julien Claassen wrote:
In Sep 22 A.D. 2010 Paul Davis scripsit:
is this a local LAN connection?
asking since UDP over NAT routers requires port forwarding on all NAT
points.
On Wed, Sep 22, 2010 at 5:02 PM, Julien Claassen
<julien(a)c-lab.de> wrote:
Firewall on my system. Does he have to forward and open specific other
ports on his router/firewall as well? I thought, as I am the one waiting
for a connection, not initiatng it, I would be the one, taking care of
this. Hello again!
Sorry, there's stilltrouble. Here's my setup:
on my sstem I opened and forwarded port 19000 as a UDP port. (I think
it's
open to tcp as well).
Then I started jackd:
jackd -R --timeout 4500 -dnetone -i1 -o1 -r 48000 -l 19000
I'm running jack 1.9.7.
The other party is running Ubuntu's jack 0.116.1 and does:
jack_netsource -h ip -p 19000
But he can't connect to my system. I suggested -H, but it seems, he had
success with -h while testing on his local network. Any suggestions?
firewall on your or his system?
12:29 p.m.
New subject: Even more netjack trouble (although setup seems as described)
Hello Jörn!
So no matter if he initiates the connection, he will also need the correct
ports forwarded from his router?
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
12:42 p.m.
New subject: Even more netjack trouble (although setup seems as described)
On 09/28/2010 12:30 PM, Julien Claassen wrote:
Hello Jörn!
So no matter if he initiates the connection, he will also need the
correct ports forwarded from his router?
UDP is stateless, and there is no concept of "initiating a connection"
on the network layer. you basically send a UDP packet and hope it makes
it. the opposite end does the same.
so say we have this setup:
machine A: 192.168.0.2/24
router A: internal address 192.168.0.1/24, external address x.x.x.x
internet
router B: internal address 192.168.0.1/24, external address y.y.y.y
machine B: 192.168.0.2/24
router A must listen to the UDP port you want to use and forward each
packet to machine A.
router B must listen to the same port and forward to machine B.
say you're A. your partner host will then be y.y.y.y, i.e. the router.
since it's forwarding, you will be in effect talking to machine B.
same rules apply for the other direction.
it's advisable to run a testing tool for udp connections before you try
netjack. i recommend iperf, it's text-mode and available at sourceforge
iirc.
12:50 p.m.
New subject: Even more netjack trouble (although setup seems as described)
In Sep 28 A.D. 2010 Jörn Nettingsmeier scripsit:
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
On 09/28/2010 12:30 PM, Julien Claassen wrote:
Thank you very much. We'll do that and test netjack again. I think we will
have more luck this time. :-)
Warm regards
Julien
Hello Jörn!
So no matter if he initiates the connection, he will also need the
correct ports forwarded from his router?
UDP is stateless, and there is no concept of "initiating a connection" on the
network layer. you basically send a UDP packet and hope it makes it. the
opposite end does the same.
so say we have this setup:
machine A: 192.168.0.2/24
router A: internal address 192.168.0.1/24, external address x.x.x.x
internet
router B: internal address 192.168.0.1/24, external address y.y.y.y
machine B: 192.168.0.2/24
router A must listen to the UDP port you want to use and forward each packet
to machine A.
router B must listen to the same port and forward to machine B.
say you're A. your partner host will then be y.y.y.y, i.e. the router. since
it's forwarding, you will be in effect talking to machine B.
same rules apply for the other direction.
it's advisable to run a testing tool for udp connections before you try
netjack. i recommend iperf, it's text-mode and available at sourceforge iirc. 
1:15 p.m.
New subject: Even more netjack trouble (although setup seems as described )
On Tuesday 28 September 2010 12:52:14 Julien Claassen wrote:
In Sep 28 A.D. 2010 Jörn Nettingsmeier scripsit:
To make it easier, you (or your partner) could setup a public accessible
openvpn (probably with port forwarding as jörn described on the servers
side). Then you can just use the network of this vpn tunnel to use udp.
That way you only have to set up openvpn once and not fiddle with changing
port-numbers and changing apps every time again...
Have fun,
Arnold
On 09/28/2010 12:30 PM, Julien Claassen wrote:
Thank you very much. We'll do that and test netjack again. I think we
will have more luck this time. :-) So no matter if he initiates the connection, he
will also need the
correct ports forwarded from his router?
UDP is stateless, and there is no concept
of "initiating a connection" on
the network layer. you basically send a UDP packet and hope it makes it.
the opposite end does the same.
so say we have this setup:
machine A: 192.168.0.2/24
router A: internal address 192.168.0.1/24, external address x.x.x.x
internet
router B: internal address 192.168.0.1/24, external address y.y.y.y
machine B: 192.168.0.2/24
router A must listen to the UDP port you want to use and forward each
packet to machine A.
router B must listen to the same port and forward to machine B.
say you're A. your partner host will then be y.y.y.y, i.e. the router.
since it's forwarding, you will be in effect talking to machine B.
same rules apply for the other direction.
it's advisable to run a testing tool for udp connections before you try
netjack. i recommend iperf, it's text-mode and available at sourceforge
iirc.
1:18 p.m.
New subject: Even more netjack trouble (although setup seems as described )
Hello Arnold!
How man port do I need for netjack? I believe two: one for each direction.
Correct? At least with jack+_netsource you can specify two ports, one to
listen and one to reply. Or are they usually the same?
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
4961
days inactive
4967
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Arnold Krille -
Julien Claassen -
Jörn Nettingsmeier -
Paul Davis