[mpls-linux-general] [again] right behaviour?

[Antonio M. <ant...@mu...>]

Hello,
I am resending this message since I had problem with my email server
I have lost all the email and may be any answer to this.
So please excuse me!
Thank you.

==================================================
Hello,
on my test network I noticed a strange bahaviour
regarding MPLS traffic.

Here my problem:

Host A: 192.168.10.10   ------------>    Host B: 192.168.10.20


On host A:
- mplsadm2 -A -O 0
  Key: 0x00000385
  Out Segment add: Success

- mplsadm2 -O 0x385 -o push:gen:170:set:tap0:ipv4:192.168.10.20
  Out Instr: Success

- more /proc/net/mpls_out
  0x00000385 0/0/0 1 PUSH(gen 170) SET(tap0,192.168.10.20)

Now if I do, from A: ping 192.168.10.20 on B I receive normal ethernet packet
and that's fine.

- iptables -t mangle -A OUTPUT -d 192.168.10.20 -j MPLS --set-key 0x385

Now, as expected, on B I receive MPLS packet marked with 170 as label.
- more /proc/net/mpls_out
  0x00000385 70/5880/0 2 PUSH(gen 170) SET(tap0,192.168.10.20)

Now If I remove the iptables entry in this way:
- iptables -t mangle -D OUTPUT -d 192.168.10.20 -j MPLS --set-key 0x385

on host B I still receive MPLS packet marked with 170 as label
and

- more /proc/net/mpls_out
  0x00000385 183/15372/0 2 PUSH(gen 170) SET(tap0,192.168.10.20)

the counter continue to go up.


So, do you think this is a right behaviour?
If yes, how can I stop host A to sending MPLS packets without removing the
mpls key in /proc/net/mpls_out, but just acting on iptables?

Thnx,
Antonio Mancuso
==================================================