Ethereum AE

1.

Ha ha ha ha ha ha What is it, you don't know,... Airdrop is lying, boasting Not fatal,

2. At first, people were more interested in his design concept, but there was no shortage of fresh objects in the world. But once people were cut leeks, they would slowly think about this thing. He has been there for so many years, and it should graally return to zero, Even Ma Yun's technology application can't catch up, and it's still popular in the world. It's a joke. The state's attitude towards him is not to fight or support him.

3. I happened to see an activity in my circle of friends, BHT's new application for bitcoin. Now the market can continue to do activities, but I just want to continue to watch the market, have an in-depth understanding, and find something very interesting. The first time I saw BHT new, I was very confused about what it was. Internet search for BHT new didn't give much detailed explanation. Instead, it was stock new. I found that this BHT new came from stock new, which is not very different from stock new operation.

4. Currently, UOS is preferred. Because eth, EOS, AE have all gone up! UOS is the basic platform of blockchain which combines the advantages of eth + EOS.

5. STM32 Shenzhou IV is RMII, you can find his schematic diagram, network card chip is dm9161ae

6. You should know that tcpmp is used to view the packets on the network, or ask 802.1d config, which should be generated when the switch runs STP
in addition, it's better to add the parameter - n with tcpmp, otherwise domain name inversion will be carried out, which is very slow

7. If you add a route, as long as the data leading to the IP starting with 61 goes from eth0, the network card will be executed directly in DOS or written as text, and it will be executed directly in bat format, and the restart will be invalid

8. 1) It is not enough to replace hwaddr only, but also need to modify the / etc / udev / rules.d/70-persistent-net.rules file to exchange the MAC addresses of eth0 and eth1
for example:

# PCI device 0x14e4:0x1639 (bnx2)
subsystem = = & quot; net", ACTION==" add", DRIVERS=="?*& quot;, ATTR{address}==" d4:ae:52:64:09:2f", ATTR{dev_ id}==" 0x0", ATTR{type}==" 1", KERNEL==" eth*", NAME=" eth1"< br /># PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM==" net", ACTION==" add", DRIVERS=="?*& quot;, ATTR{address}==" d4:ae:52:64:09:2d", ATTR{dev_ id}==" 0x0", ATTR{type}==" 1", KERNEL==" eth*", NAME=" eth0"

2) there is a difference between the two in principle. 1) it just replaces the order of kernel when loading network card
update the driver, then the new mole will be used

3) which is better, I think if there is no difference in the performance of network card, it is the same. You can choose the way you are used to

9. Scheme 1:
1: first, modify the physical configuration file of network card. If there is no such file, create a new one or it from the existing environment and modify it as required
VI / etc / udev / rules. D / 70 persistent net. Rules
# PCI device 0x14e4:0x1692 (TG3)
subsystem = = & quot; net", ACTION==" add", DRIVERS=="?*& quot;, ATTR{address}==" bc:30:5b:b1:cd:be", ATTR{dev_ id}==" 0x0", ATTR{type}==" 1", KERNEL==" eth*", NAME=" eth0"

keyword explanation:
attr {address} = = & quot; bc:30:5b:9c:ae:79" ## Check the MAC address of physical network card ifconfig
kernel = = & quot; eth*" ## Original NIC name
name = & quot; eth0" ## The current network card name 1234567

needs to configure the MAC address of the network card in this file, the original network card name and the network card name to be changed
2, modify the network configuration file
VI / etc / network / interfaces
auto eth0
Iface eth0 INET static
address 172.16.19.xx
netmask 255.255.255.0

this should be configured as a new network card name after modification
auto eth0 # the corresponding network card name should be correct 1234567

3, Restart the server
there is a certain risk in restarting the physical server. The server has not been restarted, the personal test environment is relatively old, and there have been cases where the server could not be restarted, or the server lost connection e to network configuration error when it was restarted. It is suggested that the server should be close to itself when modifying the network card, and should not be modified remotely, Prevent server from losing connection
scheme 3:
in / etc / default / grub, grub_ CMDLINE_ Add the parameter net.ifnames = 0, biosdevname = 0 in Linux, as shown in the following figure:

then execute the command line, update grub, and finally modify the / etc / network / interfaces file,
change the network card name to eth0
restart the system, and the network card name is changed successfully. Of course, the server will lose connection
read the full text