Date: Sat, 30 Apr 2005 00:26:37 +0200 From: Remko Lodder <remko@FreeBSD.org> To: Neo-Vortex <root@Neo-Vortex.net> Cc: Siddhartha Jain <sid@netmagicsolutions.com> Subject: Re: IPFW disconnections and resets Message-ID: <4272B49D.6050805@FreeBSD.org> In-Reply-To: <20050429225510.P6468@Neo-Vortex.net> References: <4272011F.9040707@netmagicsolutions.com> <20050429194242.I78552@Neo-Vortex.net> <20050429203417.P85987@Neo-Vortex.net> <20050430001910.C3271@a2.scoop.co.nz> <20050429225510.P6468@Neo-Vortex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Neo-Vortex wrote:
>
> On Sat, 30 Apr 2005, Andrew McNaughton wrote:
>
>
>>1% is way too much. use nohup. eg:
>
>
> SSH dies, asin i get "Connection reset by peer" and my ssh session closes,
> i can restart it fine though and the rest of the rules are parsed fine,
> also, i dont get that on the window that im loading the firewall rulesets,
> only on my other session wich has irssi running wich sends a packet once
> every second to update the time... the box never needs to be physically
> touched :)
>
> ~Neo-Vortex
The best reply sofar (imho) was to use screen.
When i reload my ruleset i do that with:
pfctl -Fa -f /etc/pf.conf.new && sleep 180 && pfctl -Fa -f /etc/pf.conf
where the new file is my test setup and the other file is the current
working one. When i reload them with screen i am sure that the commands
read correctly and even when i get kicked out the screen application
still carries the commands given. In worst case i can access the machine
again after three minutes, which isn't that bad ;-)
Just my 0.02E(urocents)
--
Kind regards,
Remko Lodder ** remko@elvandar.org
Reporter DSINET ** remko@DSINet.org
Founder Tienervaders ** remko@tienervaders.org
FreeBSD Documentation Project ** remko@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4272B49D.6050805>