BASIC principles of VBOX

[88supra86]

ok ppl keep asking me why they cant get the vbox live.

let me put it in basics.

theres your ROUTER... then theres your COMPUTER.... thats 1 link..

you need to open those ports on the computer to the router...

NOW with Vbox it goes this way.....

Router -> Computer -> Vbox.. your vbox runs through your computer.

SO you need to open the ports on the COMPUTER AND THE VBOX.

worse case scenario you DMZ your PC... basicly makes you attackable for hacking your stuff and doing whatever to your PC. but your VBOX is secure. (so delete your porn and your gf's pics ROFL)

think of your COMPUTER (PC) as a router as well. unless you got some spiffy router system (not sure if this type exists)_you need to add the ports from your COMPUTER.... AND YOUR VBOX. this some routers will allow. might give you an error saying your router has already added this permission to another PC... then your outta luck unless you DMZ your PC

although you can DMZ your VBOX and add the ports to your PC making it secure as your PC will only allow those ports to send information

if your VBOX has the ports open... THE PC its self DOES NOT... causing a BLOCK...

heres my tutorial on VBOX

http://forum.ragezone.com/f695/live-...t-play-737579/

please stop pming me or messaging me on skype. i cant keep helping people with there VBOX.

i may have some information mixed or backwards but i re read it and it seems strait forward to me.

Good Luck and happy ummm Servering...

*face palm* nothing fun about maintaining a server




OH and if this actually helps you... dont forget to like... (at least give back that way if nothing else lol)

[MentaL]

[das7002]

Ack .-.

Just use vbox nat and vbox port forward and tada, works better then host-only or bridged and I love that it was added.

(instead of vbox machine getting its own IP like in bridged vbox just maps ports to the host system so you could use 127.0.0.1:29000 on the host while your LAN is also still valid for port forwarding to the outside world)

[88supra86]

ya thats in the new version, a lot of people still like the older one for some reason.

i havent actually tried the new one but good idea tho.

are friends and people outside your network able to connect.

love the blue writing by the way ROFL took a moment for me to see there were words in it

ill get the new one and try it out. even tho my server is on a dedicated machine but would be cool to see

[das7002]

ya thats in the new version, a lot of people still like the older one for some reason.

i havent actually tried the new one but good idea tho.

are friends and people outside your network able to connect.

love the blue writing by the way ROFL took a moment for me to see there were words in it

ill get the new one and try it out. even tho my server is on a dedicated machine but would be cool to see

Yes you can use it outside the network, like I said it basically just binds the ports to the host and then forwards into the VM. I only have 127.0.0.1 there as a limit for that VM because I only wanted that particular machine to be able to connect. If the limits were left blank it just accepts from any IP address (similar to 0.0.0.0). You could use port forwarding on the router to the host machine's IP and the outside world can connect to the VM.

[Hunter]

what would you put for Host-only Network Details?
just your main ip or local ip?

[alif]

what would you put for Host-only Network Details?
just your main ip or local ip?

you don't need to put your IP their if you use NAT
but if you use host-only you must put your local IP there

[Hunter]

Ok thanks,and what ip's do i put for tomcat, webmin and the others.
And what ip do i put into Host-Only Network Details?
Like IPc4 address?

[das7002]

Ok thanks,and what ip's do i put for tomcat, webmin and the others.
And what ip do i put into Host-Only Network Details?
Like IPc4 address?

0.0.0.0, virtualbox assigns it with its builtin DHCP server. Then using its magical port rerouting it also has builtin you don't have to worry about any of that. From a network standpoint (as long as you leave the Host IP column blank) all of those ports are your systems own. From the same machine as Virtualbox you'd be able to use 127.0.0.1 for everything and from others on LAN your LAN IP would do and on your router it's also your LAN IP.

Long story short, I always hated host only network, don't use it, ever. Bridged is great if you want the virtual machine to get its OWN lan IP from your router.

[NeOCzx]

Hmm.. so when we using NAT..
do we need to add adapter to linux (like editing /etc/network/interfaces)
to make it work with VBOX NAT?