Re: [openwisp] Pass custom peers from OpenWISP to Wireguard via Webhook

[Federico Capoano]

I created an issue for this use case here:
https://github.com/openwisp/openwisp-controller/issues/788 .

Federico

On Sat, 1 Jul 2023 at 06:51, Rajesh Nandi 
wrote:

> I am interested
>
> On Sat, 1 Jul, 2023, 3:01 am Shawn Lyons,  wrote:
>
>> That worked. I added the two servers in as OpenWRT devices, used the
>> existing Wireguard VPN template, and now It's included those peers when
>> passing the webhook data - no more dropping hosts.
>> Thanks very much,
>> Shawn
>>
>> On Friday, June 30, 2023 at 2:03:51 PM UTC-6 f.capoano wrote:
>>
>>> Hi Shawn,
>>>
>>> an interesting case. I think the best option is to create fake devices
>>> which act as placeholders and reserve the IP addresses you need for these
>>> clients. Otherwise you risk OpenWISP assigning these IPs to other devices
>>> and run into conflicts.
>>> I had tried this in the past and it worked, please try, if you can
>>> confirm this solves your issue I think we could document this workaround
>>> and simply hide that "peers" section as I don't think it can ensure a
>>> conflict free solution (unless we implement one, which could also be an
>>> option).
>>>
>>> Best regards
>>> *Federico Capoano*
>>> OpenWISP OÜ
>>> Harjumaa, Tallinn, Sepapaja tn 6, 15551
>>> VAT: EE101989729
>>> *openwisp.io* 
>>>
>>>
>>> On Fri, 30 Jun 2023 at 13:25, Shawn Lyons  wrote:
>>>
 In the VPN section of OpenWISP I have a Wireguard server configured,
 using the Webhook including two Peers defined in the Object Properties. The
 hope and assumption I had, is that these custom peers would be included in
 the configuration that the webhook passes to the wireguard server, along
 with the wireguard device clients.

 These two peers are my OpenWISP and Radius server, so they are included
 in the wireguard tunnel, facilitating easy communication between all
 applications. When a new device is added, and the webhook is processed,
 only the device clients are passed to the wireguard server, so these 2
 peers are removed from the wireguard config and I have to manually add them
 back.

 Is it possible to pass these custom peer objects defined in the
 Configurations->VPN Servers->Wireguard through the webhook?

 --
 You received this message because you are subscribed to the Google
 Groups "OpenWISP" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to openwisp+u...@googlegroups.com.
 To view this discussion on the web, visit
 https://groups.google.com/d/msgid/openwisp/e724a2f3-47a1-4998-b0be-b685bca932f8n%40googlegroups.com
 
 .

>>> --
>> You received this message because you are subscribed to the Google Groups
>> "OpenWISP" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to openwisp+unsubscr...@googlegroups.com.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msgid/openwisp/21454e70-ab3f-41f8-8548-cd046717a1e2n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenWISP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openwisp+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/openwisp/CAN_96z0fmBu%3DQ1JPaR1zvF2GOyDsD1hRAO%3D-bvAmHZr-YP8Vsg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to openwisp+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/CAAGgX6%2BhWjT9AQ6T8LyEGT5Y62K6%2BRDTkyTC%2BdBSWqwgjUmyqw%40mail.gmail.com.

Re: [openwisp] Pass custom peers from OpenWISP to Wireguard via Webhook

[Rajesh Nandi]

I am interested

On Sat, 1 Jul, 2023, 3:01 am Shawn Lyons,  wrote:

> That worked. I added the two servers in as OpenWRT devices, used the
> existing Wireguard VPN template, and now It's included those peers when
> passing the webhook data - no more dropping hosts.
> Thanks very much,
> Shawn
>
> On Friday, June 30, 2023 at 2:03:51 PM UTC-6 f.capoano wrote:
>
>> Hi Shawn,
>>
>> an interesting case. I think the best option is to create fake devices
>> which act as placeholders and reserve the IP addresses you need for these
>> clients. Otherwise you risk OpenWISP assigning these IPs to other devices
>> and run into conflicts.
>> I had tried this in the past and it worked, please try, if you can
>> confirm this solves your issue I think we could document this workaround
>> and simply hide that "peers" section as I don't think it can ensure a
>> conflict free solution (unless we implement one, which could also be an
>> option).
>>
>> Best regards
>> *Federico Capoano*
>> OpenWISP OÜ
>> Harjumaa, Tallinn, Sepapaja tn 6, 15551
>> VAT: EE101989729
>> *openwisp.io* 
>>
>>
>> On Fri, 30 Jun 2023 at 13:25, Shawn Lyons  wrote:
>>
>>> In the VPN section of OpenWISP I have a Wireguard server configured,
>>> using the Webhook including two Peers defined in the Object Properties. The
>>> hope and assumption I had, is that these custom peers would be included in
>>> the configuration that the webhook passes to the wireguard server, along
>>> with the wireguard device clients.
>>>
>>> These two peers are my OpenWISP and Radius server, so they are included
>>> in the wireguard tunnel, facilitating easy communication between all
>>> applications. When a new device is added, and the webhook is processed,
>>> only the device clients are passed to the wireguard server, so these 2
>>> peers are removed from the wireguard config and I have to manually add them
>>> back.
>>>
>>> Is it possible to pass these custom peer objects defined in the
>>> Configurations->VPN Servers->Wireguard through the webhook?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "OpenWISP" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to openwisp+u...@googlegroups.com.
>>> To view this discussion on the web, visit
>>> https://groups.google.com/d/msgid/openwisp/e724a2f3-47a1-4998-b0be-b685bca932f8n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "OpenWISP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openwisp+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/openwisp/21454e70-ab3f-41f8-8548-cd046717a1e2n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to openwisp+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/CAN_96z0fmBu%3DQ1JPaR1zvF2GOyDsD1hRAO%3D-bvAmHZr-YP8Vsg%40mail.gmail.com.

Re: [openwisp] Pass custom peers from OpenWISP to Wireguard via Webhook

[Shawn Lyons]

That worked. I added the two servers in as OpenWRT devices, used the 
existing Wireguard VPN template, and now It's included those peers when 
passing the webhook data - no more dropping hosts.
Thanks very much,
Shawn

On Friday, June 30, 2023 at 2:03:51 PM UTC-6 f.capoano wrote:

> Hi Shawn,
>
> an interesting case. I think the best option is to create fake devices 
> which act as placeholders and reserve the IP addresses you need for these 
> clients. Otherwise you risk OpenWISP assigning these IPs to other devices 
> and run into conflicts.
> I had tried this in the past and it worked, please try, if you can confirm 
> this solves your issue I think we could document this workaround and simply 
> hide that "peers" section as I don't think it can ensure a conflict free 
> solution (unless we implement one, which could also be an option).
>
> Best regards
> *Federico Capoano*
> OpenWISP OÜ
> Harjumaa, Tallinn, Sepapaja tn 6, 15551
> VAT: EE101989729
> *openwisp.io* 
>
>
> On Fri, 30 Jun 2023 at 13:25, Shawn Lyons  wrote:
>
>> In the VPN section of OpenWISP I have a Wireguard server configured, 
>> using the Webhook including two Peers defined in the Object Properties. The 
>> hope and assumption I had, is that these custom peers would be included in 
>> the configuration that the webhook passes to the wireguard server, along 
>> with the wireguard device clients.
>>
>> These two peers are my OpenWISP and Radius server, so they are included 
>> in the wireguard tunnel, facilitating easy communication between all 
>> applications. When a new device is added, and the webhook is processed, 
>> only the device clients are passed to the wireguard server, so these 2 
>> peers are removed from the wireguard config and I have to manually add them 
>> back.
>>
>> Is it possible to pass these custom peer objects defined in the 
>> Configurations->VPN Servers->Wireguard through the webhook?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "OpenWISP" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to openwisp+u...@googlegroups.com.
>> To view this discussion on the web, visit 
>> https://groups.google.com/d/msgid/openwisp/e724a2f3-47a1-4998-b0be-b685bca932f8n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to openwisp+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/21454e70-ab3f-41f8-8548-cd046717a1e2n%40googlegroups.com.

Re: [openwisp] Pass custom peers from OpenWISP to Wireguard via Webhook

[Federico Capoano]

Hi Shawn,

an interesting case. I think the best option is to create fake devices
which act as placeholders and reserve the IP addresses you need for these
clients. Otherwise you risk OpenWISP assigning these IPs to other devices
and run into conflicts.
I had tried this in the past and it worked, please try, if you can confirm
this solves your issue I think we could document this workaround and simply
hide that "peers" section as I don't think it can ensure a conflict free
solution (unless we implement one, which could also be an option).

Best regards
*Federico Capoano*
OpenWISP OÜ
Harjumaa, Tallinn, Sepapaja tn 6, 15551
VAT: EE101989729
*openwisp.io* 


On Fri, 30 Jun 2023 at 13:25, Shawn Lyons  wrote:

> In the VPN section of OpenWISP I have a Wireguard server configured, using
> the Webhook including two Peers defined in the Object Properties. The hope
> and assumption I had, is that these custom peers would be included in the
> configuration that the webhook passes to the wireguard server, along with
> the wireguard device clients.
>
> These two peers are my OpenWISP and Radius server, so they are included in
> the wireguard tunnel, facilitating easy communication between all
> applications. When a new device is added, and the webhook is processed,
> only the device clients are passed to the wireguard server, so these 2
> peers are removed from the wireguard config and I have to manually add them
> back.
>
> Is it possible to pass these custom peer objects defined in the
> Configurations->VPN Servers->Wireguard through the webhook?
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenWISP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openwisp+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/openwisp/e724a2f3-47a1-4998-b0be-b685bca932f8n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to openwisp+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/CAAGgX6Lf%3D8bubwqOU%3D_G145B8a8WyEpbLtOur3Sxx46XdB2s2A%40mail.gmail.com.