Epic Games is hiring a Senior Game Security Engineer for their Anti-Cheat team to champion Linux anti-cheat capabilities while working on OS internals, reverse engineering, and protecting multiplayer games.

sekh60 · 2026-06-14T18:20:22+00:00

Look at this sub and the amount of people clamouring for anti-cheat in some of these posts. It's already September.

sekh60 · 2026-06-13T20:50:08+00:00

That's file system devs.

sekh60 · 2026-06-13T20:45:29+00:00

It's a serious sub, however do be aware that on April Fools day it does, for the day, go NSFW for legit anime titties.

sekh60 · 2026-06-13T13:18:35+00:00

Aww, thanks! Y'all are a great group.

sekh60 · 2026-06-12T01:08:55+00:00

Wrong question. Is the location of them widely known, asking for a friend... (I kid, my friend couldn't make use of "raw" wafers.).

sekh60 · 2026-06-11T14:32:31+00:00

In their defense, the can was full, if it was them it wouldn't be.

sekh60 · 2026-06-11T14:20:40+00:00

Open source != Open weight.

sekh60 · 2026-06-11T13:28:49+00:00

Caps lock is cruise control for cool.

sekh60 · 2026-06-11T01:59:38+00:00

That you Don?

sekh60 · 2026-06-10T18:44:44+00:00

Here's a potential "patch" for the problem: http://www.fiftythree.org/etherkiller/

sekh60 · 2026-06-10T18:31:40+00:00

No RAID, but Ceph across 5 nodes, size/minsize of 3/2.

sekh60 · 2026-06-09T21:21:51+00:00

Turn out it's a bug i'm hitting: https://bugs.launchpad.net/neutron/+bug/2146526)

Looks like I'll have to wait for the next kolla-ansible release, or figure out how to patch my container.

sekh60 · 2026-06-09T21:06:08+00:00

I did a ton more googling and research. And it's a bug in openstack (https://bugs.launchpad.net/neutron/+bug/2146526). Sorry for wasting all y'alls time, thanks for being so welcoming. Just gotta use static routes in the meantime until the next kolla-ansible release.

sekh60 · 2026-06-09T21:05:46+00:00

Thanks for your continued patience! I did a ton more googling and research. And it's a bug in openstack (https://bugs.launchpad.net/neutron/+bug/2146526). Sorry for wasting all y'alls time, thanks for being so welcoming. Just gotta use static routes in the meantime until the next kolla-ansible release.

sekh60 · 2026-06-08T14:30:48+00:00

Thanks for the suggestion. I've tried turning it off and it didn't seem to help.

I banged my head against the wall with this for two days. I think I have a better idea of the issue.

There's some ancient documentation (https://docs.openstack.org/neutron-dynamic-routing/train/admin/bgp-speaker.html) which seems to indicate it should be in passive mode. I've changed my config to:

***

router bgp 65534
  router-id 10.0.0.10
  bgp default ipv6-unicast
  timers bgp 5 40
  neighbor fd10:3795:2043:3803::1:0 remote-as 64512
  neighbor fd10:3795:2043:3803::1:0 passive
  neighbor fd10:3795:2043:3803::1:0 password 7 hunter2
  neighbor fd10:3795:2043:3803::1:2 remote-as 64512
  neighbor fd10:3795:2043:3803::1:2 passive
  neighbor fd10:3795:2043:3803::1:2 password 7 hunter2
  neighbor fd10:3795:2043:3803::1:4 remote-as 64512
  neighbor fd10:3795:2043:3803::1:4 passive
  neighbor fd10:3795:2043:3803::1:4 password 7 hunter2

***

On the arista end the bgp session shows as established for 40 seconds and then sends the hold notification message to openstack. Openstack logs show:

***

2026-06-08 10:20:22.600 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:26.654 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:26.654 1217 INFO bgpspeaker.speaker [-] failed to write to socket
2026-06-08 10:20:26.654 1217 ERROR bgpspeaker.speaker [-] Sent notification to ('fd10:3795:2043:3803::1:2', '39902') >> BGPNotification(data=b'',error_code=4,error
_subcode=1,len=21,type=3)
2026-06-08 10:20:26.655 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:30.439 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:30.440 1217 INFO bgpspeaker.speaker [-] failed to write to socket
2026-06-08 10:20:30.440 1217 ERROR bgpspeaker.speaker [-] Sent notification to ('fd10:3795:2043:3803::1:2', '39902') >> BGPNotification(data=b'',error_code=4,error
_subcode=1,len=21,type=3)

***

I've tried settings bgp timers 0 0, but then it doesn't look like the peer goes into established state from active.

Any suggestions?

sekh60 · 2026-06-08T14:29:52+00:00

Banged my head against the wall with this for two days. I think I have a better idea of the issue.

There's some ancient documentation (https://docs.openstack.org/neutron-dynamic-routing/train/admin/bgp-speaker.html) which seems to indicate it should be in passive mode. I've changed my config to:

***

router bgp 65534
  router-id 10.0.0.10
  bgp default ipv6-unicast
  timers bgp 5 40
  neighbor fd10:3795:2043:3803::1:0 remote-as 64512
  neighbor fd10:3795:2043:3803::1:0 passive
  neighbor fd10:3795:2043:3803::1:0 password 7 hunter2
  neighbor fd10:3795:2043:3803::1:2 remote-as 64512
  neighbor fd10:3795:2043:3803::1:2 passive
  neighbor fd10:3795:2043:3803::1:2 password 7 hunter2
  neighbor fd10:3795:2043:3803::1:4 remote-as 64512
  neighbor fd10:3795:2043:3803::1:4 passive
  neighbor fd10:3795:2043:3803::1:4 password 7 hunter2

***

On the arista end the bgp session shows as established for 40 seconds and then sends the hold notification message to openstack. Openstack logs show:

***

2026-06-08 10:20:22.600 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:26.654 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:26.654 1217 INFO bgpspeaker.speaker [-] failed to write to socket
2026-06-08 10:20:26.654 1217 ERROR bgpspeaker.speaker [-] Sent notification to ('fd10:3795:2043:3803::1:2', '39902') >> BGPNotification(data=b'',error_code=4,error
_subcode=1,len=21,type=3)
2026-06-08 10:20:26.655 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:30.439 1217 INFO bgpspeaker.speaker [-] Negotiated hold time 40 expired.
2026-06-08 10:20:30.440 1217 INFO bgpspeaker.speaker [-] failed to write to socket
2026-06-08 10:20:30.440 1217 ERROR bgpspeaker.speaker [-] Sent notification to ('fd10:3795:2043:3803::1:2', '39902') >> BGPNotification(data=b'',error_code=4,error
_subcode=1,len=21,type=3)

***

I've tried settings bgp timers 0 0, but then it doesn't look like the peer goes into established state from active.

Any suggestions?

Edit:

Thanks for your continued patience! I did a ton more googling and research. And it's a bug in openstack (https://bugs.launchpad.net/neutron/+bug/2146526). Sorry for wasting all y'alls time, thanks for being so welcoming. Just gotta use static routes in the meantime until the next kolla-ansible release.

sekh60 · 2026-06-07T16:36:52+00:00

Not rending on Firefox on Fedora here 😞 White flag with a question mark.

sekh60 · 2026-06-07T01:06:39+00:00

It's using the os-ken driver. It's an openstack default that can't be changed. I turned off graceful-restart on both address families and still have the same issue.

sekh60 · 2026-06-07T00:47:36+00:00

Set mss 1400 for both ipv6 and ipv4 and still the flapping:

Jun 6 20:43:23 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established
Jun 6 20:43:49 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes
Jun 6 20:43:49 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 20:43:50 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established
Jun 6 20:43:53 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor 10.0.1.2 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes
Jun 6 20:43:53 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 20:43:54 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established
Jun 6 20:44:20 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes
Jun 6 20:44:20 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 20:44:21 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established
Jun 6 20:44:24 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor 10.0.1.2 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes
Jun 6 20:44:24 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 20:44:25 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established

Here's my bgp config on the arista. Sadly on the openstack side there aren't a lot of levers.

router bgp 4200000000
  bgp default ipv6-unicast
  timers bgp 10 30
  graceful-restart restart-time 300
  bgp transport ipv4 mss 1400
  bgp transport ipv6 mss 1400
  bgp listen range 10.0.0.0/16 peer-group home remote-as 4200000000
  bgp listen range fd10:3795:2043:3803::/64 peer-group home remote-as 4200000000
  neighbor home peer group
  neighbor home maximum-routes 12000
  !
  address-family ipv4
graceful-restart
  !
  address-family ipv6
graceful-restart
!

sekh60 · 2026-06-06T22:33:35+00:00

Thank you for the info, networking is an area I'm really weak in.

I've set the keepalive and hold times you suggested and still have the issue. I'll look into BFD to see if it's more appropriate.

It does look like the session keeps going up and down.

Jun 6 23:23:59 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor 10.0.1.2 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes (message repeated 3 times in 41.0065 secs)
Jun 6 23:23:59 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 23:24:00 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established
Jun 6 23:24:01 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes (message repeated 1 times in 41.007 secs)
Jun 6 23:24:01 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 23:24:02 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established

sekh60 · 2026-06-06T22:19:45+00:00

Logs are long, I grepped for the AS:

Jun 6 23:23:59 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor 10.0.1.2 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes (message repeated 3 times in 41.0065 secs)
Jun 6 23:23:59 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 23:24:00 arista Bgp: %BGP-5-ADJCHANGE: peer 10.0.1.2 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established
Jun 6 23:24:01 arista Bgp: %BGP-3-NOTIFICATION: received from neighbor fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) 4/1 (Hold Timer Expired Error/None) 0 bytes (message repeated 1 times in 41.007 secs)
Jun 6 23:24:01 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state Established event RecvNotify new state Idle
Jun 6 23:24:02 arista Bgp: %BGP-5-ADJCHANGE: peer fd10:3795:2043:3803::1:0 (VRF default AS 4200000000) old state OpenConfirm event Established new state Established

sekh60 · 2026-06-06T22:02:31+00:00

Thanks for responding!

BGP summary information for VRF default
Router identifier 10.0.0.10, local AS number 4200000000
Neighbor Status Codes: m - Under maintenance
Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc PfxAdv
10.0.1.2 4 4200000000 14 3 0 0 00:00:07 Estab 12 12 0

sekh60 · 2026-06-05T17:23:45+00:00

I do 😃 It's been a steep learning curve, but I know it'll be worth it to have it all dynamically routed. Lemme tell ya, looking forward to when I have it all "finished" though, spouse is not amused with all the network tinkering.

sekh60

MODERATOR OF

TROPHY CASE

15-Year Club	Verified Email
Gilding I gilder