Local SSH Forwarding Port range change?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Local SSH Forwarding Port range change?

Kevin Jackson
Hi,
Is it possible to change the port forwarding port range used to connect to the local VMs?
Vagrant isn't able to detect the fact that 2200 is currently in use _outside_ of Vagrant/VirtualBox:

[controller] Importing base box 'precise64'...
[controller] Matching MAC address for NAT networking...
[controller] Setting the name of the VM...
[controller] Clearing any previously set forwarded ports...
[controller] Fixed port collision for 22 => 2222. Now on port 2200.
[controller] Creating shared folders metadata...
[controller] Clearing any previously set network interfaces...
[controller] Preparing network interfaces based on configuration...
[controller] Forwarding ports...
[controller] -- 22 => 2200 (adapter 1)
[controller] Running any VM customizations...
[controller] Booting VM...
[controller] Waiting for VM to boot. This can take a few minutes.

The

[controller] Fixed port collision for 22 => 2222. Now on port 2200.

Is my problem, where I already have a local service on localhost running on 2200.

Cheers,
Kev

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Local SSH Forwarding Port range change?

Mitchell Hashimoto
Kev,

Is this with 1.1? It should detect this. Either way, yes you can: config.vm.usable_port_range


Best,
Mitchell


On Sat, Apr 6, 2013 at 1:56 PM, Kevin Jackson <[hidden email]> wrote:
Hi,
Is it possible to change the port forwarding port range used to connect to the local VMs?
Vagrant isn't able to detect the fact that 2200 is currently in use _outside_ of Vagrant/VirtualBox:

[controller] Importing base box 'precise64'...
[controller] Matching MAC address for NAT networking...
[controller] Setting the name of the VM...
[controller] Clearing any previously set forwarded ports...
[controller] Fixed port collision for 22 => 2222. Now on port 2200.
[controller] Creating shared folders metadata...
[controller] Clearing any previously set network interfaces...
[controller] Preparing network interfaces based on configuration...
[controller] Forwarding ports...
[controller] -- 22 => 2200 (adapter 1)
[controller] Running any VM customizations...
[controller] Booting VM...
[controller] Waiting for VM to boot. This can take a few minutes.

The

[controller] Fixed port collision for 22 => 2222. Now on port 2200.

Is my problem, where I already have a local service on localhost running on 2200.

Cheers,
Kev

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Local SSH Forwarding Port range change?

Mitchell Hashimoto
Kev,


It will be part of the next release. In the mean time, just change the usable port range.

Best,
Mitchell


On Sat, Apr 6, 2013 at 2:03 PM, Mitchell Hashimoto <[hidden email]> wrote:
Kev,

Is this with 1.1? It should detect this. Either way, yes you can: config.vm.usable_port_range


Best,
Mitchell


On Sat, Apr 6, 2013 at 1:56 PM, Kevin Jackson <[hidden email]> wrote:
Hi,
Is it possible to change the port forwarding port range used to connect to the local VMs?
Vagrant isn't able to detect the fact that 2200 is currently in use _outside_ of Vagrant/VirtualBox:

[controller] Importing base box 'precise64'...
[controller] Matching MAC address for NAT networking...
[controller] Setting the name of the VM...
[controller] Clearing any previously set forwarded ports...
[controller] Fixed port collision for 22 => 2222. Now on port 2200.
[controller] Creating shared folders metadata...
[controller] Clearing any previously set network interfaces...
[controller] Preparing network interfaces based on configuration...
[controller] Forwarding ports...
[controller] -- 22 => 2200 (adapter 1)
[controller] Running any VM customizations...
[controller] Booting VM...
[controller] Waiting for VM to boot. This can take a few minutes.

The

[controller] Fixed port collision for 22 => 2222. Now on port 2200.

Is my problem, where I already have a local service on localhost running on 2200.

Cheers,
Kev

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 


--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Local SSH Forwarding Port range change?

Kevin Jackson
Thanks Mitchell. The usable_port_range fixed my issue.

Regards,
Kev

On Saturday, 6 April 2013 22:15:36 UTC+1, Mitchell Hashimoto wrote:
Kev,


It will be part of the next release. In the mean time, just change the usable port range.

Best,
Mitchell



--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.