Tag Archives: Network

Pikachu vulnerability is installed in the shooting range, and an error is reported when connecting to the MySQL database

During the installation of Pikachu vulnerability shooting range, the processing methods of connecting to MySQL database and reporting errors are as follows:

1. Confirm that the database can be connected normally. Try connecting with tools. If it is not normal, please check the configuration problems such as service, user name and password
2. Modify the IP address, user name and password of the database in config.inc.php to the IP, user name and password of the database. Both the root directory and pkxss have this file and need to be modified.

Config.inc.php in the root directory \ pkxss \ Inc also needs to be modified. It’s difficult.

[Solved] Git Clone Error: The TLS connection was non-properly terminated.

Operating system: Ubuntu 18.04

Test time: November 18, 2021

Problem Description:

Recently, the author encountered the following problems when downloading the repository on GitHub by using the GIT clone command, resulting in cloning failure

$ git clone https://github.com/pjreddie/darknet
Clone to 'darknet'...
fatal: unable to access 'https://github.com/pjreddie/darknet/': gnutls_handshake() failed: The TLS connection was non-properly terminated.

Solution:

Modify the HTTPS of the warehouse connection to git to clone

$ git clone https://github.com/pjreddie/darknet

NC -lk 7777 Error: nc: invalid option –k [How to Solve]

Recently, I am learning Flink to simulate real-time data through NC. However, when you enter NC -lk 7777 under windows, the following error is reported:

C:\Users\7371>nc -lk 7777
nc: invalid option -- k
nc -h for help

After some searching, it was finally solved
windows is different from Linux. You can enter NC - L - P 7777 directly after CMD

Error: write EPROTO 1593982200:error:100000f7:SSL routines:OPENSSL_internal

The probability is a nginx configuration problem. If the request is sent incorrectly, an SSL exception will be reported. The following is my configuration. The problem has been solved. If the certificate cannot be loaded, try to write the certificate path to the root directory.

 

 

ssl on;
        ssl_certificate         ssl/_.fetiononline.com.crt;
        ssl_certificate_key     ssl/_.fetiononline.com.key;
            
        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers HIGH:!aNULL:!MD5;
        ssl_prefer_server_ciphers on;

device no response, device descriptor read/64, error -71

Recently, I was porting rtl8723du to rk356x, and I encountered some problems in this process. Today, I recorded the problem as described in the title. This problem was recognized by the kernel when I plugged the WiFi module into the USB host, but the connection was unsuccessful. I checked a lot of data. It seems that I talked about the current signal. Now I record the problem I encountered, hoping to help more people
plug the module into the USB and use the dmesg command to view the cache information:

[  406.785107] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[  406.908835] usb 5-1: device descriptor read/64, error -71
[  407.142008] usb 5-1: device descriptor read/64, error -71
[  407.371775] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[  407.495321] usb 5-1: device descriptor read/64, error -71
[  407.725472] usb 5-1: device descriptor read/64, error -71
[  407.832210] usb usb5-port1: attempt power cycle
[  408.235232] usb 5-1: new high-speed USB device number 4 using xhci-hcd
[  408.235581] usb 5-1: Device not responding to setup address.
[  408.442000] usb 5-1: Device not responding to setup address.
[  408.648596] usb 5-1: device not accepting address 4, error -71
[  408.771923] usb 5-1: new high-speed USB device number 5 using xhci-hcd
[  408.772241] usb 5-1: Device not responding to setup address.
[  408.978858] usb 5-1: Device not responding to setup address.
[  409.185336] usb 5-1: device not accepting address 5, error -71
[  409.185559] usb usb5-port1: unable to enumerate USB device

First of all, I tried many online solutions. The general methods are:

echo Y > /sys/module/usbcore/parameters/old_scheme_first

perhaps

echo -1 > /sys/module/usbcore/parameters/autosuspend

I tried these methods, but they didn’t work in the end. But I directly inserted a hub on the board to transfer it out, and then inserted the module into the hub. At this time, the kernel can normally recognize the rtl8723du module
cache information displayed by dmesg after normal recognition:

[ 1862.348148] usb 5-1: new high-speed USB device number 11 using xhci-hcd
[ 1862.365237] usb 5-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 1862.365269] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1862.365281] usb 5-1: Product: USB 2.0 Hub
[ 1862.403229] hub 5-1:1.0: USB hub found
[ 1862.403327] hub 5-1:1.0: 4 ports detected
[ 1862.784974] usb 5-1.2: new high-speed USB device number 12 using xhci-hcd
[ 1862.803946] usb 5-1.2: New USB device found, idVendor=0bda, idProduct=d723, bcdDevice= 2.00
[ 1862.804023] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1862.804055] usb 5-1.2: Product: 802.11n WLAN Adapter
[ 1862.804084] usb 5-1.2: Manufacturer: Realtek
[ 1862.804109] usb 5-1.2: SerialNumber: 00e04c000001
[ 1862.888575] RTW:
[ 1862.888575] usb_endpoint_descriptor(0):
[ 1862.888660] RTW: bLength=7
[ 1862.888684] RTW: bDescriptorType=5
[ 1862.888705] RTW: bEndpointAddress=84
[ 1862.888725] RTW: wMaxPacketSize=512
[ 1862.888744] RTW: bInterval=0
[ 1862.888764] RTW: RT_usb_endpoint_is_bulk_in = 4
[ 1862.888784] RTW:
[ 1862.888784] usb_endpoint_descriptor(1):
[ 1862.888807] RTW: bLength=7
[ 1862.888825] RTW: bDescriptorType=5
[ 1862.888876] RTW: bEndpointAddress=5
[ 1862.888901] RTW: wMaxPacketSize=512
[ 1862.888935] RTW: bInterval=0
[ 1862.888975] RTW: RT_usb_endpoint_is_bulk_out = 5
[ 1862.889009] RTW:
[ 1862.889009] usb_endpoint_descriptor(2):
[ 1862.889046] RTW: bLength=7
[ 1862.889066] RTW: bDescriptorType=5
[ 1862.889085] RTW: bEndpointAddress=6
[ 1862.889104] RTW: wMaxPacketSize=512
[ 1862.889135] RTW: bInterval=0
[ 1862.889172] RTW: RT_usb_endpoint_is_bulk_out = 6
[ 1862.889205] RTW:
[ 1862.889205] usb_endpoint_descriptor(3):
[ 1862.889241] RTW: bLength=7
[ 1862.889278] RTW: bDescriptorType=5
[ 1862.889311] RTW: bEndpointAddress=87
[ 1862.889344] RTW: wMaxPacketSize=64
[ 1862.889364] RTW: bInterval=3
[ 1862.889383] RTW: RT_usb_endpoint_is_int_in = 7, Interval = 3
[ 1862.889419] RTW:
[ 1862.889419] usb_endpoint_descriptor(4):
[ 1862.889455] RTW: bLength=7
[ 1862.889491] RTW: bDescriptorType=5
[ 1862.889525] RTW: bEndpointAddress=8
[ 1862.889559] RTW: wMaxPacketSize=512
[ 1862.889591] RTW: bInterval=0
[ 1862.889625] RTW: RT_usb_endpoint_is_bulk_out = 8
[ 1862.889646] RTW:
[ 1862.889646] usb_endpoint_descriptor(5):
[ 1862.889670] RTW: bLength=7
[ 1862.889701] RTW: bDescriptorType=5
[ 1862.889737] RTW: bEndpointAddress=9
[ 1862.889772] RTW: wMaxPacketSize=512
[ 1862.889806] RTW: bInterval=0
[ 1862.889839] RTW: RT_usb_endpoint_is_bulk_out = 9
[ 1862.889873] RTW: nr_endpoint=6, in_num=2, out_num=4
[ 1862.889873]
[ 1862.889910] RTW: USB_SPEED_HIGH
[ 1862.889937] RTW: CHIP TYPE: RTL8723DU
[ 1862.890090] RTW: loadparam, Select P2P interface: iface_id:1
[ 1862.890593] RTW: Chip Version Info: CHIP_8723D_T4_1T1R_RomVer(0)
[ 1862.890640] RTW: USB NumInPipe(2), NumOutPipe(4/4)
[ 1862.890809] RTW: EEPROM type is E-FUSE
[ 1862.891165] RTW: Boot from EFUSE, Autoload OK !
[ 1862.891663] RTW: hal_EfuseSwitchToBank: Efuse switch bank to 0
[ 1862.981769] RTW: hal_ReadEFuse_WiFi: data end at address=0x86
[ 1862.982020] RTW: HW EFUSE
......

openwrt ipv6 nat6 ip6tables [How to Solve]

Install packages
opkg update
opkg install kmod-ipt-nat6
Run ip6tables -t nat -L
Error:  ip6tables v1.4.21: can’t initialize ip6tables table `nat’: Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.

Solutioin:
The original ipv6 nat6 requires a kernel version of 3.9.0 or higher and an iptables version of 1.4.8 or higher.
Upgrade the corresponding kernel and iptables packages to solve the problem.

[Solved] Use the truss console to connect to the public blockchain network error: mnemonic invalid or undefined

Error prompt

Error: Mnemonic invalid or undefined

Cause:. Env file naming error

Change the process.env file name directly to .Env and then execute the truss console --network Kovan command

Steps for connecting the common chain of truss
Install dotenv and truffle-hdwallet-provider

npm install dotenv --save-dev -g
npm install truffle-hdwallet-provider --save-dev -g

Note: The windows system may need to restart these two dependent packages to take effect in the project

Create an .env file in the project of root directory, write Mnemonic and INFURA_API_KEY via Form of key-value pairs in the .env file

INFURA_API_KEY= your infura_api_key
MNEMONIC="your mnemonic"

Configure in truffle-config.jsor or truffle.js file:

// Import the dotenv library created to read the settings in the `.env` file
require('dotenv').config();
// import the truffle-hdwallet-provider library to rebuild the wallet
const HDWalletProvider = require('truffle-hdwallet-provider');

module.exports = {
  networks: {
    development: {
     host: "127.0.0.1",     // Localhost (default: none)
     port: 7545,            // Standard Ethereum port (default: none)
     network_id: "*",       // Any network (default: none)
    },
    // Useful for deploying to a public network.
    // NB: It's important to wrap the provider as a function.
    kovan: {
      provider: () => new HDWalletProvider(
        process.env.MNEMONIC, 
        process.env.INFURA_API_KEY
      ),
      gas: 5000000,
      gasPrice: 25000000000,
      network_id: 42
    },
  },
  solc: {
    optimizer: {
      enabled: true,
      runs: 200
    }
  }
}

Enter truffle console --network kovan in the console to connect to the public chain, and you can enter web3.eth.getBlock('latest').then(console.log) for verification. If the following content is returned, the connection is successful:

{ author: '0x03801efb0efe2a25ede5dd3a003ae880c0292e4d',
  difficulty: '340282366920938463463374607431768211454',
  extraData:
   '0xde830206028f5061726974792d457468657265756d86312e33362e30826c69',
  gasLimit: '0x7a1200',
  gasUsed: '0x17d23',
  hash:
   '0xc7390c4f492c8c1da60608135fc9e05930123b645b39f221cba33d8b3c577b2a',
  logsBloom:
   '0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000080000000000000000000100000008000000000000000000080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400800000000000010000000000000080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009000000008000000',
  receiptsRoot:
   '0x3d05bb2ed4fcc90234eea6d840e7d0e3ce7f598a15e5314536b17bcd11c78b5b',
  sealFields:
   [ '0x84175e8801',
     '0xb84155a8cdb108dccec1d314124058fa6f22e7400ee200db0a94b7b165e4c3454c1818cc05f815cb7ce48f7a88b8401515740311a3566d9cf079428d506a6daca50101' ],
  sha3Uncles:
   '0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347',
  signature:
   '55a8cdb108dccec1d314124058fa6f22e7400ee200db0a94b7b165e4c3454c1818cc05f815cb7ce48f7a88b8401515740311a3566d9cf079428d506a6daca50101',
  size: 877,
  stateRoot:
   '0x03af5adce52a81ce5d332cddb9955e344214bff00859b78868116e1e839efdf7',
  step: '392071169',
  timestamp: 1568284676,
  totalDifficulty: '4524524338444961608702071789512829094373049115',
  transactions:
   [ '0xded7fed0842fd65ec808bc3652ec4175bc190acc11345c49c44b1fb5d954610f',
     '0x7e9112a46fa3c07aad813ea86355b15eebb44023c040d198ee7d15d379bbc2be' ],
  transactionsRoot:
   '0x0dd10d90686dda2684bd0ba70d1c9e1d9a5302c30ca75eb2c5b07a7b6e4498b9',
  uncles: [] }

Note: every time you want to call the contents of the. Env file, you must first import the dotenv Library in the JS file, otherwise you cannot read the contents of the file

[Solved] Zabbix Error: Cannot parse list of active checks

Question:

There is no data reported by the virtual machine, and an error is reported:

Cannot parse list of active checks

Solution:

1. Search the forum. The comment shows that there is a problem with the 10051 interface to the server. Check the firewall and no problem is found

2. The architecture adopts the mode of agent channel machine IP1 serverip2,

On the agent machine:

 tcping IP1 10051端口

The display is turned on. Continue troubleshooting

3. On the server machine, check the port status

tcping IP2 10051端口

It is found that the 10051 port is not open. Locate the problem, that is, the server problem. Restart the httpd service and solve it

systemctl restart httpd

[Solved] OpenSSL ssL_read: Connection was aborted,errno 10053

OpenSSL ssL_Read: connection was aborted, errno 10053 error

Original error message:
git: fatal: unable to access’ https://github.com/overwhatx/gittest.git/ :
OpenSSL ssL_read: Connection was aborted,errno 10053

terms of settlement

Reason: git limits the size of push by default. Run the command to change the limit size to increase the buffer

Solution:
git config -- global http.postbuffer 524288000

Change network authentication settings

Solution:
git config http.sslverify "false"

coredns [ERROR] plugin/errors: 2 read udp : i/o timeout

This problem seems to be caused by the failure to resolve DNS, but it is difficult to restart after checking various configurations. Finally, it is found that there is a problem with the forwarding rule configuration. Just execute the following:

iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -F

[Solved] Error(22) WARNING: IPv4 forwarding is disabled. Networking will not work.

Question

The following warning is given when docker runs the container ⚠️:

WARNING: IPv4 forwarding is disabled. Networking will not work.

Solution:

# modify configuration
echo "net.ipv4.ip_forward=1" >> /etc/sysctl.conf

# restart network
systemctl restart network

# Check
sysctl net.ipv4.ip_forward
# net.ipv4.ip_forward = 1

# restart docker
systemctl restart docker

Then restart the container ^_^