What's the difference between network adapters in VMware?

[Kaizoku ChaosStar]

When I take a look in the DC-PC server tutorial it says I'm supposed to use "bridged" connection as the network adapter in Ubuntu, in VMware. Unfortunately I gotta plug my laptop into my modem, physically, if I wanna have an Internet connection in Ubuntu with this option, or else it won't work.

I've tried mixing about with the network adapter types. When I use "NAT" (host's IP address) the Internet connection is easily established wirelessly. I got no problems whatsoever using a wireless connection to my router with this option, in VMware, for Ubuntu.

So here's the question:
Is there anything stopping me from using "NAT" over "bridged"?
If there is, can somebody please take a bit out of their time to explain this.
I would guess there are more people wondering as well.

[brourke228]

NAT connection creates a separate subnetwork in which the clients all share one ip address, much like how a router works with its connection to your ISP. Whereas a bridged connection assigns vmware an ip address on the same subnet as your primary router. (ie if your primary router has the ip address of 192.168.1.1, then vmware could have hte ip address of say 192.168.1.101, and the computer running vmware would have yet another ip address of maybe 192.168.1.100 or something like that).

I had tried to get pc-dc setup through vmware using an NAT connection originally, but I kept running into issues where Dreamcast was not getting any internet access. You can try using NAT connection if you like, but I can't guarantee that it will work. I will say that you will definately need to modify your options.(INTERFACE) file in /etc/ppp so that the local and remote ip addresses are on a different subnet than your primary router. For example if your primary router uses 192.168.1.x subnet, you will want to assign something like 192.168.2.x to vmware and Dreamcast for the dial-in connection.
So if your primary router used 192.168.1.x subnet, your options.(INTERFACE) file might look something like this:

Code: Select all

192.168.2.150:192.168.2.151
netmask 255.255.255.0

If that doesn't work, try changing the netmask to 255.255.255.255 . If you still have issues after that, then I can't really help you since I haven't gotten this to work with NAT connection myself.

[Kaizoku ChaosStar]

Thanks for the info. I think this is gonna help me out a lot if i choose to go on with NAT.

I do have an alternative to this.
If I can get my network card to show up on "additional drivers" in Ubuntu I can use the bridged connection and possibly connect, wirelessly, to my primary router for internet access.
The only problem is... no drivers show up under that "additional drivers" section, of course. If you know how to make your PC's network card work to create a wireless connection in bridged I think that would solve all my troubles with every issue I have with this PC-DC server setup.

Right now it only lets me use the standard "wired" option, which of course doesn't work unless I place my laptop in a different room and hook it up to my modem/router providing me internet. This is out of the question since my DC and TV is stationed and mounted in a room apart from my modem/router.

[Kaizoku ChaosStar]

Never mind this topic from here on. I finally got it to work right, even in bridged.
There was something totally wrong in my winsock registry for networking, alltogether.

Feel free to close down this whole topic.