How to replace `warp-cli add-excluded-route ::/0` with `warp-cli tunnel ip add`?

[fscarmen]

Which Cloudflare product(s) does this pertain to?

WARP Client

Subject Matter

warp-cli tunnel ip add only one IP can be added. How to set it to CIDR

Content Location

How to use tunnel ip insteading
warp-cli add-excluded-route ::/0 and warp-cli add-excluded-route 0.0.0.0/0

What are the following two changes for?
warp-cli enable-always-on and warp-cli disable-always-on

Additional information

No response

[ranbel]

Hi @fscarmen, thanks for the feedback, but we only take care of developers.cloudflare.com in this repo. I have opened an internal ticket with the team that manages the warp-cli help text.

[midnight-wonderer]

Hi @ranbel,
Thanks for raising the issue with the team.

Quite a few folks on the Community Forum are also interested in this.
I am sure they will discover this thread on GitHub in no time.

FWIW: This is the issue with the WARP client itself and probably not the docs or help text specifically.
We want to exclude the traffic based on CIDR instead of a single IP address.

I wonder how or what channel we can subscribe to for updates?

[ranbel]

Hi @midnight-wonderer, we have an internal ticket (CLIENT-10076) tracking this feature request. If you're using WARP for Zero Trust, you can exclude CIDRs using the API or dashboard.

To receive updates on new WARP releases, I recommend subscribing to our changelog: https://developers.cloudflare.com/cloudflare-one/changelog/warp/

[midnight-wonderer]

Thanks for the info.

I am just a regular WARP user from 1.1.1.1 and do not use it in the Zero Trust platform context.
Only warp-cli is available to me (or us). That is also why, presumably, we who post on Community Forum and GitHub don't have access to the regular support channel.

While the update channel is not great, I am quite livable with it, considering that we don't directly contribute to Cloudflare revenue, just the negotiation power. I can't use WARP (with the official client) in my situation for now, but I am looking forward to the release.

Thanks again; I am sure this info will be useful for folks looking into the issue.

[ranbel]

Engineering has implemented a new command, warp-cli tunnel ip-range add/remove <cidr>. It won't be in the upcoming GA release, but is scheduled for the next GA.

[midnight-wonderer]

Following up with whoever reaches here via Google.
The feature is now available.

Check it out by:

warp-cli tunnel ip add-range --help

I tested, and CIDRs are accepted as a valid range.
Thanks again.

[fscarmen]

Following up with whoever reaches here via Google. The feature is now available.

Check it out by:

warp-cli tunnel ip add-range --help

I tested, and CIDRs are accepted as a valid range. Thanks again.

I tested and it 's ok now.
Thanks all.

[vhbui02]

I'm experiencing a weird output:

> warp-cli tunnel ip add-range 91.108.4.0/22
Not yet implemented.

@fscarmen Was your warp-cli release from Windows or MacOS?