2q

[helloldt]

Hello,

1. Is it possible to monitor the configuration file? When the configuration file is modified, it can adapt to the changes immediately without restarting the program.
2. 2. Is it possible to support shadowsocks?

[helloldt]

Subject: Feature Request: Smart Hot-Reloading for Configuration

Hi,

I have implemented a "Smart Hot-Reloading" feature for the configuration file to improve usability, especially when frequently changing proxy settings.

Implementation Details:

1. Config Watcher:
   Added a background goroutine in main.go that monitors config.json for modifications every 3 seconds.

2. Thread-Safe Dialer:
   Modified proxy/proxy.go to use a sync.RWMutex for the global _defaultDialer. This ensures thread safety when hot-swapping the dialer at runtime.

3. Smart Reload Logic:
   When a config change is detected, the system compares the new config with the current one:

   • Proxy-Only Changes (e.g., SOCKS5 credentials, routing rules): The system performs a "Hot Swap" by updating the _defaultDialer in memory. This is seamless and does not restart the PCAP sniffer or the network stack, ensuring zero downtime for packet capture.
   • Network/PCAP Changes (e.g., IP, MTU): A full restart of the stack and PCAP handle is triggered to ensure the new network parameters are applied correctly.

This feature allows users to update proxy servers or routing rules on the fly without interrupting the underlying packet capture service.

Hope you find this useful!

useful!