On Tue, Dec 04, 2012 at 01:20:10PM -0500, Matthew Miller wrote: > On Tue, Dec 04, 2012 at 12:14:14PM -0600, Jeffrey Bastian wrote: > > as the default, even if I manually brought up the network with nmcli, I > > still could not ssh into the pandaboard. There's some funny interaction > > between NetworkManager and firewalld that blocks ssh if the network > > doesn't come up cleanly right away. > > That does not sound good. Is there a bug for that? Not yet. I'm not yet sure which component is to blame: NetworkManager, dbus, firewalld, openssh, selinux-policy, other? I generally saw this problem when: 1. Boot into graphical.target but using serial console 2. Login as root on serial console 3. Verify network is down: ip addr list eth0 4. Bring up eth0: nmcli con up id 'System eth0' 5. Verify network is up: ip addr list eth0 6. Try to ssh into the pandaboard from another system - FAIL 7. Back on the pandaboard serial console, verify ssh is running systemctl status sshd.service 8. Check firewall rules allow ssh systemctl status firewalld.service iptables -L 9. Turn off firewall systemctl stop firewalld.service iptables -F 10. Try ssh in again Does anybody else see this using the Pandaboard with serial console? Thanks! Jeff _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
