Wiretap (Read Only)
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Mac API beta not seeing Wiretap 1.7

17 REPLIES 17
Reply
Message 1 of 18
alatteri
640 Views, 17 Replies

Mac API beta not seeing Wiretap 1.7

SGI Flame 9.5.13.
When running the FAT tools in the latest API beta it is unable to see this machine. The old PPC only tools work fine. I have tested this at multiple sites.

Current API
milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api/tools/Mac/OSX/wiretap_server_dump -v
Failed to acquire server list from interface 192.168.1.2 : Unknown host 'flame'
Error acquiring the number of nodes: Failed to acquire a server list from any interfaces

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api/tools/Mac/OSX/wiretap_ping -h 192.168.1.3
Ping to WireTap host '192.168.1.3' successful.


Beta API

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_server_dump -v
Unable to acquire the server list: Device not configured

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_ping -h 192.168.1.3
Ping to WireTap host '192.168.1.3' failed: Device not configured.
17 REPLIES 17
Message 2 of 18
labuted
in reply to: alatteri

Hi Alan,

We added some support for IPv6 in the beta. Can you try it with the hostname instead of the IP?

Aside, I'm assuming it works with beta 2007.1 servers, right?

Dan
Message 3 of 18
alatteri
in reply to: alatteri

I will try this: but it is not a viable workaround as that would require either an internal DNS server or an entry in the client hosts file, neither of which is friendly or double click usable. yes, 2007 is fine.
Message 4 of 18
labuted
in reply to: alatteri

Hi Alan,

The hostname fix is one workaround. Another is to use the new syntax as follows:

wiretap_ping -h 192.168.1.1:7549

This targets the port number and bypasses a new bit of code added to handle the case where multipl eservers are present on a single host.

Aside, I find it odd that you're nding up with IP addresses via multi-cast for 1.7 servers. 1.7 servers only know how to broadcast their hostnames. Are you specifying the IPs manually, or are you using what is provided by the server list?

This problem actually exists on all platforms. A fix should be available in the final release due out shortly.

Dan
Message 5 of 18
alatteri
in reply to: alatteri

Not working either.

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_ping -h 192.168.100.50:7549
Ping to WireTap host '192.168.100.50:7549' failed: Operation timed out.
milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_ping -h 192.168.100.50
Ping to WireTap host '192.168.100.50' failed: Host is down..
milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink.quicktime/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_server_dump
WireTap Servers Storage ID Plug-In
--------------------------------------------------------------------------------------
Message 6 of 18
alatteri
in reply to: alatteri

sw_wiretap_ping on the SGI reports successful.
Message 7 of 18
alatteri
in reply to: alatteri

forget that, it worked. crappy SGI just needed a reboot.
Message 8 of 18
Anonymous
in reply to: alatteri

Good.

This is all fixed in the release version (2007.1) coming soon, so no workaroung necessary.
Message 9 of 18
alatteri
in reply to: alatteri

Hey, so i am still having an issue with the release SDK.

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_server_dump
WireTap Servers Storage ID Plug-In
--------------------------------------------------------------------------------------
discreet 192.168.1.55 IFFFS-55 Autodesk IFFFS 2007.0.0
flame flame Discreet IFFFS @ mprel - Product_2766 1.7.0

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_resolve_storage_id -s flame
flame

milky-way:~ alatteri$ /Users/alatteri/Documents/Code/shrink/wiretap/api-beta/tools/MACOSX/fat/Darwin_8_3_0/wiretap_ping -h 192.168.1.3
Ping to WireTap host '192.168.1.3' failed: Device not configured. Message was edited by: alatteri
Message 10 of 18
Anonymous
in reply to: alatteri

Hi Alan,

This is a bit surprising. We'll double-check in the AM, but you might want to make sure you're actually using the latest SDK. I know, it's like asking to make sure you're computer is pluggged-in. 🙂

BTW, all WT developers should have a way to show the API version and build number in their products. This will help us troubleshoot problems seen in the field when customers call our support line.

You might also want to try to download the official version from ADN.

Dan
Message 11 of 18
alatteri
in reply to: alatteri

Yeah, those were the release tools, just didnt update our code yet so i overwrote the old API. Anyway, i tried again directly from a fresh download. Same result.

milky-way:~ alatteri$ /Users/alatteri/Desktop/wiretapapi-sw20071-1038/tools/MACOSX/fat/Darwin_8_3_0/wiretap_server_dump
WireTap Servers Storage ID Plug-In
--------------------------------------------------------------------------------------
discreet 192.168.1.55 IFFFS-55 Autodesk IFFFS 2007.0.0
flame flame Discreet IFFFS @ mprel - Product_2766 1.7.0

milky-way:~ alatteri$ /Users/alatteri/Desktop/wiretapapi-sw20071-1038/tools/MACOSX/fat/Darwin_8_3_0/wiretap_resolve_storage_id -s flame
flame

milky-way:~ alatteri$ /Users/alatteri/Desktop/wiretapapi-sw20071-1038/tools/MACOSX/fat/Darwin_8_3_0/wiretap_ping -h 192.168.1.3
Ping to WireTap host '192.168.1.3' failed: Device not configured.

milky-way:~ alatteri$ /Users/alatteri/Desktop/wiretapapi-sw20071-1038/tools/MACOSX/fat/Darwin_8_3_0/wiretap_ping -h 192.168.1.3:7549
Ping to WireTap host '192.168.1.3:7549' successful.

milky-way:~ alatteri$ ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3): 56 data bytes
64 bytes from 192.168.1.3: icmp_seq=0 ttl=255 time=0.914 ms
64 bytes from 192.168.1.3: icmp_seq=1 ttl=255 time=0.958 ms
^C
--- 192.168.1.3 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.914/0.936/0.958/0.022 ms
Message 12 of 18
Anonymous
in reply to: alatteri

I'm assuming that hard-coding ":7549" still works as a workaround, right?
Message 13 of 18
alatteri
in reply to: alatteri

yeah.
Message 14 of 18
Anonymous
in reply to: alatteri

Hi Alan,

We definitely can reproduce the bug in house with an older version, and it's definitely fixed in the new version. At this point, I suspect that you don't have the most recent version.

Can you please verify the name of the SDK file, as well as the contents of the WIRETAP_VERSION and PRODUCT_NUMBER files included in the SDK.

Can you also send me the link from which you downloaded the SDK from ADN? The one below seems to have an old version:

http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=7478536

Dan
Message 15 of 18
alatteri
in reply to: alatteri

I was using a fresh download from the link that Craig Dean provided in his ADN email.

http://adnsparks.autodesk.com/adn/servlet/index?siteID=6681818&id=745120
2&linkID=6928614

Also tried the specific wiretap_ping binary you sent me via email too.
Message 16 of 18
alatteri
in reply to: alatteri

I just tried it again at another facility also using SGI Flame 9.5, same result.
Only works when I append the port number. Again, using the wiretap_ping binary you sent me via email.


milky-way:~ alatteri$ /Users/alatteri/Desktop/wiretap_ping -h 192.168.10.56
Ping to WireTap host '192.168.10.56' failed: Device not configured.

milky-way:~ alatteri$ /Users/alatteri/Desktop/wiretap_ping -h 192.168.10.56:7549Ping to WireTap host '192.168.10.56:7549' successful.
Message 17 of 18
Anonymous
in reply to: alatteri

Now that we established that the version posted has the fix in question after all, we just need to figure out why this particular case is still problematic.

My thinking is that it's a plain old multi-cast issue. The simple steps to troubleshoot are to make sure multi-cast is enabled on the target network by pinging 224.0.0.1 as is is outlined in the FAQ. Most routers do not turn on multicast by default.

FYI, the difference between the old and new APIs is that we now always peform a multi-cast when the port number is not specified. The port number was added to the address in v2007.1 to support multiple WT servers on a given host.

Cheers,

Dan
Message 18 of 18
alatteri
in reply to: alatteri

I forgot where we left off with this prior to NAB. My opinion, is that what used to work, got broken in API 2007.1 providing me customers with a less appealing solution. As a recap, Wiretap 1.7 servers are not auto-discovered unless Internal DNS is running, which most places do not have. I have tested the networks and it is fine, multi-cast pings properly, and Wiretap 2007 servers are auto-discovered as expected.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report