My home network - virtual soft route sharing

First off, let me clarify that I’m not here to teach anyone anything; rather, I’m simply sharing my personal experience with setting up my home network. Feel free to join in and share your own insights on networking! To give you some context, I live in a three-story house where each floor covers approximately 100 square meters. Our internet service provider offers us a 100M broadband connection via fiber optics, which enters the house at the corner of the stairs between the first and second floors. Here's a basic layout of my home: [Insert Image] Over time, my home network setup has undergone several iterations. Initially, I placed the wireless router near the fiber optic entry point. However, due to the numerous corners within the house, the Wi-Fi signal was weak in the second bedroom and the corner of the living room. Later on, I purchased a VLAN switch and installed it near the fiber optic entry point. I positioned the wireless router in the living room and tried using a single-line VLAN for reusing the existing cables. Unfortunately, whether it was the quality of the switch (model BL-SG108M) or some other issue, the setup wasn’t very stable. There were instances when the switch would fail, causing the VLAN functionality to stop working. While Wi-Fi remained operational, other devices connected to the switch couldn’t be used. Currently, I’ve decided to make better use of my GEN8 server. Instead of just running it as part of a black group, I thought I’d experiment with soft routing. I started with LEDE, which proved quite powerful, especially with its extensive feature set. However, I encountered issues with QoS, particularly during heavy downloads, which resulted in packet loss and high latency. After some research, I discovered that while LEDE had decent flow control capabilities, they weren’t perfect. Eventually, I stumbled upon LoveFlow, which seemed much easier to configure and offered robust flow control options. This led me to adopt a dual-layer soft routing approach, with LEDE handling the primary tasks and LoveFlow managing the flow control. Here’s an overview of my current network topology: [Insert Image] I’ve connected one of the IOL4 ports on the IO8 to a wireless router, enabling me to manage and configure GEN8 via a laptop or other wireless devices when there’s no active internet connection. First, I enabled Hyper-V, as shown below: [Insert Image] Next, I created four new virtual switches: [Insert Images] The WAN port is connected to the modem, while the LAN port connects to the switch. For LEDE’s network configuration, here’s how it’s set up: [Insert Images] LoveFlow, on the other hand, uses two virtual WAN ports. The LEDE WAN port connects directly to the optical modem, while the LoveFlow LAN port connects to the switch, Synology NAS, and host machine. With this arrangement, the network is largely functional. Now comes the flow control aspect. I wanted to implement flow control and SS redirection since we have a separate line for our tenant. I didn’t want their traffic going through SS. By connecting LEDE and LoveFlow separately, LEDE couldn’t differentiate between which traffic should go through SS and which shouldn’t. To address this, I allocated equal bandwidth—250 Mbps upstream and 6250 Mbps downstream—to both ports. Then, I configured IP splitting rules: [Insert Image] Tenant traffic flows through WAN2, while I handle the load balancing between WAN1 and WAN2. Additionally, I set up access controls in LEDE’s SS, assigning fixed IPs: 192.168.3.2 for WAN1 and 192.168.3.3 for WAN2. Traffic from 192.168.3.2 goes through SS, while 192.168.3.3 bypasses SS. Finally, I enabled LoveFlow’s flow control and added two additional lines. This completes the basic network setup. Other configurations involve port mapping and wireless coverage. Currently, I’ve placed a wireless router on the second floor in the living room, operating in AP mode, ensuring Wi-Fi availability throughout the house. That’s it for my network sharing! Any feedback or questions are more than welcome. [Insert Image] As for the latency, here’s a snapshot: [Insert Image] I also experimented with running a virtual machine to optimize performance further: [Insert Image] Thanks for reading, and feel free to share your thoughts or ask any questions!

Electric Motorcycle Charger

electric motorcycle charger

Electric Motorcycle Charger,Li-Ion Battery Charger For Motor,Motorcycle Li-Ion Battery Charger,Motorcycle Fast Battery Charger

HuiZhou Superpower Technology Co.,Ltd. , https://www.spchargers.com

Posted on