Ranjan Maitra inbox.com> writes:
> So, I have a strange problem which I can't figure out. After Friday's
> updates, I was unable to ssh into the machine with a nonstandard port.
> I changed the port to the default and was able to get in. I was able to
> resolve this only after stopping and starti
On Tue, 29 Jan 2013 04:00:05 +0100 Suvayu Ali wrote:
> On Mon, Jan 28, 2013 at 08:23:11PM -0600, Ranjan Maitra wrote:
> > On Tue, 29 Jan 2013 03:01:30 +0100 Suvayu Ali > +li...@gmail.com> wrote:
> >
> > I am not sure how to figure out what were in those updates. Is there a
> > way? I am not eve
On Mon, Jan 28, 2013 at 08:23:11PM -0600, Ranjan Maitra wrote:
> On Tue, 29 Jan 2013 03:01:30 +0100 Suvayu Ali +li...@gmail.com> wrote:
>
> I am not sure how to figure out what were in those updates. Is there a
> way? I am not even sure that this is an iptables issue, only that
> restarting it ap
On Tue, 29 Jan 2013 03:01:30 +0100 Suvayu Ali wrote:
> On Mon, Jan 28, 2013 at 03:47:50PM -0800, Ranjan Maitra wrote:
> > OK, I believe this is a bug (or a feature I can not fathom)
> >
> > I reboot the machine, and lose access to the ssh port. Restarting iptables
> > fixes the problem. This
On Mon, Jan 28, 2013 at 03:47:50PM -0800, Ranjan Maitra wrote:
> OK, I believe this is a bug (or a feature I can not fathom)
>
> I reboot the machine, and lose access to the ssh port. Restarting iptables
> fixes the problem. This is problematic because the machine can not be
> rebooted remote
should this be filed against?
This only started after last Friday's updates.
Many thanks!
> -Original Message-
> From: maitra.mbox.igno...@inbox.com
> Sent: Mon, 28 Jan 2013 15:01:58 -0600
> To: users@lists.fedoraproject.org
> Subject: F18: post-friday updates +
So, I have a strange problem which I can't figure out. After Friday's
updates, I was unable to ssh into the machine with a nonstandard port.
I changed the port to the default and was able to get in. I was able to
resolve this only after stopping and starting iptables service.
Is this the norm? How
