Date: Wed, 21 Jul 2004 13:10:12 -0700 From: Matt White <matt+list.sw.freebsd.current@publicly.neglect.us> To: freebsd-current@freebsd.org Subject: RE: fetch hangs, part 2 Message-ID: <3279369656.1090415412@[192.168.20.34]> In-Reply-To: <20040721115021.J81889@carver.gumbysoft.com> References: <000001c46f11$1f53a880$132a15ac@spud> <3270557515.1090406600@[192.168.20.34]> <20040721115021.J81889@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't think so in this case since I was using this same netscreen with a FreeBSD 5.1 box without incident. I'm actually suspicious of the cabling at the moment, but I have higher priorities than to figure that out at the moment. -Matt --On Wednesday, July 21, 2004 11:51 AM -0700 Doug White <dwhite@gumbysoft.com> wrote: > On Wed, 21 Jul 2004, Matt White wrote: > >> In my case, I tracked this down to either my netscreen5 or the cable into >> it going south. It's a bit strange because other software wasn't having >> an issue, so I'll probably look at this more in the next few days. But >> for now, removing that box from my network has made fetch happy again, >> which in turn has made me happy again. > > It might have been breaking passive-mode FTP. I've noticed this problem > coming from certain places. Thankfully not from my workplace or home :) > > Some older inspective firewalls don't understand passive mode and drop the > connection. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3279369656.1090415412>