just a suggestion, why don't you use something like /usr/sbin/tcpdump -ieth0 not port 1090 and not port 25322 and ..... and see what shows up. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Lyness Sent: Wednesday, July 09, 2008 11:27 AM To: [email protected] Subject: [Sequoia] Firewall Issues
Hey All, I am getting completely stumped on how to properly setup the firewall for Sequoia to allow backup transfers between controllers. I've got communication between the controllers working fine and the console properly recognizes both controllers. The only issue seen so far is that when trying to 'transfer dump' the error 'no route to host' occurs. Now, if I turn off the firewall dumps can be transferred with out a hitch (i.e. dumpserver, etc... are setup properly). I can't find anything in netstat that seems to be missing. Here are the entries used to open the firewall for sequoia, does anyone know what is missing? accept from all addrs to 224.1.1.5, all ports/tcp accept from all addrs to 224.1.1.5, all ports/udp accept from all addrs to 224.2.2.5, port 11000/udp accept from/to all addrs, port 1090/tcp accept from/to all addrs, port 1090/udp accept from/to all addrs, port 25322/tcp accept from/to all addrs, port 25322/udp accept from/to all addrs, port 25323/tcp accept from/to all addrs, port 25323/udp Martin Dale Lyness MagnetStreet [EMAIL PROTECTED] Office: (763) 450-7503 Cell: (715) 630-0296
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
