Community discussions

MikroTik App
 
rmichael
Forum Veteran
Forum Veteran
Topic Author
Posts: 718
Joined: Sun Mar 08, 2009 11:00 pm

connection mark on the bridge

Tue Dec 22, 2009 11:45 pm

On this page http://wiki.mikrotik.com/wiki/Connection_Rate author writes:
Each entry in connection tracking table represents bidirectional communication. Every time packet gets associated to particular entry, packet size value (including IP header) is added to "connection-bytes" value for this entry. (in another words "connection-bytes" includes both - upload and download)
When I look at connections tab it lists up down links separately, ie:

src dst
1.1.1.1:80 2.2.2.2:1234
2.2.2.2:1234 1.1.1.1:80

Is mentioned wiki page incorrect or connection tracking behavior is different when bridging (ROS4.2)?
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: connection mark on the bridge

Wed Dec 23, 2009 1:18 am

When I look at connections tab it lists up down links separately, ie:

src dst
1.1.1.1:80 2.2.2.2:1234
2.2.2.2:1234 1.1.1.1:80

Is mentioned wiki page incorrect or connection tracking behavior is different when bridging (ROS4.2)?
well, while routing, I cannot see double records... maybe bridging, maybe timeout - what's in TCP State and Timeout values of these entries?
 
rmichael
Forum Veteran
Forum Veteran
Topic Author
Posts: 718
Joined: Sun Mar 08, 2009 11:00 pm

Re: connection mark on the bridge

Wed Dec 23, 2009 3:05 am

hm..I cannot find any entries that have the same ports today. What I still see is my LAN as a source and destination even though we are behind nat (so LAN is always the source address) like so:

(my lan 1.1.1.0/24)
src dst
1.1.1.2:xxx 24.7.7.7:xxx
1.1.1.6:xxx 63.4.4.4:xx
197.4.4.4:xxx 1.1.1.45:xxx

This causes problems for my mangle rules as I cannot filter traffic by src as it can be listed in dst as well... any idea why this is happening?

edit: my configuration: [LAN]----[MT transparent bridge]-----[router w/NAT]-----[internet]
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: connection mark on the bridge

Wed Dec 23, 2009 2:01 pm

This causes problems for my mangle rules as I cannot filter traffic by src as it can be listed in dst as well...
anyway you will have your lan addresses either as src or as dst - packets go in both directions
 
rmichael
Forum Veteran
Forum Veteran
Topic Author
Posts: 718
Joined: Sun Mar 08, 2009 11:00 pm

Re: connection mark on the bridge

Wed Dec 23, 2009 8:35 pm

This causes problems for my mangle rules as I cannot filter traffic by src as it can be listed in dst as well...
anyway you will have your lan addresses either as src or as dst - packets go in both directions
What is the definition of src address on MT? Isn't it the side that started with TCP (SYN) packet? By that definition, since LAN is always initiating traffic it should always be the src.

thanks,
Michael
 
fewi
Forum Guru
Forum Guru
Posts: 7717
Joined: Tue Aug 11, 2009 3:19 am

Re: connection mark on the bridge

Wed Dec 23, 2009 8:48 pm

The source address is the IP address of the device that sent the particular packet you're looking at. In a unicast TCP virtual circuit that could be either of the two hosts involved, the destination address will be the other host.

It works like with all other devices, basically.

Who is online

Users browsing this forum: Amazon [Bot] and 133 guests