Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

novncproxy_base_url may be incorrect? #4

Closed
samos123 opened this issue Apr 2, 2013 · 4 comments
Closed

novncproxy_base_url may be incorrect? #4

samos123 opened this issue Apr 2, 2013 · 4 comments

Comments

@samos123
Copy link

samos123 commented Apr 2, 2013

Would this make more sense?

change
novncproxy_base_url=http://100.10.10.51:6080/vnc_auto.html
to
novncproxy_base_url=http://192.168.100.51:6080/vnc_auto.html

Else only people who have access to the management network can use VNC right?

Are you able to use VNC within Horizon if you use novncproxy_base_url=http://100.10.10.51:6080/vnc_auto.html ?

@bilelmsekni
Copy link
Owner

Hello Sam,

You are 100% correct ! I have changed the novncproxy_base_url to
http://192.168.100.51:6080/vnc_auto.html and it is currently working fine !

Thank you for your feedback

regards,
Bilel

2013/4/2 Sam Stoelinga notifications@github.com

Would this make more sense?

change
novncproxy_base_url=http://100.10.10.51:6080/vnc_auto.html
to
novncproxy_base_url=http://192.168.100.51:6080/vnc_auto.html

Else only people who have access to the management network can use VNC
right?

Are you able to use VNC within Horizon if you use novncproxy_base_url=
http://100.10.10.51:6080/vnc_auto.html ?


Reply to this email directly or view it on GitHubhttps://github.com//issues/4
.

Best regards,

Bilel Msekni | Research & Development Engineer
Institut Mines-Telecom | TELECOM & Management SudParis
9 rue Charles Fourier, 91011 EVRY Cedex, France
Mobile: +33 6 49 52 42 17

@samos123
Copy link
Author

samos123 commented Apr 3, 2013

Hehe np thanks for confirming it, I thought your almighty guide was probably right and my own thinking may be wrong haha.

I think the guide would make more sense also if you used a private network ip range for the management network such as 192.168.x.x or 10.0.0.x or 172.16.xxx. This is what I mean: http://www.rfc-editor.org/rfc/rfc1918.txt

  1. Private Address Space

    The Internet Assigned Numbers Authority (IANA) has reserved the
    following three blocks of the IP address space for private internets:

    10.0.0.0 - 10.255.255.255 (10/8 prefix)
    172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
    192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

Summary: Suggestion to use following ips: 172.16.0.0 for management network (Normally not used in offices) and 192.168.100.0/24 for the public ip.

Great job on the guide, will try it in virtualbox later, did you ever get quantum working in virtualbox? I've never succeeded to get network and internet access on an instance while using quantum inside virtualbox.

@bilelmsekni
Copy link
Owner

Great idea ! will do this too and your name to the contributor list ;)

I have been doing bare metal deployment but will be doing a multi node
install using VMs soon.
I will get back to you when i finish.

regards,
Bilel

2013/4/3 Sam Stoelinga notifications@github.com

Hehe np thanks for confirming it, I thought your almighty guide was
probably right and my own thinking may be wrong haha.

I think the guide would make more sense also if you used a private network
ip range for the management network such as 192.168.x.x or 10.0.0.x or
172.16.xxx. This is what I mean: http://www.rfc-editor.org/rfc/rfc1918.txt

Private Address Space

The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

Summary: Suggestion to use following ips: 172.16.0.0 for management
network (Normally not used in offices) and 192.168.100.0/24 for the
public ip.

Great job on the guide, will try it in virtualbox later, did you ever get
quantum working in virtualbox? I've never succeeded to get network and
internet access on an instance while using quantum inside virtualbox.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-15826147
.

Best regards,

Bilel Msekni | Research & Development Engineer
Institut Mines-Telecom | TELECOM & Management SudParis
9 rue Charles Fourier, 91011 EVRY Cedex, France
Mobile: +33 6 49 52 42 17

@bilelmsekni
Copy link
Owner

Can't seem to find your E-mail, can you provide me with one please ?

2013/4/3 Msekni Bilel msekni.bilel@gmail.com

Great idea ! will do this too and your name to the contributor list ;)

I have been doing bare metal deployment but will be doing a multi node
install using VMs soon.
I will get back to you when i finish.

regards,
Bilel

2013/4/3 Sam Stoelinga notifications@github.com

Hehe np thanks for confirming it, I thought your almighty guide was
probably right and my own thinking may be wrong haha.

I think the guide would make more sense also if you used a private
network ip range for the management network such as 192.168.x.x or 10.0.0.x
or 172.16.xxx. This is what I mean:
http://www.rfc-editor.org/rfc/rfc1918.txt

Private Address Space

The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

Summary: Suggestion to use following ips: 172.16.0.0 for management
network (Normally not used in offices) and 192.168.100.0/24 for the
public ip.

Great job on the guide, will try it in virtualbox later, did you ever get
quantum working in virtualbox? I've never succeeded to get network and
internet access on an instance while using quantum inside virtualbox.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-15826147
.

Best regards,

Bilel Msekni | Research & Development Engineer
Institut Mines-Telecom | TELECOM & Management SudParis
9 rue Charles Fourier, 91011 EVRY Cedex, France
Mobile: +33 6 49 52 42 17

Best regards,

Bilel Msekni | Research & Development Engineer
Institut Mines-Telecom | TELECOM & Management SudParis
9 rue Charles Fourier, 91011 EVRY Cedex, France
Mobile: +33 6 49 52 42 17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants