Hendrik van Wyk 96291d1de4 Do not do ipsec.InitSARemote on a stopped fastDatapathForwarder. ...

Fixes 3675

It is possible for ipsec.InitSARemote to be called after ipsec.Destroy.
If an xfrm policy for that source/destination pair exists it will be
updated to the SPI from the Destroyed connection causing IPSEC to stop
working.

2019-07-31 11:17:37 +02:00

..

awsvpc.go

Add fastdp crypto

2017-01-31 17:21:01 +00:00

ethernet_decoder.go

Merge branch '1.1'

2015-10-05 20:02:32 +01:00

fastdp.go

Do not do ipsec.InitSARemote on a stopped fastDatapathForwarder.

2019-07-31 11:17:37 +02:00

flow.go

Merge branch '1.4'

2016-02-29 14:07:02 -08:00

frame_crypto.go

refactor: split crypto code

2015-11-07 15:59:15 +00:00

http.go

updates to address comments by @bboreham

2018-08-31 14:26:00 -05:00

injector_consumer.go

Rename router.Bridge to router.InjectorConsumer

2017-04-25 11:03:32 +01:00

mac_cache.go

Update import location for mesh

2016-01-15 15:57:01 +01:00

network_overlay.go

changes differentiate beteween fatal errors (for e.g. ipsec init)

2018-09-21 16:45:47 +05:30

network_router_status.go

Rename router.Bridge to router.InjectorConsumer

2017-04-25 11:03:32 +01:00

network_router.go

Demote messages about MAC discovery and expiry to DEBUG level

2017-12-18 11:36:24 +00:00

overlay_switch.go

addressing review comments

2018-09-24 17:53:28 +05:30

pcap.go

Rename router.Bridge to router.InjectorConsumer

2017-04-25 11:03:32 +01:00

sleeve.go

Moved 'expecting PMTU' message to debug level

2019-05-03 15:28:44 +00:00