two relay on same host via docker... packets are forwarded wrong

[IMMO WETZEL]

Hi I do need to run a router with to dhcprelays. Therefore I separated them via docker.
One container for B->A
And one for A->C

           +-----------------------+
           |                       |
           |                       |
A   +------+                       +--------+  B
           |                       |
           |                       |
           +----------+------------+
                      |
                     +
                      C

Theoretically that should work cos the relay transforms the broadcasts into a unicast frame which is targeted towards the target IP host. Any answer will transcoded into broadcast and forwarded into the correct network... Theoretically.
But I do see the Discover from B not only forwarded to A
Also the dhcprelay listen (-id) on A sees the discover and send it out to C

How can I fix this ?

A= br_TB102_TMN (ens20.1002), B= br_TB102_DPU(ens19.2002) ,  C= ens18

Requesting: br_TB102_TMN as upstream: Y downstream: N
Requesting: br_TB102_DPU as upstream: N downstream: Y
Internet Systems Consortium DHCP Relay Agent 4.3.6
Copyright 2004-2017 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/br_TB102_DPU/42:b9:9b:1e:1c:c9
Sending on   LPF/br_TB102_DPU/42:b9:9b:1e:1c:c9
Listening on LPF/br_TB102_TMN/7a:59:88:45:a6:23
Sending on   LPF/br_TB102_TMN/7a:59:88:45:a6:23
Sending on   Socket/fallback
Forwarded BOOTREQUEST for 00:19:92:c6:9d:b6 to 10.160.50.18
Forwarded BOOTREQUEST for 00:19:92:c6:9d:b6 to 10.160.50.18
Forwarded BOOTREQUEST for 00:19:92:c6:9d:b6 to 10.160.50.18


Requesting: ens18 as upstream: Y downstream: N
Requesting: br_TB102_TMN as upstream: N downstream: Y
Internet Systems Consortium DHCP Relay Agent 4.3.6
Copyright 2004-2017 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/br_TB102_TMN/7a:59:88:45:a6:23
Sending on   LPF/br_TB102_TMN/7a:59:88:45:a6:23
Listening on LPF/ens18/36:78:14:96:53:13
Sending on   LPF/ens18/36:78:14:96:53:13
Sending on   Socket/fallback
Forwarded BOOTREQUEST for 00:19:92:c6:9d:b6 to 10.160.5.2
Dropping request received on ens18
Forwarded BOOTREQUEST for 00:19:92:c6:9d:b6 to 10.160.5.2

Any proposals ?

Immo
This message has been classified General Business by IMMO WETZEL on Montag, 29. Januar 2018 at 15:22:25.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users