7:45 p.m.
I always move sshd from port 22 to port nnn. To do this I use semanage
(which I had to install):
semanage port -a -t ssh_port_t -p tcp nnn
then edit /etc/ssh/sshd_config to point to port nnn.
then I edit iptables (which is off on this install, interesting, though
selinux is not) to open up port nnn.
Finally I restart sshd.
Well, first off I am sshed into the box doing this on port 22. status of
sshd is it is listening on port nnn. I tried opening another ssh
session (without stoping the one running right now), to port and get:
No route to host
To the old port 22 I get
Connection refused.
I do this all the time with Fedora and Centos. What am I missing on
this system?
I put the port back to 22 until I figure this out.
9:53 p.m.
On 04/18/2013 08:45 PM, Robert Moskowitz wrote:
I always move sshd from port 22 to port nnn. To do this I use
semanage
(which I had to install):
[...]
Robert, your starting to ask questions that are not specific to Fedora
ARM development or about specific arm hardware. For these question you
should pursue the normal support channels.
http://fedoraproject.org/en/get-help
--
Scott Sullivan
10:19 p.m.
On 04/18/2013 10:53 PM, Scott Sullivan wrote:
On 04/18/2013 08:45 PM, Robert Moskowitz wrote:
> I always move sshd from port 22 to port nnn. To do this I use semanage
> (which I had to install):
[...]
Robert, your starting to ask questions that are not specific to Fedora
ARM development or about specific arm hardware. For these question you
should pursue the normal support channels.
http://fedoraproject.org/en/get-help
Except I have been doing this on Fedora and Centos distros for years. I
try it on the ARM distro and what I have always done does not work.
What is different here?
I think it is firewall related. Right now I cannot work on it; perhaps
later this evening. Does the ARM distro do firewalling some way other
than iptables? That recommendation to try SSH to localhost is a good
test; that is one of the next things I will try.
But IMHO, this is ARM Fedora distro related, because what works on
Centos 6 i386/x86_64 and Fedora 17/18 i386/x86_64 is not working here.
11:07 p.m.
On 04/18/2013 11:19 PM, Robert Moskowitz wrote:
On 04/18/2013 10:53 PM, Scott Sullivan wrote:
> On 04/18/2013 08:45 PM, Robert Moskowitz wrote:
>> I always move sshd from port 22 to port nnn. To do this I use semanage
>> (which I had to install):
> [...]
>
> Robert, your starting to ask questions that are not specific to Fedora
> ARM development or about specific arm hardware. For these question you
> should pursue the normal support channels.
>
> http://fedoraproject.org/en/get-help
Except I have been doing this on Fedora and Centos distros for years. I
try it on the ARM distro and what I have always done does not work.
What is different here?
I think it is firewall related. Right now I cannot work on it; perhaps
later this evening. Does the ARM distro do firewalling some way other
than iptables? That recommendation to try SSH to localhost is a good
test; that is one of the next things I will try.
But IMHO, this is ARM Fedora distro related, because what works on
Centos 6 i386/x86_64 and Fedora 17/18 i386/x86_64 is not working here.
Fedora 18 introduces a lot of new features, including a new firewall demon.
https://fedoraproject.org/wiki/Releases/18/FeatureList
Specifically,
https://fedoraproject.org/wiki/Features/firewalld-default
Could you double check that the behaviour is not consistent with Fedora
18 i386/x86_64 and if so file a bug against the relevant packages?
--
Scott Sullivan
11:21 p.m.
On 04/19/2013 12:07 AM, Scott Sullivan wrote:
On 04/18/2013 11:19 PM, Robert Moskowitz wrote:
>
> On 04/18/2013 10:53 PM, Scott Sullivan wrote:
>> On 04/18/2013 08:45 PM, Robert Moskowitz wrote:
>>> I always move sshd from port 22 to port nnn. To do this I use
>>> semanage
>>> (which I had to install):
>> [...]
>>
>> Robert, your starting to ask questions that are not specific to Fedora
>> ARM development or about specific arm hardware. For these question you
>> should pursue the normal support channels.
>>
>> http://fedoraproject.org/en/get-help
>
> Except I have been doing this on Fedora and Centos distros for years. I
> try it on the ARM distro and what I have always done does not work.
>
> What is different here?
>
> I think it is firewall related. Right now I cannot work on it; perhaps
> later this evening. Does the ARM distro do firewalling some way other
> than iptables? That recommendation to try SSH to localhost is a good
> test; that is one of the next things I will try.
>
> But IMHO, this is ARM Fedora distro related, because what works on
> Centos 6 i386/x86_64 and Fedora 17/18 i386/x86_64 is not working here.
Fedora 18 introduces a lot of new features, including a new firewall
demon.
https://fedoraproject.org/wiki/Releases/18/FeatureList
Specifically,
https://fedoraproject.org/wiki/Features/firewalld-default
Could you double check that the behaviour is not consistent with
Fedora 18 i386/x86_64 and if so file a bug against the relevant packages?
I will look into this. I THOUGHT one of my notebooks was f18, but
/etc/fedora-release says f17. I guess I have only been playing around
with LiveCD on for testing some new boxes, but really am not running f18
here. So I am behind things and need to read up on this. This could
well be what is blocking me.
Thanks for the information.
12:21 a.m.
OK. My bad for not getting that iptables was replaced with firewalld.
I read up on the command line and added --permanent --port=nnn/tcp and
all is well.
Thank you for your help.
On 04/19/2013 12:07 AM, Scott Sullivan wrote:
On 04/18/2013 11:19 PM, Robert Moskowitz wrote:
>
> On 04/18/2013 10:53 PM, Scott Sullivan wrote:
>> On 04/18/2013 08:45 PM, Robert Moskowitz wrote:
>>> I always move sshd from port 22 to port nnn. To do this I use
>>> semanage
>>> (which I had to install):
>> [...]
>>
>> Robert, your starting to ask questions that are not specific to Fedora
>> ARM development or about specific arm hardware. For these question you
>> should pursue the normal support channels.
>>
>> http://fedoraproject.org/en/get-help
>
> Except I have been doing this on Fedora and Centos distros for years. I
> try it on the ARM distro and what I have always done does not work.
>
> What is different here?
>
> I think it is firewall related. Right now I cannot work on it; perhaps
> later this evening. Does the ARM distro do firewalling some way other
> than iptables? That recommendation to try SSH to localhost is a good
> test; that is one of the next things I will try.
>
> But IMHO, this is ARM Fedora distro related, because what works on
> Centos 6 i386/x86_64 and Fedora 17/18 i386/x86_64 is not working here.
Fedora 18 introduces a lot of new features, including a new firewall
demon.
https://fedoraproject.org/wiki/Releases/18/FeatureList
Specifically,
https://fedoraproject.org/wiki/Features/firewalld-default
Could you double check that the behaviour is not consistent with
Fedora 18 i386/x86_64 and if so file a bug against the relevant packages?
4063
days inactive
4063
days old
5 comments
2 participants
participants (2)
-
Robert Moskowitz -
Scott Sullivan