hi,
we will like to understand why our OSCdump tests are failing.
since the object just needs one argument (the port)
[dumpOSC 54321] | | [print test]
as don't see the port 54321 being opened in the syslog and nmap doesn't show it as an open port we cannot be sure why data still passes by when we try via localhost:
[send localhost 54321( | [sendOSC]
and messages are passing.
next step is to check the firewall, turn it off or allow packets to via the port 54321 in the corresponding IP. but still no flow from external packages.
what else can we try to debug and understand where is that the packects are being trapped?
suggestions for linux, os x and windows are welcome since we have tried in those 3 platforms and from different places/countries with no luck yet.
tx!
/alejo
Start pd and add [dumpOSC 5678]
now try in a console
lsof | grep pd | grep UDP
if a handle is visible you will see something similar as
pd 4563 puredata 11u IPv4 12695 UDP *:5678
On Thu, 28 Jun 2007 01:27:14 +0200 "alejo d" alejoduque@gmail.com wrote:
hi,
we will like to understand why our OSCdump tests are failing.
since the object just needs one argument (the port)
[dumpOSC 54321] | | [print test]
as don't see the port 54321 being opened in the syslog and nmap doesn't show it as an open port we cannot be sure why data still passes by when we try via localhost:
[send localhost 54321( | [sendOSC]
and messages are passing.
next step is to check the firewall, turn it off or allow packets to via the port 54321 in the corresponding IP. but still no flow from external packages.
what else can we try to debug and understand where is that the packects are being trapped?
suggestions for linux, os x and windows are welcome since we have tried in those 3 platforms and from different places/countries with no luck yet.
tx!
/alejo