[EXTERNAL] Re: --request-ip not in the source code?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yep -- confirmed it works for me, here, too.

Observation:  The "typical" behavior is that the provided IP just increments across the range of available IPs on each successive connection to the VPN server.

I rebooted my client (forcing a reconnection each time) and observed that with --request-ip=x.x.x.x we can retain a specific IP across reconnections.

I did not test to see what happens if we request an IP that's already in use by another client.

Thanks!

-----Original Message-----
From: Daniel Lenski [mailto:dlenski at gmail.com] 
Sent: Monday, February 4, 2019 8:08 PM
To: Phillips, Tony
Cc: openconnect-devel at lists.infradead.org
Subject: Re: [EXTERNAL] Re: --request-ip not in the source code?

On Mon, Feb 4, 2019 at 5:32 PM Phillips, Tony <tonyphillips at ti.com> wrote:
>
> Hey, Dan!
>
> Thanks for your reply, and I realize I wasn?t very specific.
>
> I?m using Palo Alto globalprotect protocol, not Cisco.

Gotcha, okay. I rebased my patches for this on top of the latest v8.02
release: https://gitlab.com/dlenski/openconnect/tree/request_same_address_reconnect

This version works for me on 2 different GlobalProtect VPNs. I'm 99%
certain that I understand this perfectly for GlobalProtect, but It'd
be good to have you test it and confirm if it works for you as well.

Thanks,
Dan


[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux