Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am having three virtual machines with different linux distros installed on it(oracle virtualbox).I just wanted to know if there is any way to connect these three machins in LAN.if so how to do it in vmware and virtualbox?
In Vmware you have the option to create another network for your viritual machine (seperate from your local network). This is called Network Address Translation, in short NAT. What it does in simple terms is that it directs traffic from the internet to the correct pc in the local network. Your computer then becomes the router for your viritual machines. It also can act as a DCHP server that gives out IP addresses to your VMs only.
Here is an example:
As you can see here your viritual machines (VM) get internet access from your computer. Your computer acts similary to your normal router. Keep in mind if you want to connect from one of the computers on the local network, you have to do some port forwarding on your computer.
To do this look under network adapter settings in Vmware.
Hope this helped
-Kad
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
In a working VoIP setup i want to replace the PC(Isabella) with new virtual machine(Isabella ready) on a new server(connected to new switch) using esxi 7
PC is connected to a router right now.
There is a few vm on the server and i think it is better to have a separate network on esxi for voip.
My difficulty is how to connect router to server and network setup.
Shall I connect router to server directly or to the physical switch?
I have to define a new vswitch for this?
How should be the esxi network config?
Any help and guide or address appreciated
Thanks
I'll give you a hint in this question.
You need to understand the basics about physical world and virtual world.
You have to connect router > switch > server (esxi). It's recommend that use two physical nic on ESXI servers. For performance and security use VLANs for different traffic, you should configure this options on router and switch (l2 administrable switch). Check if your hardware has this options.
At virtual world, you'll have vswitch0 that map your physical nic. Inside this switch you would create your network stack. You don't need to create separate switch for every nic, also It's not recommend, use at least two nic for each vswitch.
VMkernels will handle esxi management like DCUI, vmotion, vsan, iscsi, HA and FT. Port Groups will handle VLAN Traffic for your VMs. So, at this point you should create a separate VLAN for your VOIP VM.
Please check VMware documentation for more details. Hope this comment help you understand basics.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I am working on a small embedded device based upon an STM32F4xx MCU. It implements a TCP/IP server over a Wi-Fi connection. The question I have relates to exposing the IP address of the device so that it may be discovered by computers on the same network. UPnP and SSDP seem to be rather "heavy" solutions to this problem.
Are there other techniques/protocols that have a smaller footprint than UPnP and SSDP?
Thanks in advance for your input,
Sid
If you can make up any custom protocol, a simple UDP beacon periodically sent to the broadcast address (255.255.255.255 or your preferred interface's broadcast address) is simple and reliable.
Synopsis of comments:
For listing in mainstream platforms' (Windows, Linux, OS X) network views, the best option would likely be to implement the full stack required for Windows' Network Discovery.
If hostname lookup is enough, Netbios or mDNS could be enough.
The search term you are likely looking for is zero-configuration networking and should give you all the available options
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Is there a method to determine whether a host (on your LAN) is on WiFi vs Ethernet using nmap or any other tool? I am OK with fuzzy guesses as well.
tl;dr No, there is none
Long answer:
There is no way to find out what kind of connection other PC on your network is using(without physically accessing it ofc).
Those things are abstracted on network. You can sniff traffic on transport layer by Wireshark and see there is no data on interfaces being transported.
An option:
You can learn a physical network interface vendor by sniffing traffic.
Wireshark can guess those, because vendors have their own MAC address prefixes. And if it's some company which is making wireless interfaces only, you can hit a jackpot. It's not even close to being a bulletproof method though.
Nmap may be used to look for open ports. There might be a chance that you can deduce which software server is running by getting info on ports, but I can hardly imagine you will find anything wlan/eth specific.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I have a HP ProCurve switch, I recently added 2 new machines to the network, which I had to assign the IP addresses to manually. Now using these 2 machines I can ping my current machine and other machines on the network, however if I try to ping those 2 machines from my current machine (or others on the network) it does not go through. So my thoughts are that the router table has not updated so that's why I can't ping them from machines that have been on this router.
(Not too sure, not enough knowledge yet)
At least I think so. My question is does the Router Table update it's information automatically?
Assuming your HP Procurve is acting only as a switch, then the Routing Table should not be your problem. A switch does not route IPs, a switch is concerned with routing packets via their layer-2 addresses (MAC addresses). The switch determined which physical port is connected to a device with a MAC address, and when it gets a packet addressed to that MAC address, it sends the packet out that port. The mapping on port to destination mac address is stored in a CAM table inside the switch. This is very different from a routing table that maps IP address ranges to physical interfaces.
What is probably happening is that ARP is not resolving. ARP binds layer 3 IPs to layer 2 MACs in a local network. This can be cause for a few reasons. The first thing i would look into is if the switch has VLANs enabled. This makes the switch act like multiple isolated switches. After that you may need to look at your computers ARP tables to make sure they are correct. The arping command will be useful.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm using KVM to run a Windows virtual machine on my Linux box. Networking is accomplished through a tap device, hooked into a bridged Ethernet device, which allows the Windows VM to basically appear like a separate physical computer on my network. This is pretty nice.
However, my understanding is that most, if not all, wireless drivers can't support bridging. I'd really like to be able to roam a little more freely while I'm working -- does anyone know of an effective workaround?
User-mode networking won't work, as I have to use some Windows VPN software that wants lower-level networking access.
I assume that you could configure your Windows guest to use the host as its default gateway, and set up NAT via the wireless interface on the host. So the signal flow would look like this:
Windows software opens connections to a host on the internets.
Windows routes the packet via the default gateway, i.e. the host Linux system.
Linux does NAT magic and routes the packet via its normal routing table (which should use a default gateway via the wireless interface).
I have never tried this in combination with bridging though.
Other, related questions like this one seem to indicate it is simply a limitation of many wireless drivers. There are a few for Linux that will do bridging, but one would have to plan to build that into their system from day one.
Why it should be a problem to setup host linux system to use WLAN and then us this connection as default gateway for local/internal bridge and all VMs are pluged into it? Ok, simple NAT has to be configured but what ist actually the point?