cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jayapal Uradi <>
Subject Re: [DISCUSS] Why we MARK packets?
Date Thu, 19 Apr 2018 05:03:25 GMT

My comments inline.

On Apr 19, 2018, at 1:52 AM, Rohit Yadav <<>>

Nevermind, found the use of custom routing tables. In case someone want to refer, hints are

Jayapal and others - I've another one, is there a way to do routing without marking packets
at all, even in case of VRs with additional public interfaces?

AFAIK marking is the only way to do it.
Do you have any performance numbers with and without mark rules.

- Rohit


From: Rohit Yadav <<>>
Sent: Wednesday, April 18, 2018 10:39:02 PM
Subject: [DISCUSS] Why we MARK packets?


I could not find any history around 'why' we MARK or CONNMARK packets in mangle table in VRs?
I found an issue in case of VPCs where `MARK` iptable rules failed hair-pin nat (as described
in this PR:

The valid usage I found was wrt VPN_STATS, however, the usage is not exported at all, it is

Other than for debugging purposes in the VR, marking packets and connections I could not find
any valid use. Please do share if you're using marked packets (such as VPN ones etc) outside
of VR scope?

I propose we remove MARK on packets which is cpu intensive and slows the traffic (a bit),
instead CONNMARK can still be used to mark connections and debug VRs without actually changing
the packet marking permanently. Thoughts?

- Rohit

53 Chandos Place, Covent Garden, London  WC2N 4HSUK
53 Chandos Place, Covent Garden, London  WC2N 4HSUK

This e-mail may contain privileged and confidential information which is the property of Accelerite,
a Persistent Systems business. It is intended only for the use of the individual or entity
to which it is addressed. If you are not the intended recipient, you are not authorized to
read, retain, copy, print, distribute or use this message. If you have received this communication
in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent
Systems business does not accept any liability for virus infected mails.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message