Reputation
966
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 12
Newest
 Yearling
Impact
~21k people reached

Feb
22
revised local SSH works when using “localhost”, but not using IP address
deleted 7 characters in body
Feb
22
comment What is wrong with this cron tab entry?
Traditionally, there is comment line with the column titles above the first entry. Make sure your line matches the syntax. In Ubuntu, for instance, your line would be incorrect. BTW, what distro are you using?
Feb
22
comment local SSH works when using “localhost”, but not using IP address
Connection to 192.168.2.12:22 establishes, it is clear from debug messages. Localhost connection succeeds because of faster local authentication - it fits the LoginGraceTime period.
Feb
22
revised local SSH works when using “localhost”, but not using IP address
added 174 characters in body
Feb
22
awarded  Commentator
Feb
22
comment Active Directory and Exchange in one Server
It should be clear that if several applications want to write to disc simultaneously, the have to share the resources. It means that every app would write to disc twice slower than it could. In addition, Exchange may provide service for external users or for remote workers, thus being accessible from the outer world (internet). It raises the chance to be under attack. AD is vital for the whole infrastructure and it provides no service for outer world. That is why it must be accessible only from LAN. Having both services in single box, it is impossible to reliably protect AD.
Feb
22
comment Active Directory and Exchange in one Server
I mention the most important reasons and they are sufficient to set up services separately. But okay. In addition: performance (as tombull says), access delegation for company admins, public access (exchange should be accessible from the internet, AD - never).
Feb
22
answered local SSH works when using “localhost”, but not using IP address
Feb
22
answered Active Directory and Exchange in one Server
Feb
21
comment local SSH works when using “localhost”, but not using IP address
How long does it take from pressing Enter after ssh -v jane@192.168.2.12 to Connection closed by 192.168.2.12? 10 second? Maybe 30?
Feb
21
comment Privileges for ifconfig
Yes, you are right, but ip is still much more convenient (unless you're on BSD system).
Feb
20
awarded  Editor
Feb
20
revised Privileges for ifconfig
edited body
Feb
20
answered Privileges for ifconfig
Feb
20
comment Setting up IP masquerading by passing packets through external nodes
Ok. You might set up a pool of VPS = a pool of "frontend" IP addresses. Then set up a point-to-point VPN connection from root to each VPS. Then set up default route and routes balancing on your root server, which now have 4 uplinks through VPNs (lartc.org/howto/lartc.rpdb.multiple-links.html - it should help with that). Now, if any of VPS is under attack and not responding, you can use the others or set up a new VPS from different provider.
Feb
20
comment Setting up IP masquerading by passing packets through external nodes
No, I mean - if you have a website on your root server (as far as i see on a diagram), it means you are listening port 80. In such case, you definitely cannot control who would be trying to connect to your server through port 80. However, if you aren't listening on any port or if you want to have incoming connections only from known host, there is a decision.
Feb
20
comment Setting up IP masquerading by passing packets through external nodes
Does your root server provide service to the world? In such case you can not prevent it from being say DDoSed in this way.
Feb
20
answered Setting up IP masquerading by passing packets through external nodes
Feb
20
comment How to portforward with iptables?
Issue iptables -t nat -n -L -v and you will see your rule added to PREROUTING chain of nat table.
Jan
11
comment Prevent users to access to website using port 8080 (apache) when using Varnish (on port 80)
I've just edited the answer and included the example.