help getting off the ground

Dave Randolph drandolph at nstarbank.com
Wed Sep 22 12:10:46 PDT 2010


Hi.
I'm running the 6.2 release and trying to proxy some SAN replication traffic.  Here's my setup.


SAN-A         -> WanproxyA       -> WAN -> WanproxyB                    ->SAN-B
192.168.24. x    192.168.24.1(LAN)             192.168.24.129(LAN)          192.168.24.134
                        192.168.223.6(WAN)          192.168.223.2(WAN)


WanproxyA is listening on port 3300.

Here's the config for WanproxyA:

create log-mask catch-all
set catch-all.regex "^/"
set catch-all.mask DEBUG
activate catch-all

# Set up codec instances.
create codec codec0
set codec0.codec XCodec
activate codec0

# Set up interfaces.
create interface if0
set if0.family IPv4
set if0.host "192.168.24.1"
set if0.port "3300"
activate if0

# And peers to connect to them.
create peer peer0
set peer0.family IPv4
set peer0.host "192.168.223.2"
set peer0.port "3301"
activate peer0

# Set up proxy from the client that encodes.
create proxy proxy0
set proxy0.interface if0
set proxy0.interface_codec None
set proxy0.peer peer0
set proxy0.peer_codec codec0
activate proxy0

----------------------------------------------------------------------------
And the config for WanproxyB
create log-mask catch-all
set catch-all.regex "^/"
set catch-all.mask DEBUG
activate catch-all

# Set up codec instances.
create codec codec0
set codec0.codec XCodec
activate codec0

# Set up interfaces.
# if0 not really used yet...
create interface if0
set if0.family IPv4
set if0.host "192.168.24.129"
set if0.port "3300"
activate if0

# Set up interfaces.
create interface if1
set if1.family IPv4
set if1.host "192.168.223.2"
set if1.port "3301"
activate if1



# And peers to connect to them.
create peer peer0
set peer0.family IPv4
set peer0.host "
set peer0.port "3260"
activate peer0


# Set up proxy from the client that encodes.
create proxy proxy0
set proxy0.interface if1
set proxy0.interface_codec codec0
set proxy0.peer peer0
set proxy0.peer_codec None
activate proxy0
-----------------------------------------------------------------------------------

WanproxyB _seems_ be be ok.  At least it doesn't display any errors.

WanproxyA gives stuff like this, over and over:

1285181197.480405 [/splice] DEBUG: Unexpected event: <Error>/104 [Connection reset by peer]
1285181197.481028 [/splice/pair] DEBUG: Unexpected event: <Error>/104 [Connection reset by peer]
1285181197.481737 [/wanproxy/proxy/client] ERR: Unexpected event: <Error>/104 [Connection reset by peer]
1285181197.507567 [/xcodec/encoder] DEBUG: Pushing queued data.
1285181197.536737 [/splice] DEBUG: Unexpected event: <Error>/104 [Connection reset by peer]
1285181197.537268 [/splice/pair] DEBUG: Unexpected event: <Error>/104 [Connection reset by peer]
1285181197.537757 [/wanproxy/proxy/client] ERR: Unexpected event: <Error>/104 [Connection reset by peer]

tcpdumps on WanproxyB reveal that reset packets are coming out of the WAN-side interface but the don't seem to be originating from SAN-B.  Also, packets are getting all the way from SAN-A to SAN-B properly for a few packets before the RST packet comes along & kills the connection.


Any help you could give me with getting this running would be apprciated.
Thanks
dave
The information in this electronic mail message is confidential and may be legally privileged. 
It is intended solely for the addressee(s) named herein. 
Access to this electronic message by anyone else is unauthorized
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wanproxy.org/pipermail/wanproxy-wanproxy.org/attachments/20100922/01b67644/attachment-0003.htm>


More information about the wanproxy mailing list