Great ... be sure to test the /23 .
Lonnie
> On Sep 5, 2021, at 6:30 PM, Michael Knill
> wrote:
>
> Thanks Lonnie
>
> No that cannot happen as the softswitch only connects to a single Astlinux
> peer IP address e.g. Peer 1 - 10.4.1.1/32, Peer 2 - 10.4.1.2/32
> All the Astlinux peers wo
Thanks Lonnie
No that cannot happen as the softswitch only connects to a single Astlinux peer
IP address e.g. Peer 1 - 10.4.1.1/32, Peer 2 - 10.4.1.2/32
All the Astlinux peers would have the same locally significant range
10.4.0.1-254. All calls to the softswitch from a remote peer are term
That should work, be a CIDR ninja. :-)
Though if you want your "softswitch" to route to a remote Mobile Client, /23's
all around might be needed.
Lonnie
> On Sep 5, 2021, at 4:47 PM, Michael Knill
> wrote:
>
> Thanks Lonnie
>
> So what I am thinking is that I will use a /23 on the remote
Thanks Lonnie
So what I am thinking is that I will use a /23 on the remote system but
continue to use /24 for my softswitch on the higher subnet. This will give a
total of 250 VPN connections to the Softswitch.
Each remote system will then have the lower subnet for local connectivity only
for
Hi Michael,
As per the docs, the range of .101 to .199 is reserved for mobile clients.
--
Note -> Mobile Clients are automatically assigned a unique IP address in the
range of .101 to .199 for the last octet (example here: 10.4.0.101 to
10.4.0.199). Best practice is to refrain from using IP's in
Hi Group
Is there any reason that I could not use the .101 to .199 subnet addresses for
Remote Peers? If I do add a mobile peer will it check Remote Peers when
allocating an IP addresses or would I need to manually check there are no
duplicates?
As I am moving to cloud hosting most of my system
