Recently my 5+ year old Linksys router stopped translating PASV commands for the FTP protocol. This showed up first by throwing errors during the LIST process and then just ended up refusing to translate any PASV commands. In the end the inconsistency finally resulted in no Active or Passive FTP traffic whatsoever, with all other features working just fine. Linksys's Routers are one of the few that can dynamically handle PASV commands and port shifting, without leaving open ports on a perm basis. It accomplishes this with an API translator that is prone to corruption. I've not found a way to fix the issue (that wouldn't have cost more in time than the cost of a new router). If your functioning FTP site suddenly stops translating PASV commands and starts throwing 226 and 500 errors and it's behind a Linksys BEFSR41 try removing it from the loop of possibilities. Just might save you some time.
Sure there can be a litany of other things that can cause the issue, last on most peoples list is the routers translation API, but it's really not that uncommon of a problem for these normally iron clad work horses.
Long live your BEFSR41, rip to the rest...
-Z
No comments:
Post a Comment