Setting Up Offline Mode - Cabal

[striker1010]

Hello All,

I was hoping if I could get some input from you guys regarding this situation. In one of my posts earlier, I had mentioned that I currently live under a "college community" system and was looking to make a private lan (solely for me) server. This is due to the fact that I am not admin on the router since it belongs to the school and as such can't set up port forwarding.

Now, while I was setting up VirtualBox, no matter what settings I messed around with, bridge networking refuses to give access to the internet and the only way to access the internet is via NAT setting.

So now, under the NAT setting the way I talk with the server is using port forward through virtual box. For example, to use winscp, I connect to my local host computer's lan IP but I have that port forwarded on virtual box to linux. Could I theoretically do the same thing with all other ports I will need to connect to the server and simply use my host lan ip in internal.txt which will get forwarded to linux?

Any input would be much appreciated.

Thank You.

[MentaL]

[wtvelocity]

Just set up all the address that would be your forward=facing IP to be 127.0.0.1.
First, either way you set this up, you should set network card to be "Bridged".

You want to connect to the VM through your network if possible, and even if ports are closed:
that's usually just to OUTSIDE traffic, unless they specifically program the router otherwise.
In other words, you should still be able to have the VM and your PC on the network with separate LAN IPs from that router.

If you can't even connect to the VM with WinSCP, I recommend getting your OWN router,
connecting through that, then having that connect to your network. Then your friends can also play on their laptops.
A cheap but good router would be a linksys e2000 or higher, and install Tomato firmware on it.
You can use it when you move then, as well, and not need to change much.

Now, provided you have it set it with BRIDGED:
For this example, your computer on the network is 192.168.1.120, and the IP for the VM is 192.168.1.123,
and your WAN IP (internet address given from whatsmyip or ipchicken) is 32.124.35.58:

Anything the tutorials says that's headed towards your WAN (Internet IP: 32.124.35.58)
should be changed instead to 192.168.1.123 (your VM, because that's what you would have port forwarded to).

The reasoning so you understand this, is ports usually only tell addresses OUTSIDE the network to go.
You don't usually need port forwarding to send traffic IN the network, that's what computer firewalls are for.
In short, anything that WOULD be port forwarded after going to your WAN (32.124.35.58),
is instead going directly to your server, no middle-man.

So, with all of that, the review here is:
Everything (including internal.txt) should be connecting to your VM's IP address once bridged.
If this works, it will also allow anyone connected to the same router as you, to connect as well.
Maybe not everyone in the building or campus, depending on how the routers are set, but anyone on the same router as you.

Let me know if you have more questions,
if this helps, hit like please? :P
<<<<<

[striker1010]

Thank you for the input, my problem is that when I use "bridged networking" with virtual box. It doesn't work. Under bridge networking, CentOs can't connect to internet > meaning no ip to use for Centos when I do "ifconfig" in terminal.

After playing around a bit, I started using "Host-Only Adapter" setting. This allows me to have a Lan IP finally but I then ran into an error where all services were good except for ChatNode, Loginsvr, EventMgr, Worldsvr. For some reason they won't run so reinstalling centos and seeing if that fixes anything.

Thanks for the response though. I still don't get why bridged isn't working for me.

[wtvelocity]

1) Are you using ORACLE for the VM
2) What version of Centos are you using? You need 5.8, using 5.9 or some others can make that happen.
3) You should still try to do it through Bridged: You may not have had the Linux network drivers installed or set up properly.
You should install 5.8 in Oracle, but have the hardware already set properly (including Network: bridged).

Otherwise, even if you get it working you may still have some odd problems you can't get help with....

[striker1010]

1) Yes
2) 5.8
3) Like I said, If I do bridged, I don't have a CentOS Ip to use. I will post screen shot in a bit so you can see.

[wtvelocity]

Ok, but as I said for #3, it means you likely don't have the internet actually set up properly for it,
or you installed the O.S. without it set on bridged, which means CentOS is using the wrong drivers.

I've personally ran into many odd problems using NAT or HA settings on VM ware, when trying to get my MWO server running.
CentOS only takes like maybe half an hour to reinstall, and you don't have to babysit it most of the time it's doing so:
So as I said again, I recommend reintalling CentOS, this time ensuring the networking is set properly.
On that note, I also recommend setting up a static IP address
(192.168.1.1 as DNS and gateway, 255.255.255.0 as Subnet mask, on most routers).

[striker1010]

Ok, but as I said for #3, it means you likely don't have the internet actually set up properly for it,
or you installed the O.S. without it set on bridged, which means CentOS is using the wrong drivers.

I've personally ran into many odd problems using NAT or HA settings on VM ware, when trying to get my MWO server running.
CentOS only takes like maybe half an hour to reinstall, and you don't have to babysit it most of the time it's doing so:
So as I said again, I recommend reintalling CentOS, this time ensuring the networking is set properly.
On that note, I also recommend setting up a static IP address
(192.168.1.1 as DNS and gateway, 255.255.255.0 as Subnet mask, on most routers).

Sorry I forgot to repost, I got the server to fully function.
What I did was reinstall CentOS using 2 adapters. One set to NAT and one set to Host-Only. This allows me internet access and allows the guest to speak to the host as well. Then I reinstalled and server and everything is good to go :)