• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Suse 10.1: does ssh work for anyone else?

N

n0cmonkey

Elite Member
I installed Suse 10.1 in VMWare, and it refuses to allow ssh connections. I can't even ssh to localhost on the machine.

Any ideas?

I've removed the stupid firewall rules (asses setting up a bunch of rules on install, how retarded), and modified the sshd_config since it only wanted to listen on the ipv6 address (which isn't even setup).
 
Never set up ssh before. I could maybe learn about it and test it out tomorrow. I never install software firewalls on my pc and always turn them off on first install. I just keep mine updated on my router (WRT54G).
 
Hmmm, it just worked locally, but not from a "remote" VMWare session. I flushed the firewall and it won't even work locally now. 😕
 
It's a firewall issue. Flushing iptables _should_ have solved it, but I guess mild retardation runs deep in Suse. I re-enabled the firewall and set a rule for ssh and it works.

Why doesn't it work when the firewall is turned off? 😕
 
Wow , I didn't know that . I always assumed , that after an iptables flush the default policy rules would take effect
 
Originally posted by: djdrastic
Wow , I didn't know that . I always assumed , that after an iptables flush the default policy rules would take effect
Click to expand...

That's probably how it works, but I think that's stupid. To me, a firewall should do what's in the rules, that's why if you want a default drop you have a catch-all default drop rule.

How in the hell would I fix this if that default drop isn't a rule? 😕
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top