I have attached two of my previous posts to mailing list and news groups.
Long story short, I have a Linux box with ipmasq that connects to the
Internet via PPP. I noticed this behavior around the transition to kernel
2.2.x and ipchains, but I am not totally sure they are related to the
problem.
My gateway machine (Debian Linux running 2.2.6 currently) after a certain
amount of uptime will still masq ports for all my client systems, but will
not longer work for itself. Meaning I cannot be logged into the gateway
system and FTP or Telenet to another system either inside my localnet or
outside to the Internet.
Now that I am connected 24x7 to the Internet, I notice the condition
occurred in about 5 days the last two time (before it was 16 to 17 days
when I used diald). Any ideas on how I can track what is happening, or how
I can solve it?
[First Note 2/17/1999]
Hey All...
I have a reoccurring problem that can be solved by a reboot, but I would
rather fix the problem now so I know what is going on. It is a fairly
awkward error that just started again on my system after working for
17-days without reboot.
My home Linux box is on a network and is a gateway to the Internet via a
PPP dial up account. IPchains is setup and working like a champ, but now
my system is to the point where it does not communicate (for lack
of a better word) with daemons at my work.
If I try to FTP to my Linux box at work from my Linux box at home (via PPP)
it simply hangs on the client end and gives the following message on the
server side:
Feb 16 19:18:03 torch wu-ftpd[32109]: warning: can't get client address:
Connection reset by peer
Feb 16 19:18:03 torch wu-ftpd[32109]: connect from unknown
Feb 16 19:18:03 torch syslog: getpeername (wu-ftpd): Transport endpoint is
not connected
Feb 16 19:18:06 torch wu-ftpd[32109]: FTP session closed
Similar messages with telnetd occur. However, I can use SSH just fine.
While I thought this was a IPmasq problem, it seems that I do have the same
scenario on my local net with just this Linux server (the gateway system).
All other systems in my local home network can get to the Internet with all
of their clients (telnet, ftp, etc.) through the troubled server without a
hitch. Strange, but I am not sure how to correct this problem or go about
troubleshooting my home Linux server?
[END]
[Second Note 3/8/99]
Well it seems to happen every 16 days or so.
My home Linux box that I use as my IPmasq dial up box for my home network
his not connecting with most of the standard network (client/server) apps.
Now, when my system is at home and make a PPP connection to the Internet, I
cannot use the clients on that server to get anywhere (with Lynx, FTP,
telnet, etc). Ssh, however, does work and I can use that to get anyone of
my Debian servers.
This is not just limited to traffic through PPP it holds true for the home
networked machines as well via ethernet. Here is what I get in my log file
on the SERVER end at work when I try to FTP home my home dial up box:
Mar 8 11:05:54 torch wu-ftpd[686]: warning: can't get client address:
Connection reset by peer
Mar 8 11:05:54 torch wu-ftpd[686]: connect from unknown
Mar 8 11:05:54 torch syslog: getpeername (wu-ftpd): Transport endpoint is
not connected
Mar 8 11:05:57 torch wu-ftpd[686]: FTP session closed
This has happened two other times, and I have noticed it after 16 days of
uptime on my gateway box (home dial up).
A reboot will fix the problem, but I would like to know what is going on.
[END]
--Jay Barbee
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
