Clients on the private side of a jump box
-
Re: Linux Lab Project: Building a Linux Jump Box
Question in regards to the jump box and the clients on the private side.
If the jump box is sitting in line of the router to the Internet and to the switch to the rest of the network, do the clients internally have access to the Internet passively through the jump box?
-
Jump boxes are not networking devices. They should not be in the packet path for normal traffic in or out of a network. That's a firewall, not a jump box. Jump boxes are a break point, normal traffic would simply be blocked by one.
-
A Jump box is a proxy in the English sense, but not in the technical sense. No software on a Jump box does proxying.
-
I just think of another end point, when I hear you MSP guys talk about jump boxes, something inside the LAN, like any other end point.
-
@Donahue said in Clients on the private side of a jump box:
I just think of another end point, when I hear you MSP guys talk about jump boxes, something inside the LAN, like any other end point.
That is always my definition. I use my workstation in the office as a jump box when I am out of the office. I can remote into it via screenconnect and then remote into everything else.
-
We do jump boxes in a dedicated datacenter for general stuff, and often have one inside a customer network for work on their network.
-
Speaking of which, I need to go build a new jump box at a client site. MeshCentral makes our jump boxes more flexible.
-
@scottalanmiller said in Clients on the private side of a jump box:
Speaking of which, I need to go build a new jump box at a client site. MeshCentral makes our jump boxes more flexible.
I was following your thread on MC vs SC. What about MC makes it more flexible for your scenario?
-
@Donahue said in Clients on the private side of a jump box:
I just think of another end point, when I hear you MSP guys talk about jump boxes, something inside the LAN, like any other end point.
So endpoint over pass-through. Got it.
-
@wrx7m said in Clients on the private side of a jump box:
@scottalanmiller said in Clients on the private side of a jump box:
Speaking of which, I need to go build a new jump box at a client site. MeshCentral makes our jump boxes more flexible.
I was following your thread on MC vs SC. What about MC makes it more flexible for your scenario?
Cost, speed, development, support, etc.
We've already gotten better support for smaller issues in MC than SC provides when you pay an arm and a leg and it is show stopping stuff!
MC will save us something like $1600 a year, and provides some really nice features that we like. And seems to have a bright future. SC has appeared to have gotten worse, not better, in the last two years. That's not good when you are paying so much.
But we really like the insanely fast "in browser" connections in MC. SC causes so much delay that it is frustrating. Only a few seconds, but when you are trying to work, unnecessary stopping and waiting makes people frustrated.
