Happy birthday! :3
Aww!💕 thank you!
seen from Yemen

seen from Japan
seen from United States
seen from China
seen from Italy
seen from United States

seen from United Kingdom

seen from Canada

seen from Malaysia
seen from United States

seen from United Kingdom

seen from France
seen from Canada
seen from Malaysia

seen from United Kingdom
seen from China

seen from United States
seen from Germany
seen from United States
seen from Poland
Happy birthday! :3
Aww!💕 thank you!
I made a thing. Look at the thing!
Reminder on iptables configs CentOS6.5 and earlier
lokkit: Seems like a standard. AKA system-config-firewall-base in RH-land. Is used in a lot of puppet manifests floating around the foreman-associated projects and in SaltStack. Simple configuration, e.g.
lokkit --list-services
, add a hole for SSH
lokkit --service=ssh
or
lokkit --port=ssh:tcp
firewalld: in Fedora20 and CentOS7. This is a dynamic firewall configuration daemon (uses dbus) which can co-exist with lokkit.
The alternatives are? Shorewall? Just run iptables commands?
Debian got rid of it, claiming it was buggy and unmaintained.
NB: netstat-nat is interesting.
Using lokkit to handle your firewall.
Some common thing is to turn of the firewall if a freshly installed machine isn't reachable from the outside, as fidling with iptables is not everyones passion. lokkit is another way to open some ports to the public. Just use
$ sudo lokkit --list-services
to see what services/ports can be managed/opened using lokkit. For me it's quite common to open ports for ssh, ipsec and mdns afer a fresh installation
$ sudo lokkit -s ssh $ sudo lokkit -s mdns $ sudo lokkit -s ipsec
Let's see if there will be something new in the near future to handle - somtimes quite complex (see virtualization) - iptable setups.
The IT sector has gained great momentum in today's times and a large number of people have understood the benefits of working in the IT sector.