Note: Android service station problem Records and solutions

1, DNSMASQ Domain name hijacking failed:

　　Phenomenon:

The DNSMASQ command was actually executed after the WiFi hotspot was turned on, but the domain hijacking failed.

　　Reason:

WiFi Hotspot Open command executes the DNSMASQ command directly, when the hotspot opening process time is very short, the domain name hijacking can be successful, but the boot is slightly slower will be the system started by the DNSMASQ command to kill and overwrite, so it will result in invalid.

　　Solution:

Check that the WiFi hotspot has been turned on successfully before turning on DNSMASQ, and then kill the system-initiated DNSMASQ process, then execute the DNSMASQ command using the custom configuration file.

2, WiFi hotspot start frequent failure:

　　Phenomenon:

Turning on WiFi hotspot does not fail when mobile data is turned off.

When moving data is turned on, the behavior is as follows ':

When the WiFi hotspot is turned on, restarting the DNSMASQ service will cause the WiFi hotspot to fail, or even make an error, and it will fail to open in the system settings, and the device must be restarted to be available.

When you turn on the WiFi hotspot and do not do the DNSMASQ service, WiFi hotspot will not fail.

　　Reason:

The reason for failure is the iptables command, which is independent of the DNSMASQ command:

"Iptables-f && iptables-t nat-f && iptables-t mangle-f &&A" was used when the WiFi hotspot was turned on using iptables for port redirection. mp Iptables-x "command clears the iptable rule. So turning it on again can cause an open failure.

　　Solution:

After you turn off the WiFi hotspot, use "iptables-t nat-a prerouting-p tcp--dport 80-j REDIRECT--to-ports 80" To restore 80 ports to the 80 port to redirect to the other port;