vrdp listen address

680 views
Skip to first unread message

jemi...@kcg.com

unread,
Mar 4, 2016, 11:09:22 AM3/4/16
to Packer
From the docs, packer will use a random port for vrdp which you can change.  However the listen host is fixed to locahost.  Is it possible to change this to listen on all interfaces (0.0.0.0)?

Thanks

Packer uses a randomly chosen port in this range that appears available. By default this is 5900 to 6000. The minimum and maximum ports are inclusive.

Bernd Naumann

unread,
Mar 4, 2016, 11:53:29 AM3/4/16
to packe...@googlegroups.com
On 03/04/2016 05:09 PM, jemi...@kcg.com wrote:
> From the docs, packer will use a random port for vrdp which you can
> change. However the listen host is fixed to locahost. Is it possible
> to change this to listen on all interfaces (0.0.0.0)?
>
> Thanks

Greetings,

I do not know if it is possible to specify the interface/ip, but a
workaround is:

local$ ssh -N -L <local-port>:localhost:<remote-port> <remote-host>

and then use the local-port for the remote-screen...


Bernd

jemi...@kcg.com

unread,
Mar 4, 2016, 1:10:01 PM3/4/16
to Packer
Thanks for the suggestion.  This is part of an automated install so I'd like for it to just work for from anywhere.  I also run multiple of these instances in parallel making this a little hacky.

Jeremy

jemi...@kcg.com

unread,
Mar 4, 2016, 1:12:12 PM3/4/16
to Packer
I should also add this behavior is changed from the previous version.  If you didn't specify a vrdp port it would listen on 0.0.0.0:3389 (RDP default)

Ian Duffy

unread,
Mar 4, 2016, 2:21:23 PM3/4/16
to packe...@googlegroups.com
Is it possible to change this to listen on all interfaces (0.0.0.0)?

No, Its hardcoded at 127.0.0.1 see https://github.com/mitchellh/packer/blob/master/builder/virtualbox/common/step_configure_vrdp.go#L54

Feel free to open a pull request.....

If you didn't specify a vrdp port it would listen on 0.0.0.0:3389 (RDP default)

Not with virtualbox, before this version exposing of the virtualbox console wasn't possible. vrdp support is new and the only way virtualbox exposes its consoles in a headless manor. 

Other build providers such as vmware to use rdp. 


On 4 March 2016 at 18:12, <jemi...@kcg.com> wrote:
I should also add this behavior is changed from the previous version.  If you didn't specify a vrdp port it would listen on 0.0.0.0:3389 (RDP default)

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/d8dc8b02-d587-4447-bb37-9ad3da22d89d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Bernd Naumann

unread,
Mar 5, 2016, 10:17:17 AM3/5/16
to packe...@googlegroups.com
On 03/04/2016 07:10 PM, jemi...@kcg.com wrote:
> Thanks for the suggestion. This is part of an automated install so I'd
> like for it to just work for from anywhere. I also run multiple of
> these instances in parallel making this a little hacky.
>
> Jeremy
>
> On Friday, March 4, 2016 at 11:53:29 AM UTC-5, Bernd Naumann wrote:

If you have multiple templates you can specify one port per template.
(But this doesn't make the setup easier) I also would like to specify
"listen on all interfaces" and avoid the ssh workaround. But mostly I do
this while debugging a new setups. If a template is working fine, the
job runs periodically anyway without supervision.

Bernd

martin...@gmail.com

unread,
Aug 24, 2016, 4:54:04 AM8/24/16
to Packer
Yes, if you add

       "vboxmanage": [
        [ "modifyvm", "{{.Name}}", "--vrdeaddress", "0.0.0.0" ]
      ]

to the virtualbox builder, it will change it from listening from 127.0.0.1 to 0.0.0.0, although the packer output will still say it's listening on 127.0.0.1, netstat shows that it's on 0.0.0.0 and you can connect from other machines.

Rickard von Essen

unread,
Aug 24, 2016, 5:53:22 AM8/24/16
to packe...@googlegroups.com
See the top of https://github.com/mitchellh/packer/blob/master/CHANGELOG.md

Packer will now only use 127.0.0.1 for vrdp, this change will be in the next release.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/d1af0ef7-9ae8-4673-b86c-1eafa009b5e3%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages