i read the admin guide, but wasnt' able to find anything except using ipfilter to filter out either telnet or ssh, but is there a way to natively enable/disable either protocol?
ok, i found the answer to my previous question is yes, i locked myself out, i can connect to console though, but when i try to delete the new rule i just created, it says,
i tried both removing the policy and removing the rule that denies telnet connection which is the #1 rule and the only rule in the policy, here's the commands i tried
dynamox
9 Legend
•
20.4K Posts
0
February 26th, 2009 10:00
dynamox
9 Legend
•
20.4K Posts
1
February 25th, 2009 13:00
To disable telnet:
ipfilter --create block_telnet_v4 --type ipv4
ipfilter --addrule block_telnet_v4 -rule 2 -sip any -dp 23 -proto tcp -act deny
ipfilter --save block_telnet_v4
ipfilter --activate block_telnet_v4
To re-enable telnet:
ipfilter --delete block_telnet_v4
ipfilter --save
...to do ssh ..change port 23 to 22.
tomrbc
80 Posts
0
February 25th, 2009 13:00
tomrbc
80 Posts
0
February 25th, 2009 15:00
tomrbc
80 Posts
0
February 25th, 2009 15:00
Not owner of the current transaction
help!
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 15:00
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 15:00
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 15:00
ipfilter ¿-transabort
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 15:00
tomrbc
80 Posts
0
February 25th, 2009 15:00
anyhow, do i have to create another rule to state any other traffic is allowed?
tomrbc
80 Posts
0
February 25th, 2009 16:00
ipfilter --delete block_telnet
ipfilter --delrule block_telnet -rule 1
the response to both commands is
Not owner of the current transaction
and yes, i tried "ipfilter --transabort", it took it but doesn't seem to do anything for me, i'm still locked out
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 16:00
tomrbc
80 Posts
0
February 25th, 2009 16:00
tomrbc
80 Posts
0
February 25th, 2009 16:00
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 17:00