Am 19.02.2017 um 13:34 schrieb Mantas Mikulėnas:
On Sat, Feb 18, 2017 at 10:32 PM, Ian Pilcher > wrote:
I have configured sshd on my firewall to listen only on its internal
IP address. This is causing it to fail when it first starts,
On Sat, Feb 18, 2017 at 10:32 PM, Ian Pilcher wrote:
> I have configured sshd on my firewall to listen only on its internal
> IP address. This is causing it to fail when it first starts, since the
> IP address is not actually configured yet.
>
> I have confirmed that
On Mon, Feb 06, 2017 at 09:56:30PM +0100, Lennart Poettering wrote:
> On Sat, 21.01.17 21:20, Marc Haber (mh+systemd-de...@zugschlus.de) wrote:
> > On Fri, Jan 20, 2017 at 02:51:00PM +, Patrick Schleizer wrote:
> > > I've learned about the kernel parameter and symlink ways to disable
> > >
No, that's not how I tested it.
On Sun, Feb 19, 2017 at 2:42 PM, Reindl Harald
wrote:
>
> i guess you tested that from the local host itself and not from the
> outside because this is *not* true
>
> on the local machine things are different like reject a specific port for
On Sun, Feb 19, 2017 at 6:56 PM, Andrei Borzenkov
wrote:
> 19.02.2017 15:34, Mantas Mikulėnas пишет:
> > On Sat, Feb 18, 2017 at 10:32 PM, Ian Pilcher
> wrote:
> >
> >> I have configured sshd on my firewall to listen only on its internal
> >> IP
On 02/19/2017 06:34 AM, Mantas Mikulėnas wrote:
That said... listening only on internal addresses doesn't mean the
connections will be accepted only from internal interfaces -- at least
for IPv4, Linux considers the addresses as belonging to the whole host,
and will still accept connections from
19.02.2017 15:34, Mantas Mikulėnas пишет:
> On Sat, Feb 18, 2017 at 10:32 PM, Ian Pilcher wrote:
>
>> I have configured sshd on my firewall to listen only on its internal
>> IP address. This is causing it to fail when it first starts, since the
>> IP address is not