[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Dev Ramudit
Subject: Re: [Discuss-gnuradio] Problem with udp-sink/source over a network
Date: Fri, 06 Jul 2007 13:31:02 -0400
User-agent: Icedove (X11/20070329)

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)?

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.).


Discuss-gnuradio mailing list
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
./vector_source.py --dst-name=

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

I've tried reversing which host connects to the other, changing ports with the --src-port option, running the scripts in different orders, 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!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]