lkml.org 
[lkml]   [1998]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectnetwork anomalies in 2.0.35

Yesterday I moved from 2.0.33 to 2.0.35 on my gateway server (sort of,
it's directly connected to the internet (cable), and does masquerading).

Today, I couldn't use the ftp data port anymore (20 if I'm correct), from
a machine that's on the masqueraded local network.
Anyways, performing the "ls" command on any site gave me a "Bad PORT
command" error and sometimes "ftp: bind: port already in use".
(Note: connecting to the site went OK, so port 21 seemed OK.)
On the gateway server, everything was still OK.

Sorry if this was already known, I have little time to follow linux-kernel
nowadays (holidays, you know ;)).

Nico.


FWIW, I'm also experiencing ipfwadm troubles (This was the reason for
upgrading in the first place). I set up some filters to deny all inbound
packages from 2 particular class B networks. This went fine at first, but
after a few minutes, the gateway machine didn't let anything in anymore.
(outbound everything was still open). I had to flush the filters and reset
them again. Anyone?

--:: Nico Galoppo ::--------------------------------------------------
--:: scratch at ace.ulyssis.student.kuleuven.ac.be ::-----------------
:: ::
--:::::::::::::::::::::::::: Linux - Free power for the masses :::::::




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:44    [W:0.033 / U:0.632 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site