ARP storm after bonding

IPv4/6, Port, VPN, proxy, SSH, remote access and more.
Post Reply
User avatar
colsanders83
Posts: 3
Joined: 08 Feb 2025, 05:29
United States of America

ARP storm after bonding

Post by colsanders83 »

Hi All,

I have an F2-423 with dual 2.5gb LAN ports. When connected to the network as individual ports there are no issues. When I bond them together I get an ARP storm of 131,000+ request every 10 minutes.
When bonded the TNAS auto changed the IP address from a 192 address to a 169 address with a subnet mask of 255.255.0.0. Even though the bonded IP address is in a completely different range, the original IP of the first port still gets me to the admin page. I can't log in (or even ping) the 169 address.

Do I need to manually change the IP and subnet to something within the 192 address range?
User avatar
Gremlin
Gold Member
Posts: 1627
Joined: 02 Dec 2022, 22:31
Great Britain

Re: ARP storm after bonding

Post by Gremlin »

Different story, similar ending. Welcome to the club:

viewtopic.php?t=7472
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
TMnick
TM Product Manager
Posts: 95
Joined: 03 Jul 2024, 15:56
China

Re: ARP storm after bonding

Post by TMnick »

colsanders83 wrote: 21 Feb 2025, 00:00 Hi All,

I have an F2-423 with dual 2.5gb LAN ports. When connected to the network as individual ports there are no issues. When I bond them together I get an ARP storm of 131,000+ request every 10 minutes.
When bonded the TNAS auto changed the IP address from a 192 address to a 169 address with a subnet mask of 255.255.0.0. Even though the bonded IP address is in a completely different range, the original IP of the first port still gets me to the admin page. I can't log in (or even ping) the 169 address.

Do I need to manually change the IP and subnet to something within the 192 address range?
Hello! Regarding the issue you are experiencing, you can try the following steps to resolve it:

1.Use TNAS PC to change the IP: Attempt to change the IP address to a range starting with 192 through TNAS PC.

2.Restart the device: If TNAS PC cannot change the IP, try restarting the NAS device. If the issue persists, it is recommended to restart the router.

3.Direct connection to the computer: Connect the NAS directly to the computer. TNAS PC will display an IP address starting with 169, which you can use to log in to the NAS.

If none of the above methods resolve the issue, please contact us promptly. If the issue has been resolved, please enter the system and send us the logs so we can further analyze the cause. Thank you.

Method to send logs: Go to the "Support & Help" module, generate a report on the "Issue Feedback" page, and send it to our technical support email.

Thank you again for your support and understanding!
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
User avatar
HarveyHobbs
Posts: 1
Joined: 03 Mar 2025, 13:28
United States of America

Re: ARP storm after bonding

Post by HarveyHobbs »

Thanks for the guide!
Harvey Hobbshappy wheels
Post Reply

Return to “Network”