Rat uses 224.255.222.239 on UDP port 47000 for interprocess communication, plus the address and port pair used for the wide-area audio. There's no need to open the complete multicast range.
Colin On 9 Jul 2004, at 13:43, Ti Leggett wrote: > For one thing, rat requires a local multicast loopback to communicate. > > So you'll need to allow either > > iptables -A INPUT -s 224.0.0.0/4 -j ACCEPT > > or > > iptables -A OUTPUT -d 224.0.0.0/4 -j ACCEPT > > or both possibly. > > That's a first guess. > > On Thu, 2004-07-08 at 17:45, Joshua M. Brown wrote: >> Fred Dech wrote: >> >>> speaking of firewalls... >>> i repeatedly installed and uninstalled, etc., etc., the FC2 RPMs >>> courtesy of >>> http://osl.cpe.ku.ac.th >>> and Sugree Phatanapherom yum instructions by way of Michael Miller. >>> Thanks Sugree! >>> but i could't even get a videoConsumer to run, let alone RAT. huh? >>> very frustrating, but no monitors broken ;^) >>> >>> as i was reading the XP firewall thread it dawned on me that the >>> FedoraCore2 >>> firewall interface had been simplified to ON/OFF. i disabled it and >>> RAT >>> came up and my videoConsumer started receiving streams... >>> >>> since i'd prefer to have a semblance of a firewall, i just have to >>> learn >>> how to set up iptables to allow the right range of tcp/udp ports >>> access. >>> >>> >> i was wondering that kinda thing myself. i've not seen an enumeration >> of >> all ports (all, for whatever reason at any/all times) that AG uses. i >> spose i could analyze my traffic, but don't want to miss any "corner >> cases" that could trip it up. >> >> Anyone have a list like that? >> >> jmb >> >>> i'd appreciate any pointers ;^) >>> >>> --fred >>> >>> >>> >> > > -- Colin Perkins http://csperkins.org/
