I use a cable modem and have no dial-up functions. I did absolutely nothing to enable ICQ specifically. In fact, I only have one port open for inbound access (7272) that I use for Apache.
My outbound services list looks like this:
prot port n_attach name
UDP 26000 0
Quake
UDP 7648 0
cuseeme
TCP 21 0
ftp
TCP 7070 0
RealAudio
UDP 27000 0
Quake
TCP 6667 0
irc
TCP 7000 0
VDOlive
which is the default as far as I know.
My boot log looks like this:
ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
NE*000 ethercard probe at 0x300: 00 40 05 27 70 0d
eth0: NE2000 found at 0x300, using IRQ 5.
NE*000 ethercard probe at 0x320: 00 40 05 4d e4 b6
eth1: NE2000 found at 0x320, using IRQ 11.
Starting S10debug...
Starting S10syslogd...
Starting S15inet...
Starting S50dhcpcd...
External IP address: 24.213.45.146
Starting S60masq...
Starting S80dhcpd...
Starting S89admstn...
Starting S90admin...
Starting S90ptfwd...
ShareTheNet VERSION=2.1.3
Prot Local Addr/Port > Remote Addr/Port
TCP 123.123.123.123/7272 > 192.168.0.2/80
ip_masq_new(proto=UDP): no free ports.
ip_masq_new(proto=UDP): no free ports.
ip_masq_new(proto=UDP): no free ports.
ip_masq_new(proto=UDP): no free ports.
As a side question, does anyone know what the "no free ports" stuff is all about.
Terry Horton
dave wrote:
> The ICQ system is rather flakey even when connected directly_______________________________________________ ShareTheNet maillist - [EMAIL PROTECTED] http://www.webserv.com/mailman/listinfo/sharethenet
> and I have seen these problems when NOT running STN.That's certainly true but these problems seem to be a direct result of going
through STN. If I drop off STN and connect directly to my ISP, the problems
automagically go away.Is it best to leave a range of 12-24 ports open for ICQ as in the FAQ or a
whole mess of 'em? I also would like to know what would be the difference
(security - wise) between the way I normally connect to the net (via dialup
ISP) and using STN with all ports open ... 0 - 64k or so for TCP/IP and UDP.> Also I often see a "cant connect" issue when switching between
> ISPs - the answer it seems is to always disconnect manually
> (or terminate ICQ while still online to the ISP) before
> dialing the other ISP. I also see this with or without STN.Right - if you don't disconnect from ICQ and instead just click off the net,
ICQ doesn't notice you're disconnected. Then when you connect to your other
ISP, or even the same ISP again, and try to connect, ICQ says - "wait, he's
already connected at that UIN - can't have two people on the same UIN with
different IPs - he'll have to wait..." until the original UIN times out.
The ICQ client sends something along the lines of a ping or keepalive
ack/nack thing to the server every so often. You can see this very clearly
with the Linux variant called LICQ. It has a nifty little network traffic
window :)If anyone has gotten ICQ to work flawlessly (particularly if they have a lot
of active users on their ICQ list) I'd sure like to know about their setup
both for STN and ICQ's firewall settings.dave w
_______________________________________________
ShareTheNet maillist - [EMAIL PROTECTED]
http://www.webserv.com/mailman/listinfo/sharethenet
