Re: [Discuss-gnuradio] Problem with udp-sink/source over a network

[Bart Mermuys]

Hi,

> Tom Rondeau wrote:
> > Dev Ramudit wrote:
> >
> > > Tom Rondeau wrote:
> > >
> > > > What port are you trying to use? Have you tried to run your scripts
> > > > between machines on the same network (that is, same subnet; not through
> > > > a router or anything)?
> > > >
> > > > Tom
> > > I've generally tested with the 65500 port that the scripts have, but
> > > I've also changed this to 13421 (and a couple of others) with the same
> > > problem. I've tested on machines in the same network and subnet, which
> > > are all able to see each other and connect to other ports through
> > > other applications. Has anyone else tried running the vector_source.py
> > > and vector_sink.py scripts remotely? Just want to clarify if this is
> > > an issue with my setup
> >
> > I'm not sure what you mean when you say you're running the scripts
> > remotely? If you just mean running the source on one computer and the
> > sink on another, then yes, I tested them out on my network. I had two
> > computers taking with static IPs on a GigE switch. I've not tried to go
> > through a router or gateway, though I don't see why that wouldn't work
> > (sans firewalls, proxy's, etc.).
> >
> > Tom
> >
> >
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

> Thanks for the response Tom, that's exactly what I was looking for. I have 
> the same setup (no routers or NAT-ing involved). Running vector_sink on 
> either and running vector_source on the other gives the same error 
> message. I'm running:
>
> on host 9.8.7.1:
> ./vector_source.py --dst-name=9.8.7.2
>
> on host 9.8.7.2:
> ./vector_sink.py --src-name=9.8.7.2

Have you tried the following ?

on host 9.8.7.1:
./vector_source.py --dst-name=9.8.7.2 --src-name=9.8.7.1

on host 9.8.7.2:
./vector_sink.py --src-name=9.8.7.2

vector_source uses udp_sink, which explicitly binds before calling connect 
which requires you to pass the correct source IP, which I believe must be 
the IP of the NIC that's going to be used to reach the destination address, 
though 0.0.0.0 may work too, but not the default "localhost".

> I've tried reversing which host connects to the other, changing ports with 
> the --src-port option, running the scripts in different orders,

Technically UDP doesn't connect.  vector_source which uses udp_sink sends 
data, while vector_sink uses udp_source which receives data.  There is no 
real connection being made.  The connect and bind calls only associate local 
and remote endpoints with the socket for use in subsequent recv or send 
calls.

Greetings
Bart Mermuys

> etc. I'm running debian on one host and fedora on the other, and I've 
> disabled the firewall on both machines. Going to keep trying to figure it 
> out, thanks for all the responses so far!
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio