by other than UDP port 4000, you might need to setup TCP port as well. In the
ICQ configuration, you can specify the port number in the Connection menu.
Just say I'm behind a firewall and not using SOCKS. For my case, I use
2040 to 2060 for TCP. But I'm not using IPCHAIN, it's ipfwadm instead. It
works great. Give it a try!
Kelvin
> Running 2.2.5 kernel with IP Chains installed. Running IP Masq with
> firewall
> rc.firewall file is as follows for MASQ timeouts and IP Masq:
> ipchains -M -S 7200 10 60
> ipchains -P forward DENY
> ipchains -A forward -s xxx.xxx.xxx.xxx/xx -j MASQ
> With this setup ICQ recv's TCP packets perfectly. Problem is that I
> can't send. ICQ req UDP packets to go through port 4000. I tried the
> following
> ipchains -F (flush the firewall)
> ./rc.firewall (initialize)
> ipchains -A output -p UDP -s xxx.xxx.xxx.xxx./xx -d 0.0.0.0/0 4000
> then
> ipchains -L (verified firewall policies)
> It shows:
> Chain Input (policy ACCEPT):
> <nothing here>
> Chain forward (policy DENY):
> target = MASQ
> prot = all
> opt = blank
> source = xxx.xxx.xxx.xxx/xx
> destination = anywhere
> ports = n/a
> Chain output (policy ACCEPT):
> target = blank
> prot = udp
> opt = blank
> source = xxx.xxx.xxx.xxx/xx
> destination = anywhere
> ports = any -> 4000
> Reboot windows machine, and it still won't send messages. So what am I
> missing here. Newsgroups work, email works, web works, ftp works, irc
> works, etc. etc. etc.
> Ideas ?? Someone out there with IP Chains experience ?