Very Computer

> hello all,

> i have a machine set up with redhat 5.1, kernel 2.0.35 running
> ip masquerading.  just about every application i use (web, ftp,
> telnet, realaudio, aol instant messenger, etc) has worked fine
> without any intervention on my part.

> icq ALMOST works.  it connects, i can send and receive messages
> from people (haven't tried it with files yet), but it refuses
> to allow me to use the chat feature!  it just times out waiting
> for the other party to respond.  or vice versa.  has anybody
> experienced this problem or found a way to fix it?

> do i need to use ipautofw?  i have read a lot of pages that
> say you have to install ipautofw to do a lot of the things that
> i can already do without it, so i thought maybe the ip masq
> support in newer kernels made ipautofw obsolete.

> any help would be appreciated (please cc to my e-mail if at

> thanks,
> chris

> > icq ALMOST works.  it connects, i can send and receive messages
> > from people (haven't tried it with files yet), but it refuses
> > to allow me to use the chat feature!  it just times out waiting
> > for the other party to respond.  or vice versa.  has anybody
> > experienced this problem or found a way to fix it?

> > do i need to use ipautofw?  i have read a lot of pages that
> > say you have to install ipautofw to do a lot of the things that
> > i can already do without it, so i thought maybe the ip masq
> > support in newer kernels made ipautofw obsolete.

> > any help would be appreciated (please cc to my e-mail if at

> Yeah, you have to use ipautofw to forward some ports to your windows box for ICQ.
> I think ICQ wants at least 11 ports (could be 7, I forget). You can find out when
> you setup ICQ to use the ports you have assigned it. If you need more info / help,
> feel free to ask me.

> Actually, all you have to do is configure your ICQ to go through your
> inux box as a firewall. You can get to it by choosing:
> Preferences, Connection and click on LAN connection, firewall. No socks
> server or anything.

>hello all,

>i have a machine set up with redhat 5.1, kernel 2.0.35 running
>ip masquerading.  just about every application i use (web, ftp,
>telnet, realaudio, aol instant messenger, etc) has worked fine
>without any intervention on my part.

>icq ALMOST works.  it connects, i can send and receive messages
>from people (haven't tried it with files yet), but it refuses
>to allow me to use the chat feature!  it just times out waiting
>for the other party to respond.  or vice versa.  has anybody
>experienced this problem or found a way to fix it?

>do i need to use ipautofw?  i have read a lot of pages that
>say you have to install ipautofw to do a lot of the things that
>i can already do without it, so i thought maybe the ip masq
>support in newer kernels made ipautofw obsolete.

>any help would be appreciated (please cc to my e-mail if at

>thanks,
>chris

> Actually, all you have to do is configure your ICQ to go through your
> inux box as a firewall. You can get to it by choosing:
> Preferences, Connection and click on LAN connection, firewall. No socks
> server or anything.

>hello all,

>i have a machine set up with redhat 5.1, kernel 2.0.35 running
>ip masquerading.  just about every application i use (web, ftp,
>telnet, realaudio, aol instant messenger, etc) has worked fine
>without any intervention on my part.

>icq ALMOST works.  it connects, i can send and receive messages
>from people (haven't tried it with files yet), but it refuses
>to allow me to use the chat feature!  it just times out waiting
>for the other party to respond.  or vice versa.  has anybody
>experienced this problem or found a way to fix it?

>do i need to use ipautofw?  i have read a lot of pages that
>say you have to install ipautofw to do a lot of the things that
>i can already do without it, so i thought maybe the ip masq
>support in newer kernels made ipautofw obsolete.

>any help would be appreciated (please cc to my e-mail if at

>thanks,
>chris

> If both users are behind a firewall, then I don't think chat or file transfers will
> work.  (Unless there is a socks proxy for Linux?  I haven't tried looking for one yet.)

> I have been trying to use ipautofw myself, and every time I get the message:
>   setsockopt: Protocol not available
> This happens no matter what options I try.  Anyone know what might be causing this?
> Also, ip masq modules are complaining of unresolved symbols.  I haven't been able to
> test if the modules are working.  (I'm using Red Hat 5.2--2.0.36 kernel, if that makes a
> difference.)

> --
> Mike Patterson

> > Actually, all you have to do is configure your ICQ to go through your
> > inux box as a firewall. You can get to it by choosing:
> > Preferences, Connection and click on LAN connection, firewall. No socks
> > server or anything.

> I had the same problem with ipautofw. Just recompiled the kernel and set ipautofw on under
> networking options. Then it worked.

> > I have been trying to use ipautofw myself, and every time I get the message:
> >   setsockopt: Protocol not available
> > This happens no matter what options I try.  Anyone know what might be causing this?
> > Also, ip masq modules are complaining of unresolved symbols.  I haven't been able to
> > test if the modules are working.  (I'm using Red Hat 5.2--2.0.36 kernel, if that makes a
> > difference.)