Prev: detachtty problems
Next: problem loading trivial-features ...
From: Captain Obvious on 17 Jul 2010 09:01
HB> I have (at Session menu) destination address and port:
HB> 192.168.56.1 (ip address of VM linux) and port 4005,

You should have default SSH port 22 in here.

We do it in three steps:

1. connect via SSH normally
2. launch SBCL with swank server on port 4005
3. connect to that swank server through tunnel

So port 4005 comes to existance on the second step and it does not even
exist on the first step.

HB> and at Tunnels menu I have source port 4005 and destination
HB> localhost:4005.

And here port 4005 is correct, but we need it only on the third step.

HB> Do I have to turn off Ubuntu firewall or open port 4005 ?

No, Ubuntu doesn't have firewall by default, but probably it doesn't have
SSH server either.
So you need to install SSH server, package is called openssh-server.
You can use your favourite installation manager, or if you don't have
favourite I recommend aptitude:

aptitude install openssh-server

This will either install it or say that it is already installed.

From: Haris Bogdanovic on 17 Jul 2010 11:52
I installed openssh-server and started it:
/etc/init.d/ssh start
I then typed: iptables -L
to remove default firewall rules
and then I get "connection refused" again.
I use ip address 192.168.56.1 which is in
Network connections -> VirtualBox Host only netwoek (on windows)
which I can ping. When I type ifconfig -a (Ubuntu) I get 10.0.2.15
which I cannot ping and typing "ip address" in google I get the same ip
addess
like in google on windows so that's the outside address of my router so
the ip address of VM Ubuntu must be 192.168.56.1.
Why I always get connection refused ?
As I said Putty Session destination ip address is 192.168.56.1 on port 22.
Tunnel settings are: source port 4005 and destination: localhost:4005


From: D Herring on 17 Jul 2010 12:10
On 07/17/2010 11:52 AM, Haris Bogdanovic wrote:
> I installed openssh-server and started it:
> /etc/init.d/ssh start
> I then typed: iptables -L
> to remove default firewall rules
> and then I get "connection refused" again.
> I use ip address 192.168.56.1 which is in
> Network connections -> VirtualBox Host only netwoek (on windows)
> which I can ping. When I type ifconfig -a (Ubuntu) I get 10.0.2.15
> which I cannot ping and typing "ip address" in google I get the same ip
> addess
> like in google on windows so that's the outside address of my router so
> the ip address of VM Ubuntu must be 192.168.56.1.
> Why I always get connection refused ?
> As I said Putty Session destination ip address is 192.168.56.1 on port 22.
> Tunnel settings are: source port 4005 and destination: localhost:4005

Ok. This looks like a network configuration issue. Try telling
Ubuntu to use IP 192.168.56.1 or 192.168.56.101.

If that doesn't work, try asking the VirtualBox people how to get it
working.

- Daniel
From: Haris Bogdanovic on 17 Jul 2010 16:29
Which virtual machine you use so that works for you,
wmware or ms virtual pc ?


From: Captain Obvious on 18 Jul 2010 12:44
Well I guess your problem is that you have IP address configuration problem.
I'm not familiar with VirtualBox so I can't help here, and actually this
topic isn't even remotely ontopic in comp.lang.lisp.
Try asking in groups which are related to VirtualBox, Linux or networking
configuration.

HB> I installed openssh-server and started it:
HB> /etc/init.d/ssh start
HB> I then typed: iptables -L
HB> to remove default firewall rules
HB> and then I get "connection refused" again.
HB> I use ip address 192.168.56.1 which is in
HB> Network connections -> VirtualBox Host only netwoek (on windows)

You've misunderstood this.
"Network connections" item represents IP address of Windows machine in the
VirtualBox'es host-only network.

Subnetwork is sort of an address space -- computers within network can
directly see each other but they cannot communicate with computers on
different subnetworks without routing.

VirtualBox have made a new subnetwork which is used as host only. It has IP
addresses in form of 192.168.56.x.
Your Windows host machine needs a network adapter and an IP address to be
able to work with this network.

The network adapter is the thing you see in Network connections (it is
virtual, of course), and Windows host's IP address is 192.168.56.1.

But your Linux VM probably haven't got connected to this network because you
didn't it configure it to do so.

I dunno how you do this in VBox. I'm more familiar with VMware -- there is
network adapters section and you can configure VM to use any number of
networks.

Note that if you leave only host-only then VM won't be able to download
stuff from the internet.

HB> which I can ping. When I type ifconfig -a (Ubuntu) I get 10.0.2.15

This is the address your virtual machine have got. I have no idea what does
it mean in your network. Perhaps VM is directly connected to LAN (it is
called "bridged networking") or something.

Most likely you've configured VM networking as bridged and it got IP address
from your router.

HB> which I cannot ping

This is kinda strange. If my guess is true, then networking on Windows in
mis-configured. Or your router is mis-configured.

If Windows host and Linux VM are on same subnet (I dunno, perhaps 10.0.2.x?)
then they should be able to speak with each other directly.
They won't be able to do so if subnet is mis-configured. It should be
255.255.255.0 or 255.255.0.0, but probably you've set it to 255.255.255.255
and that's why it doesn't work.

So, perhaps, you just need to configure you Windows machine correctly and it
will just work with IP address 10.0.2.15.

But that's a speculation, I haven't seen your network settings, of course.

HB> and typing "ip address" in google I get the same ip addess
HB> like in google on windows
HB> so that's the outside address of my router

This means that your VM can speak with your router. We don't even know if it
speaks directly or through VBox NAT.

HB> so the ip address of VM Ubuntu must be 192.168.56.1.

No, it is not.

HB> Why I always get connection refused ?

Because it is wrong.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: detachtty problems
Next: problem loading trivial-features ...