[AG-DEV] node services connecting via a unicast bridge?

[Thomas D. Uram]

This should be working.  When the client enters, the agdevicecontrol stream 
should be allocated, and the BridgeServer should create a bridge for it, 
advertising it in the agdevicecontrol StreamDescription.  I assume this is 
working correctly, and the devicecontrol service gets the bridge address.

The underlying QuickBridge is noisy to stdout; you could try watching that 
output to see if it acknowledges the client.  If that's in order, I'd try 
watching traffic out of the bridge machine (using ethereal) as a start.

Tom


On 9/20/05 8:11 PM, Darran Edmundson wrote:
> 
> Hi All,
> 
> We've encountered a problem with AGDeviceControl when run on a node  
> connecting
> via a unicast bridge.  If you look at our node service script:
>     http://trac.agcentral.org/AGDeviceControl/file/trunk/ 
> agdevicecontrol/AGTk/DeviceControlService.py
> 
> you'll see that we define an agdevicecontrol producer stream.   This  
> gives us a multicast
> group and port over which we do AGDeviceControl heartbeat and  
> discovery.  This works
> beautifully for multicast-connected nodes.  However, nodes connected  
> via a unicast
> bridge are not receiving heartbeats.  We have verified this with an  
> Ethereal packet
> dump.  Namely, vic and rat streams are coming through but not our  
> custom agdevicecontrol
> traffic.  Surely the bridge routes all streams, no?
> 
> Cheers,
> Darran.
> 
>