Re: setting up ssh {solved}

2011-08-29 Thread Adam Williamson
On Sat, 2011-08-27 at 10:01 -0600, Peter G. wrote: > Michael Spahn wrote: > > > In my opionion it's still a bug, the should be a notice what "Apply" mean. > > I agree. I meant that I don't need any more hints or tips, because I have > solved > the problem and I now have ssh working. Clearly, as

Re: setting up ssh {solved}

2011-08-27 Thread Peter G.
Michael Spahn wrote: > In my opionion it's still a bug, the should be a notice what "Apply" mean. I agree. I meant that I don't need any more hints or tips, because I have solved the problem and I now have ssh working. Clearly, as I was trying to get this solved, we stumbled across a bug in th

Re: setting up ssh {solved}

2011-08-27 Thread Michael Spahn
In my opionion it's still a bug, the should be a notice what "Apply" mean. Am 27.08.2011 01:59, schrieb Peter G.: > Michael Cronenworth wrote: > >> # ip(6)tables -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j >> # ACCEPT >> run "systemctl restart iptables.service" and >> "systemctl rest

Re: setting up ssh {solved}

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > # ip(6)tables -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j > # ACCEPT > run "systemctl restart iptables.service" and > "systemctl restart ip6tables.service" This works. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fe

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Peter G. wrote: > I guess thatś because I restarted after I came back from the body shop. Yes, your iptables/ip6tables settings get loaded by the iptables/ip6tables service upon boot-up. You can get the same effect as running "systemctl restart iptables.service" and "systemctl restart ip6tables

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Spahn wrote: > Bug is opened, feel free to add a comment. > > https://bugzilla.redhat.com/show_bug.cgi?id=733778 > > Regards > > Michael Thanks. I was going to do that after I get back from a jog :-) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fed

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > Peter G. wrote: >> iptables -L does now show an ssh entry. Does this also do ipv6 (or would >> I ever need to deal with this in an ipv6 situation, down the road?)? > > No. You will want ip6tables for that. Odd. I just checked /etc/sysconfig/ip6tables and there is thi

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > The apply button in system-config-firewall should apply the firewall > settings. He shouldn't need to reboot or reload the iptables rules. That's what I thought. That's why it says apply. Apply means to put into being, now. -- test mailing list test@lists.fedorapro

Re: setting up ssh

2011-08-26 Thread Peter G.
Clyde E. Kunkel wrote: > I assume you have rebooted after changing firewall rules no. I didn't. Linux folklore states that rebooing is not necessary > and/or issued: > > # systemctl restart iptables.service I didn know I had to. > If so, then I dunno but I do... now. -- test maili

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Peter G. wrote: > iptables -L does now show an ssh entry. Does this also do ipv6 (or would I > ever > need to deal with this in an ipv6 situation, down the road?)? No. You will want ip6tables for that. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Clyde E. Kunkel wrote: >I assume you have rebooted after changing firewall rules and/or issued: > > # systemctl restart iptables.service > > If so, then I dunno The apply button in system-config-firewall should apply the firewall settings. He shouldn't need to reboot or reload the iptable

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > # iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j > # ACCEPT > > As Michael said, system-config-firewall has a bug. You two should file a > bug against it. Thanks for all the help. I hope this will now work. I will try it in a couple of hours...

Re: setting up ssh

2011-08-26 Thread Michael Spahn
Bug is opened, feel free to add a comment. https://bugzilla.redhat.com/show_bug.cgi?id=733778 Regards Michael Am 26.08.2011 21:04, schrieb Peter G.: > Michael Spahn wrote: > >> I learned that the firewall system-config tool doesn't work. >> >> I actually don't know why but I always had to disab

Re: setting up ssh

2011-08-26 Thread Clyde E. Kunkel
On 08/26/2011 02:55 PM, Peter G. wrote: > Michael Cronenworth wrote: > >> # iptables -L | grep ssh >> ACCEPT tcp -- anywhere anywherestate NEW >> tcp dpt:ssh > > You know, I just tried your command again, but this time without grepping, and > I see that ssh is nowhere

Re: setting up ssh

2011-08-26 Thread Jan Wildeboer
Does it put the correct rules in iptable.safe? Might be a systemd problem of restarting with the new rules. Does it work after a reboot? Jan -- Jan H Wildeboer| EMEA Open Source Affairs | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Spahn wrote: > I learned that the firewall system-config tool doesn't work. > > I actually don't know why but I always had to disable the whole firewall. I never had to disable the firewall in f13 or f14 or f15 for ssh (only for nfs, which I no longer use, because of that and other reas

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Peter G. wrote: > You know, I just tried your command again, but this time without grepping, and > I see that ssh is nowhere in the output, so how could grep ssh ever return > anything? My command was an example of when a firewall rule existed to allow ssh through. > > But, when I examine /etc/s

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Michael Spahn wrote: > I learned that the firewall system-config tool doesn't work. You should file a bug... -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > # iptables -L | grep ssh > ACCEPT tcp -- anywhere anywherestate NEW > tcp dpt:ssh You know, I just tried your command again, but this time without grepping, and I see that ssh is nowhere in the output, so how could grep ssh ever return

Re: setting up ssh

2011-08-26 Thread Michael Spahn
Hello, I learned that the firewall system-config tool doesn't work. I actually don't know why but I always had to disable the whole firewall. Regards Michael Am 26.08.2011 20:40, schrieb Peter G.: > Michael Cronenworth wrote: > >> netstat lists network port information. It does not know about

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > netstat lists network port information. It does not know about or list > firewall configuration information. > > iptables is the command-line tool to view, add, delete, or change > firewall rules. > > # iptables -L# lists default table rules > > # iptables -L |

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Peter G. wrote: > Doesn't that mean the firewall is open on port 22 (for both ipv4/6, even)? netstat lists network port information. It does not know about or list firewall configuration information. iptables is the command-line tool to view, add, delete, or change firewall rules. # iptables -

Re: setting up ssh

2011-08-26 Thread Peter G.
Michael Cronenworth wrote: > Is the firewall on both machines configure to allow port 22 through? I think so. I unclicked and reclicked ssh in the firewall configuration, then apply. Then I restarted sshd.service on both computers and on both computers netstat showed: tcp0 0 0.0.

Re: setting up ssh

2011-08-26 Thread Michael Cronenworth
Peter G. wrote: > What is happening? How can I get the computers to communicate? Is the firewall on both machines configure to allow port 22 through? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test