I'm trying to do bandwidth test between my two WAN interfaces on one Mikrotik, which has static ips. Splitted two PCs based on mangle route marking for specific ports (80, 443 and 5001/UDP). One PC shows IP_WAN1, the other PC shows IP_WAN2 (tested in 2ip.ru). Here starts my problems.
I've started iperf client on PC1 (IP_WAN1) and iperf server on PC2 (IP_WAN2). Trying to connect PC1 to PC2 and nothing happens. I've troubleshooted this issue and found that PC1 trying to connect to IP_WAN2 over local input flow (by short-path), in this case i will test LAN throughput, but i need to test WAN throughput. How to forward over WAN not LAN?
Re: iperf between two wan... need help
If you force it to NAT between the two addresses would that not give you the same load as your "WAN" situation?
Re: iperf between two wan... need help
sorry, you mean hairpin, but this case isn't it, here is little picture
i need red flow, to test exchange between wan, NOT green to test switch capabilities
i need red flow, to test exchange between wan, NOT green to test switch capabilities
You do not have the required permissions to view the files attached to this post.
Re: iperf between two wan... need help
i've doubt is it possible at all? no matter what i've done result is the same Rx/Tx rate spin only on lan interface (it's hairpin)
Code: Select all
/ip fi ma
add action=mark-connection chain=input disabled=no in-interface=wan_if new-connection-mark=wan-con-mark passthrough=yes
add action=mark-routing chain=output connection-mark=wan-con-mark disabled=no new-routing-mark=route-wan passthrough=yes
add action=mark-connection chain=prerouting disabled=no dst-address-type=!local in-interface=lan_if new-connection-mark=wan-con-mark passthrough=yes
add action=mark-routing chain=prerouting connection-mark=wan-con-mark disabled=no in-interface=lan_if new-routing-mark=route-wan passthrough=yes
Re: iperf between two wan... need help
Ah, like that. Your picture is nice! 
Routerboards always add all their own interfaces to the routing table under 'routes'. This way traffic always takes the shortest route possible. In your rules you are thinking too complex.
If you change the routes so that it doesn't know a certain range can be reached over an other interface it should send it on to the default gateway of the first WAN interfaces (thus the internet) and then get the same traffic back on the second WAN interface. Effectivly passing it through the internet.
You can verify it using a traceroute!
Should be easy (if I understood you correctly).
Routerboards always add all their own interfaces to the routing table under 'routes'. This way traffic always takes the shortest route possible. In your rules you are thinking too complex.
If you change the routes so that it doesn't know a certain range can be reached over an other interface it should send it on to the default gateway of the first WAN interfaces (thus the internet) and then get the same traffic back on the second WAN interface. Effectivly passing it through the internet.
You can verify it using a traceroute!
Should be easy (if I understood you correctly).
Who is online
Users browsing this forum: No registered users and 11 guests