No, this is a crappy setup with 2 standard internet connections, one 
fixed wireless and one cable (normal directly assigned layer 2 subnet) 
on interface 1 one on interface 2. Each gets a subnet of IP addresses.

These packets continue to loop - the behavior in question continues for 
as long as I leave the rules enabled and causes service impairment 
(probably due to upload saturation).

Thanks,

-Riley


On 12/7/2016 1:57 PM, Grand Avenue Broadband wrote:
> Is WAN2 the edge of "your" network, or do you have equipment beyond WAN2 that 
> might be participating in a common OSPF network with you?  I'm wondering if 
> that equipment, not having your preferential routing rules, may be deciding 
> that the most direct route to the target is *back* through the router in 
> question, which would explain why input suddenly rises to match output.  The 
> packets would loop only once, since your preferential routing rules don't 
> kick in on input from this interface.  You would also see a corresponding 
> rise in output traffic on the other interface.
>
>
>> On Dec 7, 2016, at 12:20 PM, Hexis via Mikrotik-users 
>> <[email protected]> wrote:
>>
>> If by related you mean bridged or set as master port, no, they are not.
>> ether2-switch2 is the master port of the "LAN" side and wan2 is on it's
>> own interface w/ no master port. The default route is shown below.
>>
>>
>> /ip route
>> comment=WAN2 distance=1 gateway=xxx.xxx.xx.x \
>>        routing-mark=to_WAN2
>>
>>
>> On 12/7/2016 11:24 AM, Ethan E. Dee wrote:
>>> Is the gateway reachable through the in interface of the mikrotik.
>>> Is the ether2 switch2 in any way related to wan2? Because it could be
>>> looping the traffic.
>>> Are your default routes in tact?
>>>
>>> On 12/07/2016 10:15 AM, Hexis via Mikrotik-users wrote:
>>>> I am doing some work on a small fixed wireless network, and they have 2
>>>> connections, neither of which are fiber. They are attempting to push
>>>> most of the streaming traffic out one provider while allowing everything
>>>> else to go through the other. I implemented routing marks based off of
>>>> an example in the Mikrotik wiki in order to accomplish that, marking
>>>> based on layer7 regex for example:
>>>>
>>>> Code: Select all
>>>> /ip firewall mangle print
>>>> add action=mark-routing chain=prerouting comment=Facebook disabled=no \
>>>>       in-interface=ether2-switch2 layer7-protocol=facebook
>>>> new-routing-mark=\
>>>>       to_WAN2 passthrough=no
>>>>
>>>>
>>>> I then have a route that matches the routing mark:
>>>>
>>>> Code: Select all
>>>> /ip route
>>>> comment=WAN2 distance=1 gateway=xxx.xxx.xx.x \
>>>>       routing-mark=to_WAN2
>>>>
>>>>
>>>> After activating these rules, things starting matching the regex Layer 7
>>>> rules fine, CPU load was stable, but I noticed that the traffic on WAN2
>>>> (where most of the marked connections were going) was showing perfectly
>>>> equal TX and RX traffic on the interface. This maxed out the upload on
>>>> the connection and caused massive packet loss. Anyone have any idea why
>>>> the traffic would have been looping like that?
>>>>
>>>> _______________________________________________
>>>> Mikrotik-users mailing list
>>>> [email protected]
>>>> http://lists.wispa.org/mailman/listinfo/mikrotik-users
>> _______________________________________________
>> Mikrotik-users mailing list
>> [email protected]
>> http://lists.wispa.org/mailman/listinfo/mikrotik-users

_______________________________________________
Mikrotik-users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/mikrotik-users

Reply via email to