Have to start somewhere. FC4, Actiontec 701. If I turn the firewall "off" Gaim works just fine. If I turn it "on" nothing, just sits there. Ok add iptabs accept 5190. Just sits there. Yahoo & Google have been no help. Any help here - I pay in beer ;-)

yahoo is 5160 and jabber 5222?? not sure with the ports. but in general if you allow 5000-6000 you will be able to connect. if you want stricter rules, disable firewall, you connect to your yahoo and google accounts through gaim, just do a netstat -ant and see the ports that they use. then enable firewall and allow the ports accordingly.

Tried this
iptables -A INPUT -p tcp -i ppp0 --destination-port 5000:6000 -j ACCEPT
nope.
Did find Gaim uses 5050 & 5190 - so... iptables -L -vn --line-numbers gives
65 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5050
66 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5190
still nothing. netstat gives
tcp 0 1 192.168.0.4:55170 205.188.153.121:5190 SYN_SENT
tcp 0 1 192.168.0.4:43888 216.155.193.145:5050 SYN_SENT

iptables -L -vn
Chain INPUT (policy ACCEPT 52 packets, 10156 bytes)
pkts bytes target prot opt in out source destination
0 0 DROP tcp -- ppp0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:23
1 48 DROP tcp -- ppp0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
0 0 QUEUE udp -- br0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53
551 33749 ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED
0 0 ACCEPT udp -- eth0 * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED
0 0 ACCEPT all -- eth0 * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
0 0 ACCEPT tcp -- ppp0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5050
0 0 ACCEPT tcp -- ppp0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5190

tks

Found in the Gaim FAQs
-----------------
QUOTE
Ques: I cannot connect to Yahoo! and I'm behind a firewall or NAT. Why doesn't Gaim have Yahoo's "Firewall with no proxy" option? Yahoo!'s firewall with no proxy option connects to Yahoo! by wrapping the YMSG protocol inside HTTP. Gaim currently doesn't support doing this.

Ans: Gaim does support changing the port it connects to. Try changing the Pager Port in the Account editor under "Show more options". Ports known to work are: 20, 23, 25, 80, 119, 5050, 8001, and 8002. While this doesn't work for as many people as actually tunneling through the HTTP protocol would, it helps many users.
UNQUOTE
-------------
So ok I'll walk the port list - first one is "20" Well what'cha know I'm connected.