Wen: Wei Dongshan
We deeply windows, troubled mutual PING problem between ubuntu, development board,
in particular recorded a video for this problem ( https://v.qq.com/x/page/h0505eg7z0m.html)
but unfortunately there are still many, many students do not watch video directly to ask questions, or watched the video can not solve the problem, so I will try to solve this problem with a few pages of the document.
This is a ping-date documentation problem solving, a problem first look here, I hope this is the last document.
The different cable connections can be divided into three cases:
a, Windows through WIFI, from the wireless router boards close to
two, Windows through WIFI, boards far from the wireless router
three, Windows WIFI card is not used
In each case can be divided into cable connection, VMWare in selected card, set the IP and verification of four parts, here we were to explain, please choose according to their specific circumstances.
A. Windows via WIFI, development boards from the wireless router close
1.1 cable connector
Following the wiring diagram (development board cable, must receive a router, not to the computer):
If you just want to let Windows and Ubuntu interoperability, development can not take the cable board.
1.2 VMWare WIFI card in selection
If you just want to let Windows interoperability and development board, you can not start VMWare, of course, also do not have to set up VMWare and Ubuntu.
How many PC card, such as WIFI card, a wired LAN.
In this connection, VMWare bridge mode must be selected, WIFI card must be selected.
As shown operation (VMware different version, the menu may differ, please look for yourself; the new version of vmware player no menu item to select the card, install the corresponding pro version):
1.3 IP Settings
Windows of WIFI card IP, IP ubuntu's IP, development boards, three IP must be in the same network segment (what is the same network segment? Is in front of the IP are the same, they finally face three different).
. a Windows automatically assigned an IP are generally in the command line: ipconfig, to determine its IP,
assumed to 192.168.1.10
. Ubuntu B need to manually set an IP, the terminal performs the Ubuntu: ifconfig, determining the name of the card,
probably eth0, eth4, ens33, the assumption is ens33
then execute:
sudo ifconfig ens33 192.168.1.100 // 配置网卡IP为192.168.1.100
c. the development board running UBOOT, when running LINUX,
their IP need to be set, these two stages no IP connection,
these two phases will not run at the same time, so they can be the same IP.
If the boards are running UBOOT, execute the following command to set the IP:
set ipaddr 192.168.1.123
save
If the development board running LINUX, execute the following command to set the IP:
echo “ifconfig eth0 192.168.1.123” >> /etc/init.d/rcS
reboot
1.4 verification
① validate Windows and Ubuntu exchange:
in the Windows command line:
ping 192.168.1.100
// ping Ubuntu, it says that if there is data returned through the following chart:
Note: Windows ping Ubuntu nowhere can execute the following command to turn off the firewall in Ubuntu try (the same below, will not be repeated):
sudo ufw disable
// then enter the password 123456
If the ping fails you can try to turn off Windows Firewall (please Baidu method, the same below, will not be repeated)
② validate Windows and "Running uboot development board" interoperability (step ②③, as long as you can do a):
Note: Data UBOOT not respond to PING, PING nowhere so you are UBOOT, and
can only go to PING another computer in UBOOT .
If the "alive", says through.
Sometimes the Windows firewall lead nowhere PING, PING ubuntu can try to go the IP.
③ validate Windows and "Running Linux development board" interoperability (the first ②, ③ step, as long as you can do a):
similar to the first step ①, the Windows command line IP PING development board.
Note that you must start the development board into Linux, it can be through Windows PING.
Two. Windows through WIFI, the development board is far away from the wireless router
2.1 Connecting cable
2.1.1 Windows PC and development board cable, have received another hub or router
It is strongly recommended to buy a network hub, very cheap, 20 dollars it; soil trench can buy a router instead of a hub.
Following the wiring diagram (development board and a computer network cable to the network hub, development boards and computers not directly connected with the network cable):
If you just want to let Windows and Ubuntu interoperability, see the previous chapter (Chapter 1): Not required development board connection cable, do not need to buy a hub.
2.1.2 Development board computer and directly connected (not recommended) with a network cable
I do not want to buy a network hub (strongly recommended not to do so, otherwise the process of trouble from time to time occur):
If you just want to let Windows and Ubuntu interoperability, see the previous chapter (Chapter 1): development board does not need to access the network cable no need to buy a hub.
Cable PC and development board directly connected,
This is the case for a special treat!
If the computer is directly connected with the development board and cable, program development board, the card must be enabled!
Otherwise, Windows saw the wired network card will have a red cross.
Red cross indicates the "off"
They are "off" you do not ask me why PING nowhere.
So,
if the computer and development board with network cable direct connection, the development of the program board must be enabled NIC:
A If you want to play UBOOT development board:
Native UBOOT is a wonderful work,
it usually does not enable the card,
only in use that small network command will only enable the network card.
Therefore, you must replace the "full UBOOT can make the card",
JZ2440 of uboot we offer, has enabled the entire card, and
you can see it in the first two rows of information in print: enable Ethernet alltime
. b LINUX If you want to play in the development board,
the LINUX drive must have a network card, you must configure the network card,
you can execute a command like this in the development board in:
ifconfig eth0 192.168.1.123
2.2 VMWare in select Wired LAN
If you just want to let Windows interoperability and development board, you can not start VMWare, of course, also do not have to set up VMWare and Ubuntu.
How many PC card, such as WIFI card, a wired LAN.
In this connection, VMWare bridge mode must be selected, wired LAN must be selected.
As shown operation (VMware different version, the menu may differ, please look for yourself; the new version of vmware player no menu item to select the card, install the corresponding pro version):
2.3 IP Settings
Note Note Note: WIFI network card in Windows, wired network cards, they are two IP network segment must not be the same!
IP WIFI card is usually automatically assigned, are generally 192.168.1.xxx ,
then we put the wired network card IP is set 192.168.2.XXX , can not WIFI card with the same network segment.
Windows of wired network card IP, IP ubuntu's IP, development boards, three IP must be in the same network segment.
a. Windows wired LAN IP how to manually set your own Baidu, assumed to 192.168.2.10
. b Ubuntu need to manually set an IP, the Ubuntu performed in the terminal: the ifconfig, determining the name of the card,
may be eth0, eth4, ens33, ens33 assumption is
then performed:
sudo ifconfig ens33 192.168.2.100
// configure the LAN IP to 192.168.2.100
c. the development board running UBOOT, when running LINUX,
their IP need to be set, these two stages no IP connection,
these two phases will not run at the same time, so they can be the same IP.
If the boards are running UBOOT, execute the following command to set the IP:
set ipaddr 192.168.2.123
save
If the development board running LINUX, execute the following command to set the IP:
echo “ifconfig eth0 192.168.2.123” >> /etc/init.d/rcS
reboot
2.4 verification
① validate Windows and Ubuntu exchange:
in the Windows command line:
ping 192.168.2.100
// ping Ubuntu, if there is data to return, says through, as shown below:
② validate Windows and "Running uboot development board" interoperability (step ②③, as long as you can do a):
Note: UBOOT not respond to PING data, so you are nowhere PING UBOOT, the
only UBOOT to PING another computer.
③ validate Windows and "Running Linux development board" interoperability (step ②③, as long as you can do a):
similar to the first step ①, the Windows command line IP PING development board.
Note that you must start the development board into Linux, it can be through Windows PING.
Three. Windows does not use WIFI card
3.1 Connecting cable
3.1.1 Windows Internet via a wired LAN access router, router boards from close
If you just want to let Windows and Ubuntu interoperability: development board does not need to access the network cable.
3.1.2 Windows Internet router via a wired LAN connection, the development board is very far away from the router
It is strongly recommended to buy a network hub, very cheap, 20 dollars it; soil trench can buy a router instead of a hub.
If you just want to let Windows and Ubuntu interoperability, see Section 3.1.1: development board does not need to access the network cable, need to buy a hub, but the computer network cable must be connected to the router (LAN so it is not disconnected state, before use) .
3.1.3 is not the Internet, Windows PC and development board cable, hub or router are connected
Development board and a computer, using a network cable connection through a hub or router interconnect:
If you just want to let Windows and Ubuntu interoperability: development board does not need to access the network cable, but the computer network cable must be connected to your router or hub (such card was not turned off state, before use).
3.1.4 Development board computer and a network cable is directly connected (not recommended)
I do not want to buy a network hub (strongly recommended not to do so, otherwise the process of trouble from time to time occur):
If you just want to let Windows and Ubuntu interoperability, but there is no hub or router: still need to use a cable to connect the computer and Development Board ( this card was not disconnected state, before use).
When computer network cable and direct development board,
which is the case for a special treat!
If the computer is directly connected with the development board and cable, program development board, the card must be enabled!
Otherwise, Windows saw the wired network card will have a red cross.
Red cross indicates "off",
they are "off" you do not ask me why PING nowhere.
So,
if the computer and development board with network cable direct connection, the development of the program board must be enabled NIC:
A If you want to play UBOOT development board:
Native UBOOT is a wonderful work,
it usually does not enable the card,
only in use that small network command will only enable the network card.
Therefore, you must replace the "full UBOOT can make the card",
JZ2440 of uboot we offer, has enabled the entire card, and
you can see it in the first two rows of information in print: enable Ethernet alltime
. b LINUX If you want to play in the development board,
the LINUX drive must have a network card, you must configure the network card,
you can execute a command like this in the development board in:
ifconfig eth0 192.168.1.123
3.2 VMWare in select Wired LAN
If you just want to let Windows interoperability and development board, you can not start VMWare, of course, also do not have to set up VMWare and Ubuntu.
How many PC card, such as WIFI card, a wired LAN.
In this connection, VMWare bridge mode must be selected, wired LAN must be selected.
As shown operation (VMware different version, the menu may differ, please look for yourself; the new version of vmware player no menu item to select the card, install the corresponding pro version):
3.3 IP Settings
Windows of wired network card IP, IP ubuntu's IP, development boards, three IP must be in the same network segment.
. a set of Windows wired LAN IP:
If the wired network card to the router, then it will automatically assign IP in general,
can be executed ipconfig look under Windows command line, assumed to 192.168.1.10;
If the IP does not automatically assign the wired LAN, you can be manually set, Baidu method of your own.
Also assumed to 192.168.1.10
. b Ubuntu need to manually set an IP, the terminal performs the Ubuntu: ifconfig, determining the name of the card,
may be eth0, eth4, ens33, assumption is ens33
then execute: sudo ifconfig ens33 192.168.1.100 // IP network adapter configured to 192.168.1.100
c. the development board running UBOOT, when running LINUX,
their IP need to be set, these two stages no IP connection,
these two phases will not run at the same time, so they can be the same IP.
If the boards are running UBOOT, execute the following command to set the IP:
set ipaddr 192.168.1.123
save
If the development board running LINUX, execute the following command to set the IP:
echo “ifconfig eth0 192.168.1.123” >> /etc/init.d/rcS
reboot
3.4 verification
① validate Windows and Ubuntu exchange:
in the Windows command line:
ping 192.168.1.100
// ping Ubuntu, if there is data to return, says through, as shown below:
② validate Windows and "Run uboot development board" interoperability (the first ②, ③ step, as long as you can do a):
Note: UBOOT not respond to PING data so you are nowhere PING UBOOT, the
only UBOOT to PING another computer.
If the "alive", says through.
Sometimes the Windows firewall lead nowhere PING, you can try to PING ubuntu.
③ validate Windows and "Running Linux development board" interoperability (step ②③, as long as you can do a):
similar to the first step ①, the Windows command line IP PING development board.
Note that you must start the development board into Linux, it can be through Windows PING.
Summary: the situation so much, I do not know you have not read the halo, or unclear words or watch a video of it. We did our best.
-END-
No. baiwenkeji public attention the first time to obtain the embedded dry.
Technical exchanges plus personal prestige 13,266,630,429, verify: CSDN blog
