Cannot use eth0 as mgt interface without using a static route. #70
Replies: 1 comment 2 replies
-
Hi Brent, This issue is usually caused by the incorrect value being set in the configuration file for the interface to be used for management. Getting the routing right is quite tricky, but wiperf should take care of things for you if you set the interfaces correctly in the config file. Can you please check if your config file is set as follows and that you have no static routes set please:
If this fails to fix things, can you please send me a copy of your config.ini file and the output of the commands "ifconfig -a" and "ip route" while in the failed state and no static routes manually add please so that I can analyse what is going on ([email protected]) Also, are you using the most recent version of wiperf? Regards Nigel. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I would like to send my wiperf test results over an ethernet interface, but whenever wiperf runs it adds a metric 500 to my eth0 interface. This shuts down my SSH connection and makes it so it can't actually send the data over that interface to a splunk database. (basically makes it so i can't use the eth0 connection):
I fixed this problem by adding static routes, however when i connect the probe on a different subnet i will always have to change the static routes (obviously). My main question is: Is it possible to still have eth0 as a mgt interface (to send the tests to the splunk database) without having to use static routes? Basically in the end i want to be able to connect the probe and have it connect automatically to a subnet on eth0 instead of having to change the static route manually every different subnet.
Personally i love using Wiperf and want to thank you for all your work, any help would be greatly appreciated.
Regards
Brent
Beta Was this translation helpful? Give feedback.
All reactions