Ah the two different IPs are because I was changing my IPs for this mailing list and I guess I forgot that one. :) Will try added a static route. Also going to snoop traffic and see if the gluster client is actually getting to the server or being blocked by the firewall. Ill letcha all know what I find. Thanks for the ideas. Liam On Dec 3, 2010 6:32 PM, <mki-glusterfs at mozone.net> wrote: > On Fri, Dec 03, 2010 at 04:25:18PM -0800, Liam Slusser wrote: >> [root at client~]# netstat -pan|grep glus >> tcp 0 1 10.8.10.107:1000 10.8.11.102:6996 SYN_SENT 3385/glusterfs >> >> from the gluster client log: >> >> However, the port is obviously open... >> >> [root at client~]# telnet 10.8.11.102 6996 >> Trying 10.2.56.102... >> Connected to glusterserverb (10.8.11.102). >> Escape character is '^]'. >> ^] >> telnet> close >> Connection closed. > > Looking further... why is your telnet trying 10.2.56.102 when you > clearly specified 10.8.11.102? Also, what happens if you do a > specific route for the 10.8.11.0/24 block thru the appropriate gw > without relying on the default gw to route for you? In this way > you dont end up in a situation where the client is mistakenly > trying to go over the wrong interface. The telnet maybe switching > to an alternate interface to see if it gets thru? > > Mohan > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
