Bug #11539
closed
Mobile IPsec ``split_include`` value of ``0.0.0.0/0`` causes some clients to fail
Added by Jim Pingle about 3 years ago.
Updated 2 months ago.
Description
Currently for mobile IPsec the code sets up subnet and split_include entries for IPv4/IPv6 pools based on the GUI setting for networks to send to clients.
When split_include has a value of 0.0.0.0/0, some clients will fail to connect. A forum user reported this for the built-in Android IKEv2 client but there may be others.
So we either need to figure out some better logic about what to put in each of subnet and split_include separately or at the very least, do not add 0.0.0.0/0 or ::/0 to split_include.
Also warrants some more research in strongSwan to ensure both of those fields are being used appropriately.
Files
I can't find a client that can reproduce this so I can't confirm a fix. Attached is a patch which will omit 0.0.0.0/0 and ::/0 from the split_include line, or omit the line entirely if that is the only value.
Needs some testing before committing.
- Status changed from New to Feedback
- Plus Target Version set to 21.05
- Plus Target Version changed from 21.05 to 21.09
Nothing committed here yet and only one data point on if it's beneficial. Bumping this one up for the moment. I'd like to find a way to reproduce this and check that it doesn't break existing setups first.
- Plus Target Version changed from 21.09 to 22.01
There are other changes in 21.09 which may fix this, but leaving it open and moving target for now in case it needs additional work. Can remove target and close it if it works OK on 21.09.
- Plus Target Version changed from 22.01 to 22.05
- Plus Target Version changed from 22.05 to 22.09
Still no meaningful feedback here, can keep waiting until someone who can replicate the original problem can confirm if the suggested change helps.
Tested on 22.05 - I couldn't reproduce the original issue using the native (OxygenOS) android 11 IKEv2 MSCHAPv2 client.
- Plus Target Version changed from 22.09 to 22.11
- Plus Target Version changed from 22.11 to 23.01
- Status changed from Feedback to Ready To Test
- Plus Target Version changed from 23.01 to 23.05
Still no feedback on the proposed fix
- Subject changed from Mobile IPsec "split_include" value of 0.0.0.0/0 causes some clients to fail to Mobile IPsec ``split_include`` value of ``0.0.0.0/0`` causes some clients to fail
Updating subject for release notes.
- Plus Target Version changed from 23.05 to 23.09
- Plus Target Version changed from 23.09 to 24.01
Still waiting on an affected user to test and offer feedback.
- Plus Target Version changed from 24.01 to 24.03
- Status changed from Ready To Test to Rejected
- Target version deleted (
CE-Next)
- Plus Target Version deleted (
24.03)
The original reporter(s) of this issue have long since disappeared and nobody else seems to be able to reproduce the problem or offer feedback on the proposed change.
Closing this out for now but we can reopen this if anyone can offer meaningful feedback or specific instructions to reproduce the problem.
Also available in: Atom
PDF
Updated by 
Updated by