|
|
Sponsored Content
Operating Systems
Linux
Interesting challenge getting SSH from outside to my VMWare guest
Post 302469114 by brightstorm on Thursday 4th of November 2010 07:22:17 PM
11-04-2010
Interesting challenge getting SSH from outside to my VMWare guest
Hi,
I'm working on getting more acquainted with VMWare and the SUSE SLES OS, so I've downloaded and created a guest running SLES 11 SP1. This works great, no problems. However, there's some funny-ness (is that a word?) when I'm attempting/testing to SSH from outside my local LAN into the guest.
Let my sum up my setup:
The VMWare server
- Is a Windows 7 with LAN-ip 192.168.1.66 (static).
- The guest is running with a bridged configuration, not NAT.
- Windows Firewall has been disabled in an attempt to get some data in the SUSE firewall logs.
Another PC in my LAN
- Is also a Windows 7 with LAN-ip 192.168.1.65 (also static).
- Connects just fine to the VMWare guest on 192.168.1.77 (see next section).
- Has Windows Firewall running fine (also attempted to disable)
The SLES guest
- Is configured with LAN-ip 192.168.1.77 (also static, obviously).
- SSH port has been changed from 22 -> 1337.
- The SUSE firewall allows SSH from 192.168.1.0/24 to make it accessible from my LAN area (this is going to be narrowed down later, just to please the security minded people
)
- The SUSE firewall DOES NOT allow SSH from outside the LAN, but should be allowed on a IP-by-IP basis.
External Linux Debian VPS
I have an external Linux Debian VPS solution. When I ssh to my WAN IP from this, and supplying port 1337, it just eventually times out, clearly indicating something's amiss somewhere in my configuration.
My ISP-provided router setup
- Portforwards port 1337 to 192.168.1.77
So, what I'm pondering about is what I can try to get the traffic actually arriving at my guest. I have read alot about running the guest in NAT configuration and then using the VMWare tools to portforward port X to the VMWare's assigned IP address.
I am not really very experienced in networking (which is why I'd really like to avoid a NAT solution until I get a hold of stuff), but I have the idea that if I without further ado can access my VMWare guest from my local LAN just by providing the statically assigned IP, I would figure that I'd get it off just by portforwarding the assigned SSH port directly to my guest's IP?
I hope that I have provided sufficient information but if not I shall happily provide additional details as necessary. I hope that you might be able to push me in the right direction
I'm working on getting more acquainted with VMWare and the SUSE SLES OS, so I've downloaded and created a guest running SLES 11 SP1. This works great, no problems. However, there's some funny-ness (is that a word?) when I'm attempting/testing to SSH from outside my local LAN into the guest.
Let my sum up my setup:
The VMWare server
- Is a Windows 7 with LAN-ip 192.168.1.66 (static).
- The guest is running with a bridged configuration, not NAT.
- Windows Firewall has been disabled in an attempt to get some data in the SUSE firewall logs.
Another PC in my LAN
- Is also a Windows 7 with LAN-ip 192.168.1.65 (also static).
- Connects just fine to the VMWare guest on 192.168.1.77 (see next section).
- Has Windows Firewall running fine (also attempted to disable)
The SLES guest
- Is configured with LAN-ip 192.168.1.77 (also static, obviously).
- SSH port has been changed from 22 -> 1337.
- The SUSE firewall allows SSH from 192.168.1.0/24 to make it accessible from my LAN area (this is going to be narrowed down later, just to please the security minded people
)- The SUSE firewall DOES NOT allow SSH from outside the LAN, but should be allowed on a IP-by-IP basis.
External Linux Debian VPS
I have an external Linux Debian VPS solution. When I ssh to my WAN IP from this, and supplying port 1337, it just eventually times out, clearly indicating something's amiss somewhere in my configuration.
My ISP-provided router setup
- Portforwards port 1337 to 192.168.1.77
So, what I'm pondering about is what I can try to get the traffic actually arriving at my guest. I have read alot about running the guest in NAT configuration and then using the VMWare tools to portforward port X to the VMWare's assigned IP address.
I am not really very experienced in networking (which is why I'd really like to avoid a NAT solution until I get a hold of stuff), but I have the idea that if I without further ado can access my VMWare guest from my local LAN just by providing the statically assigned IP, I would figure that I'd get it off just by portforwarding the assigned SSH port directly to my guest's IP?
I hope that I have provided sufficient information but if not I shall happily provide additional details as necessary. I hope that you might be able to push me in the right direction
|
|
9 More Discussions You Might Find Interesting
1. Solaris
hi All,
I require your help and suggestion in this. I have a solaris 10 (guest) installed on a vmware and my host OS is windows 2003 server. i am trying to conenct to the solaris 10 from my local Pc through putty, but unable to connect. please advice what setup or prerequitsites are required to... (4 Replies)
Discussion started by: bathija
4 Replies
2. Virtualization and Cloud Computing
Is there any command in VMware Server 2.0 to poweron/start the guests like we have vmware-cmd ESX server 3.5 .. (1 Reply)
Discussion started by: fugitive
1 Replies
3. Red Hat
Hello i have CentOS installed on vmware , few days ago every thing was working fine. today every time im connect with putty to the CentOs server after few minutes it disconnect me , how can i find what is the reason ? (5 Replies)
Discussion started by: umen
5 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I have a Solaris 10 x86 VM and I am trying to access the Solaris install menu.
I have the ISO set to connect on startup, and I can see that it is mounted in my system. But when I power on the VM, the GRUB menu comes up and I only have the option of booting Solaris.
Also I have... (4 Replies)
Discussion started by: bstring
4 Replies
5. Ubuntu
Hello,
Please, I would like to connect a VM to another:
I typed as follows:
ssh root@192.168.1.4
root@192.168.1.4 's password:
Permission denied, please try again.
root@192.168.1.4 's password:
Permission denied, please try again.
root@192.168.1.4 's password:
Permission denied... (6 Replies)
Discussion started by: chercheur111
6 Replies
6. UNIX for Advanced & Expert Users
I have a log with entries like:
out/target/product/imx53_smd/obj/STATIC_LIBRARIES/libwebcore_intermediates/Source/WebCore/bindings/V8HTMLVideoElement.cpp
: target thumb C++: libwebcore <=... (8 Replies)
Discussion started by: glev2005
8 Replies
7. Solaris
I swear I have no other devices on the vmnet 192.168.142.2, but after I configured one of the solaris x86 os, I kept getting warning ..node xx xxxxx have our ip addresss 192.168.142.2, and it scrolled thru it forever ..
I tried to boot it into single user mode , still having the same issue..
... (1 Reply)
Discussion started by: ppchu99
1 Replies
8. Shell Programming and Scripting
I have searched through google, and this forum to try and find the answer, but alas, nothing quite hits the whole answer.
I am trying to read the last line (or lines) of some log files. I do this often.
The files are named sequentially, using the date as part of the file name, and appending... (18 Replies)
Discussion started by: BatterBits
18 Replies
9. UNIX for Dummies Questions & Answers
Hi!
I am not sure if this is the right place to post this question. What I did was to download vmware onto my laptop, them install a linux distro as a guest O.S., on VM network configuration I have used "bridge", them I used Virtual Network Editor to chose the network interface, but as I write... (4 Replies)
Discussion started by: fretagi
4 Replies
LEARN ABOUT MOJAVE
sharing
sharing(8) BSD System Manager's Manual sharing(8) NAME
sharing -- create share points for afp and smb services. SYNOPSIS
sharing [-a <path> [options]] [-e <share point name> [options]] [-r <share point name>] [-l] DESCRIPTION
A list of flags and their descriptions: -a <path> Add a new share point for the directory specified by <path>. -e <share point name> Edit the share point record specified by <share point name>. -r <share point name> Delete the share point record specified by <share point name>. -l List all existing share point records. The following options modify share point record attributes: -A <afp name> Use customized name <afp name> when using share point with afp. -S <smb name> Use customized name <smb name> when using share points with smb. -s <flags> Use this option to enable and disable sharing via afp and smb. By default a share point is enabled for afp and smb protocols. To enable and disable particular services, combine (binary AND) the following flags as required: 100 (enable sharing for afp) and 001 (enable sharing for smb). Specify 000 to turn off sharing of a share point altogether. -g <guest flag> Use this option to enable and disable guest access for afp and smb. By default guest access is enabled for afp and smb. To enable and disable guest access to particular services, combine (binary AND) the following flags as required: 100 (enable guest for afp) and 001 (enable guest for smb). Specify 000 to turn off guest access for a share point altogether. -i <inherit privileges flag> Use this option to enable and disable the "inherit privileges" attribute for afp. By default "inherit privileges" is enabled for afp. To enable "inherit privileges", combine (binary AND) the following flags as required: 10 ("inherit privileges" for afp). Specify 00 to turn off "inherit privileges" for a share point altogether. -n <customized record name> Specify a <customized record name> to be used as the share point record name. By default the record name is the name of the direc- tory pointed to by the share point record. This directory is specified by the <path> when the record is created. EXAMPLES
/usr/sbin/sharing -a /SomePath/ShareThisDirectory This example shows how to create a share point for the directory "/SomePath/ShareThisDirectory": /usr/sbin/sharing -e ShareThisDirectory -A SP1 -g 101 This example shows how to edit the share point record created above, adding a customized name "SP1" for afp servies, and enabling guest access only for afp and smb. FILES
/usr/sbin/sharing location of tool macOS June 1, 2019 macOS