Date: Sat, 04 Jun 2016 10:12:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ipfw@FreeBSD.org Subject: [Bug 209680] ipfw: when enabled, net connections time out/ssh results in "broken pipe" Message-ID: <bug-209680-7515-izo6xSaquT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209680-7515@https.bugs.freebsd.org/bugzilla/> References: <bug-209680-7515@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209680 --- Comment #6 from ohartman@zedat.fu-berlin.de --- Today, I made another observation in this matter. On a server that has in-kernel NAT and LIBALIAS and attached to the net via ADSL SoHo connection, serving as a server accessible from the outside world isn't possible anymor= e. It worked a couple of weeks ago with the ipfw-rules I use, inclusive the pr= oper forwarding rules, but since ~ two weeks, when these "broken pipe issues" started getting worse and worse, connecting to the provided www server or s= sh wasn't possible anymore. I started then checking for mistakes in the ipwf ruleset. Today, I had the chance to access the box from the outside world simultanously with access to the server and its IPFW itself and after a cle= an reboot of=20 FreeBSD 11.0-ALPHA2 #10 r301307: Sat Jun 4 11:03:17 CEST 2016 amd64 trying to connect to the server's Apache server or ssh failed. Then we restarted simply several times the local ipfw via "service ipfw restart" and voila - it worked! Sorry for the poor material I can provide at the moment, but time constrain= ts are tight and my abilities of debugging are limited and seting up alternati= ve serving systems circumventing the issue reporting here eat a lot of time. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209680-7515-izo6xSaquT>