date:20230404

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

2023-04-04 Thread Federico Capoano

See here:
https://github.com/openwisp/docker-openwisp/blob/master/docs/ENV.md#ssl_cert_mode
It seems there's a way to turn HTTPS off entirely.

F.

On Tue, 4 Apr 2023 at 14:46, François Noah  wrote:

> thanks for yours awnsers, it will help me.
> my instance of wifi-login-pages and  openwisp docker run on the same
> computer . my question is which cetificate is checkeed by wifi-login-page
> ?where is it stored.
> i created a self signed certificate linked to my ip 192.168.1.157
> (build.lab)  adn i saved it to /etc/ssl/cert and /ect/ssl/private (for
> private key)
> do you have any idea where i have to save my certificate ?
>
> regards
>
> François NOAH
>
> Le mar. 4 avr. 2023 à 19:52, Federico Capoano  a
> écrit :
>
>> I never ran into this issue when testing locally. I think it's because
>> docker-openwisp is not meant for testing locally and it pushes you to use
>> HTTPS, for which you do not have a valid certificate and for that reason
>> nodeJS complains when used through wifi-login-pages.
>>
>> To test wifi-login-pages
>>  locally I have
>> my dev org YAML file which points to a local development instance of
>> openwisp-radius  (also
>> running on HTTP) and I run:
>>
>> yarn setup
>> yarn start
>>
>> Instructions for running openwisp-radius for development are here:
>> https://openwisp-radius.readthedocs.io/en/latest/developer/setup.html#installing-for-development
>> We use the same setup in the CI to run browser based tests:
>> https://github.com/openwisp/openwisp-wifi-login-pages/blob/master/.github/workflows/ci.yml#L79-L116
>> .
>>
>> Alternatively, if you need to continue using docker-openwisp for
>> freeradius and openwisp-radius, I think you would need to change the code
>> of the server side part of openwisp-wifi-login-pages to ignore the SSL
>> warning:
>>
>> https://stackoverflow.com/questions/51363855/how-to-configure-axios-to-use-ssl-certificate
>>
>> I hope this helps!
>>
>> Best regards
>> Federico Capoano
>>
>> On Tue, 4 Apr 2023 at 13:38, François Noah  wrote:
>>
>>> it is not for production , i need to test it on my computer.
>>> i created a self signed certificate and
>>> i store certificate on my computer and on my docker container ( i use
>>> openwisp-docker)
>>> but i still have the same error
>>>
>>> eap eap-irecycle {
>>> default_eap_type = ttls
>>> timer_expire = 60
>>> ignore_unknown_eap_types = no
>>> cisco_accounting_username_bug = no
>>> max_sessions = ${max_requests}
>>>
>>> tls-config tls-common {
>>> # make sure to have a valid SSL certificate for production usage
>>> private_key_password = whatever
>>> private_key_file = /etc/ssl/private/example.key
>>> certificate_file = /etc/ssl/certs/example.pem
>>> ca_file = /etc/ssl/certs/example.crt
>>> dh_file = ${certdir}/dh
>>> ca_path = ${cadir}
>>> cipher_list = "DEFAULT"
>>> cipher_server_preference = no
>>> ecdh_curve = "prime256v1"
>>>
>>> cache {
>>> enable = no
>>> }
>>>
>>> ocsp {
>>> enable = no
>>> override_cert_url = yes
>>> url = "http://127.0.0.1/ocsp/";
>>> }
>>> }
>>>
>>> ttls {
>>> tls = tls-common
>>> default_eap_type = pap
>>> copy_request_to_tunnel = yes
>>> use_tunneled_reply = yes
>>> virtual_server = "inner-tunnel_irecycle"
>>> }
>>> }
>>>
>>> Le mardi 4 avril 2023 à 16:33:57 UTC+2, f.capoano a écrit :
>>>
 This is the error: *Error: self signed certificate.*

 For production usage you need a valid SSL certificate.

 Best regards
 Federico


 On Tue, 4 Apr 2023 at 08:57, François Noah  wrote:

> hello,
> i'am trying to use openwisp-wifi-login-pages but i get zrror below
>
> [
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *ERROR 2023-04-04 13:30:39:3039] {[0]   error: Error: self signed
> certificate[0]   at TLSSocket.onConnectSecure
> (node:_tls_wrap:1530:34)[0]   at TLSSocket.emit 
> (node:events:520:28)[0]
>   at TLSSocket.emit (node:domain:475:12)[0]   at
> TLSSocket._finishInit (node:_tls_wrap:944:8)[0]   at
> TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {[0] code:
> 'DEPTH_ZERO_SELF_SIGNED_CERT',[0] config: {[0]   transitional:
> [Object],[0]   adapter: [Function: httpAdapter],[0]
> transformRequest: [Array],[0]   transformResponse: [Array],[0]
> timeout: 2000,[0]   xsrfCookieName: 'XSRF-TOKEN',[0]
> xsrfHeaderName: 'X-XSRF-TOKEN',[0]   maxContentLength: -1,[0]
> maxBodyLength: -1,[0]   validateStatus: [Function: validateStatus],[0]
>   headers: [Object],[0]   method: 'post',[0]   url:
> 'http://api.b

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

2023-04-04 Thread François Noah

thanks for yours awnsers, it will help me.
my instance of wifi-login-pages and  openwisp docker run on the same
computer . my question is which cetificate is checkeed by wifi-login-page
?where is it stored.
i created a self signed certificate linked to my ip 192.168.1.157
(build.lab)  adn i saved it to /etc/ssl/cert and /ect/ssl/private (for
private key)
do you have any idea where i have to save my certificate ?

regards

François NOAH

Le mar. 4 avr. 2023 à 19:52, Federico Capoano  a
écrit :

> I never ran into this issue when testing locally. I think it's because
> docker-openwisp is not meant for testing locally and it pushes you to use
> HTTPS, for which you do not have a valid certificate and for that reason
> nodeJS complains when used through wifi-login-pages.
>
> To test wifi-login-pages
>  locally I have my
> dev org YAML file which points to a local development instance of
> openwisp-radius  (also
> running on HTTP) and I run:
>
> yarn setup
> yarn start
>
> Instructions for running openwisp-radius for development are here:
> https://openwisp-radius.readthedocs.io/en/latest/developer/setup.html#installing-for-development
> We use the same setup in the CI to run browser based tests:
> https://github.com/openwisp/openwisp-wifi-login-pages/blob/master/.github/workflows/ci.yml#L79-L116
> .
>
> Alternatively, if you need to continue using docker-openwisp for
> freeradius and openwisp-radius, I think you would need to change the code
> of the server side part of openwisp-wifi-login-pages to ignore the SSL
> warning:
>
> https://stackoverflow.com/questions/51363855/how-to-configure-axios-to-use-ssl-certificate
>
> I hope this helps!
>
> Best regards
> Federico Capoano
>
> On Tue, 4 Apr 2023 at 13:38, François Noah  wrote:
>
>> it is not for production , i need to test it on my computer.
>> i created a self signed certificate and
>> i store certificate on my computer and on my docker container ( i use
>> openwisp-docker)
>> but i still have the same error
>>
>> eap eap-irecycle {
>> default_eap_type = ttls
>> timer_expire = 60
>> ignore_unknown_eap_types = no
>> cisco_accounting_username_bug = no
>> max_sessions = ${max_requests}
>>
>> tls-config tls-common {
>> # make sure to have a valid SSL certificate for production usage
>> private_key_password = whatever
>> private_key_file = /etc/ssl/private/example.key
>> certificate_file = /etc/ssl/certs/example.pem
>> ca_file = /etc/ssl/certs/example.crt
>> dh_file = ${certdir}/dh
>> ca_path = ${cadir}
>> cipher_list = "DEFAULT"
>> cipher_server_preference = no
>> ecdh_curve = "prime256v1"
>>
>> cache {
>> enable = no
>> }
>>
>> ocsp {
>> enable = no
>> override_cert_url = yes
>> url = "http://127.0.0.1/ocsp/";
>> }
>> }
>>
>> ttls {
>> tls = tls-common
>> default_eap_type = pap
>> copy_request_to_tunnel = yes
>> use_tunneled_reply = yes
>> virtual_server = "inner-tunnel_irecycle"
>> }
>> }
>>
>> Le mardi 4 avril 2023 à 16:33:57 UTC+2, f.capoano a écrit :
>>
>>> This is the error: *Error: self signed certificate.*
>>>
>>> For production usage you need a valid SSL certificate.
>>>
>>> Best regards
>>> Federico
>>>
>>>
>>> On Tue, 4 Apr 2023 at 08:57, François Noah  wrote:
>>>
 hello,
 i'am trying to use openwisp-wifi-login-pages but i get zrror below

 [






















 *ERROR 2023-04-04 13:30:39:3039] {[0]   error: Error: self signed
 certificate[0]   at TLSSocket.onConnectSecure
 (node:_tls_wrap:1530:34)[0]   at TLSSocket.emit (node:events:520:28)[0]
   at TLSSocket.emit (node:domain:475:12)[0]   at
 TLSSocket._finishInit (node:_tls_wrap:944:8)[0]   at
 TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {[0] code:
 'DEPTH_ZERO_SELF_SIGNED_CERT',[0] config: {[0]   transitional:
 [Object],[0]   adapter: [Function: httpAdapter],[0]
 transformRequest: [Array],[0]   transformResponse: [Array],[0]
 timeout: 2000,[0]   xsrfCookieName: 'XSRF-TOKEN',[0]
 xsrfHeaderName: 'X-XSRF-TOKEN',[0]   maxContentLength: -1,[0]
 maxBodyLength: -1,[0]   validateStatus: [Function: validateStatus],[0]
   headers: [Object],[0]   method: 'post',[0]   url:
 'http://api.build.lab/api/v1/radius/organization/default/account/
 ',[0]
   data:
 '{"email":"te...@test.com","username":"te...@test.com","password1":"azerty","password2":"azerty"}'[0]
 },*

 registrration works when a use  api
 https://api.build.lab/api/v1/radius/organization/def

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

2023-04-04 Thread Federico Capoano

I never ran into this issue when testing locally. I think it's because
docker-openwisp is not meant for testing locally and it pushes you to use
HTTPS, for which you do not have a valid certificate and for that reason
nodeJS complains when used through wifi-login-pages.

To test wifi-login-pages
 locally I have my
dev org YAML file which points to a local development instance of
openwisp-radius  (also
running on HTTP) and I run:

yarn setup
yarn start

Instructions for running openwisp-radius for development are here:
https://openwisp-radius.readthedocs.io/en/latest/developer/setup.html#installing-for-development
We use the same setup in the CI to run browser based tests:
https://github.com/openwisp/openwisp-wifi-login-pages/blob/master/.github/workflows/ci.yml#L79-L116
.

Alternatively, if you need to continue using docker-openwisp for freeradius
and openwisp-radius, I think you would need to change the code of the
server side part of openwisp-wifi-login-pages to ignore the SSL warning:
https://stackoverflow.com/questions/51363855/how-to-configure-axios-to-use-ssl-certificate

I hope this helps!

Best regards
Federico Capoano

On Tue, 4 Apr 2023 at 13:38, François Noah  wrote:

> it is not for production , i need to test it on my computer.
> i created a self signed certificate and
> i store certificate on my computer and on my docker container ( i use
> openwisp-docker)
> but i still have the same error
>
> eap eap-irecycle {
> default_eap_type = ttls
> timer_expire = 60
> ignore_unknown_eap_types = no
> cisco_accounting_username_bug = no
> max_sessions = ${max_requests}
>
> tls-config tls-common {
> # make sure to have a valid SSL certificate for production usage
> private_key_password = whatever
> private_key_file = /etc/ssl/private/example.key
> certificate_file = /etc/ssl/certs/example.pem
> ca_file = /etc/ssl/certs/example.crt
> dh_file = ${certdir}/dh
> ca_path = ${cadir}
> cipher_list = "DEFAULT"
> cipher_server_preference = no
> ecdh_curve = "prime256v1"
>
> cache {
> enable = no
> }
>
> ocsp {
> enable = no
> override_cert_url = yes
> url = "http://127.0.0.1/ocsp/";
> }
> }
>
> ttls {
> tls = tls-common
> default_eap_type = pap
> copy_request_to_tunnel = yes
> use_tunneled_reply = yes
> virtual_server = "inner-tunnel_irecycle"
> }
> }
>
> Le mardi 4 avril 2023 à 16:33:57 UTC+2, f.capoano a écrit :
>
>> This is the error: *Error: self signed certificate.*
>>
>> For production usage you need a valid SSL certificate.
>>
>> Best regards
>> Federico
>>
>>
>> On Tue, 4 Apr 2023 at 08:57, François Noah  wrote:
>>
>>> hello,
>>> i'am trying to use openwisp-wifi-login-pages but i get zrror below
>>>
>>> [
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *ERROR 2023-04-04 13:30:39:3039] {[0]   error: Error: self signed
>>> certificate[0]   at TLSSocket.onConnectSecure
>>> (node:_tls_wrap:1530:34)[0]   at TLSSocket.emit (node:events:520:28)[0]
>>>   at TLSSocket.emit (node:domain:475:12)[0]   at
>>> TLSSocket._finishInit (node:_tls_wrap:944:8)[0]   at
>>> TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {[0] code:
>>> 'DEPTH_ZERO_SELF_SIGNED_CERT',[0] config: {[0]   transitional:
>>> [Object],[0]   adapter: [Function: httpAdapter],[0]
>>> transformRequest: [Array],[0]   transformResponse: [Array],[0]
>>> timeout: 2000,[0]   xsrfCookieName: 'XSRF-TOKEN',[0]
>>> xsrfHeaderName: 'X-XSRF-TOKEN',[0]   maxContentLength: -1,[0]
>>> maxBodyLength: -1,[0]   validateStatus: [Function: validateStatus],[0]
>>>   headers: [Object],[0]   method: 'post',[0]   url:
>>> 'http://api.build.lab/api/v1/radius/organization/default/account/
>>> ',[0]
>>>   data:
>>> '{"email":"te...@test.com","username":"te...@test.com","password1":"azerty","password2":"azerty"}'[0]
>>> },*
>>>
>>> registrration works when a use  api
>>> https://api.build.lab/api/v1/radius/organization/default/account/
>>>
>>> I want to know which certificate is used by openwisp-wifi-login-pages ?
>>> is it a bug ? anyone know how i can solve it ?
>>>
>>>
>>> --
>>> 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/7aaa8eed-d857-4c50-81e0-cecee6f1e4c0n%40googlegroups.com
>>>

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

2023-04-04 Thread François Noah

it is not for production , i need to test it on my computer.  
i created a self signed certificate and 
i store certificate on my computer and on my docker container ( i use 
openwisp-docker)
but i still have the same error 

eap eap-irecycle {
default_eap_type = ttls
timer_expire = 60
ignore_unknown_eap_types = no
cisco_accounting_username_bug = no
max_sessions = ${max_requests}

tls-config tls-common {
# make sure to have a valid SSL certificate for production usage
private_key_password = whatever
private_key_file = /etc/ssl/private/example.key
certificate_file = /etc/ssl/certs/example.pem
ca_file = /etc/ssl/certs/example.crt
dh_file = ${certdir}/dh
ca_path = ${cadir}
cipher_list = "DEFAULT"
cipher_server_preference = no
ecdh_curve = "prime256v1"

cache {
enable = no
}

ocsp {
enable = no
override_cert_url = yes
url = "http://127.0.0.1/ocsp/";
}
}

ttls {
tls = tls-common
default_eap_type = pap
copy_request_to_tunnel = yes
use_tunneled_reply = yes
virtual_server = "inner-tunnel_irecycle"
}
} 

Le mardi 4 avril 2023 à 16:33:57 UTC+2, f.capoano a écrit :

> This is the error: *Error: self signed certificate.*
>
> For production usage you need a valid SSL certificate.
>
> Best regards
> Federico
>
>
> On Tue, 4 Apr 2023 at 08:57, François Noah  wrote:
>
>> hello,
>> i'am trying to use openwisp-wifi-login-pages but i get zrror below 
>>
>> [
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *ERROR 2023-04-04 13:30:39:3039] {[0]   error: Error: self signed 
>> certificate[0]   at TLSSocket.onConnectSecure 
>> (node:_tls_wrap:1530:34)[0]   at TLSSocket.emit (node:events:520:28)[0] 
>>   at TLSSocket.emit (node:domain:475:12)[0]   at 
>> TLSSocket._finishInit (node:_tls_wrap:944:8)[0]   at 
>> TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {[0] code: 
>> 'DEPTH_ZERO_SELF_SIGNED_CERT',[0] config: {[0]   transitional: 
>> [Object],[0]   adapter: [Function: httpAdapter],[0]   
>> transformRequest: [Array],[0]   transformResponse: [Array],[0]   
>> timeout: 2000,[0]   xsrfCookieName: 'XSRF-TOKEN',[0]   
>> xsrfHeaderName: 'X-XSRF-TOKEN',[0]   maxContentLength: -1,[0]   
>> maxBodyLength: -1,[0]   validateStatus: [Function: validateStatus],[0] 
>>   headers: [Object],[0]   method: 'post',[0]   url: 
>> 'http://api.build.lab/api/v1/radius/organization/default/account/ 
>> ',[0] 
>>   data: 
>> '{"email":"te...@test.com","username":"te...@test.com","password1":"azerty","password2":"azerty"}'[0]
>>  
>> },*
>>
>> registrration works when a use  api 
>> https://api.build.lab/api/v1/radius/organization/default/account/
>>
>> I want to know which certificate is used by openwisp-wifi-login-pages ? 
>> is it a bug ? anyone know how i can solve it ?
>>
>>
>> -- 
>> 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/7aaa8eed-d857-4c50-81e0-cecee6f1e4c0n%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/b5b1c018-de0d-4d23-8a67-1d0d7ad4ab27n%40googlegroups.com.

Re: [openwisp] Network topology

2023-04-04 Thread Federico Capoano

Michele, that's most probably due to the OpenVPN status format version.
We use this library under the hood to parse that format:
https://github.com/tonyseek/openvpn-status
It supports only one version, OpenVPN supports two different formats, the
format you shared doesn't look like the one supported by the library,
that's why it is not working.

I hope this helps.
Federico

On Tue, 4 Apr 2023 at 13:32, Michele Salerno  wrote:

> I use openvpn but don't works.
>
> On my openvpn server i have this option "management localhost 7505"
> My templates on openwisp is:
>
> #!/bin/sh
> COLLECTOR_URL="https://controller.nnxx.ninux.org/api/v1/network-topology/topology/81461fe7-479b-4a6d-96cc-7b873bcd4efe/receive/?key=qGfhxlhfepEllYDiheZIBrNQVRgqcsM0";
>  
> 
> DATA=$(cat /var/log/openvpn.stats)
> curl -s -X POST -d "$DATA" --header "Content-Type: text/plain" $COLLECTOR_URL
>
> i run this: /usr/sbin/send_topology
>
> {"detail":"Supplied data not recognized as OpenVPN, got exception of type 
> \"ConversionException\" with message \"OpenVPN parsing error: expected 
> 'OpenVPN CLIENT LIST' but got 'OpenVPN STATISTICS'\""}
>
> # more /var/log/openvpn.stats
>
> OpenVPN STATISTICS
> Updated,2023-04-02 23:04:29
> TUN/TAP read bytes,5005389
> TUN/TAP write bytes,19304454
> TCP/UDP read bytes,22829623
> TCP/UDP write bytes,5995265
> Auth read bytes,19304560
> pre-compress bytes,0
> post-compress bytes,0
> pre-decompress bytes,0
> post-decompress bytes,0
> END
>
> I never understood how to make it work.
>
> Thanks.
>
>
> Il 29/03/23 14:00, Federico Capoano ha scritto:
>
> The softwares currently supported are:
>
> VPNs:
>
> - OpenVPN
> - Wireguard
>
> Format:
>
> - NetJSON NetworkGraph
>
> Dynamic routing demons:
>
> - OLSRd
> - Batman-advanced
> - other less known routing deamons and formats
>
> It is also possible to write a parser to supply the data to the collector
> in NetJSON NetworkGraph format.
>
> The main question is: what kind of networking technology are you using and
> how does your topology look?
> Is it a LAN network, an OSPF network, etc.
>
> The topology module was built mainly to show topologies of wireless
> networks, these networks are usually deployed using routing protocol
> software which are able to collect the topology information.
> But the same concept can be adapted to other situations.
>
> Best regards
> Federico Capoano
>
>
> On Tue, 28 Mar 2023 at 17:20, Daniele Cerasuolo 
> wrote:
>
>> Hi Federico,
>> first of all thank you for your quick response and your great job.
>> Actually the question is if there is something integrated to retrieve this
>> data. In case it does not exist, what kind of software do you recommend
>> besides openvpn?
>>
>> Il lun 27 mar 2023, 16:04 Federico Capoano  ha
>> scritto:
>>
>>> Hi,
>>>
>>> The topology module needs to be fed topology data which is parsed and
>>> sent to the collector.
>>> Usually some networking software like OpenVPN or a dynamic routing
>>> protocol have the topology information which can be parsed and collected.
>>> From what software do you want to collect the network topology from?
>>>
>>> Federico
>>>
>>> On Mon, 27 Mar 2023 at 04:59, Daniele Cerasuolo <
>>> d.cerasu...@gematica.com> wrote:
>>>
 hi, I am trying to configure the network topology on my installation
 with an openwrt test device installed in a virtual machine. From directives
 i can't install an openvpn server, what is the easiest method to implement
 the topology? i tried with the script

#!/bin/sh
 BASE_URL="https://network-topology-visualizer.mynetwork.org";
 UUID="4e38397a-4254-4521-89a6-045db25b8de6"
 KEY="S9wCfjeFN8irasZNiV7dGcyK68BTES0m"

 COLLECTOR_URL="$BASE_URL/api/receive/$UUID/?key=$KEY"
 DATA=$(echo "/netjsoninfo filter graph ipv4_0" | nc 127.0.0.1 2009)
 curl -s -X POST -d "$DATA" --header "Content-Type: text/plain"
 $COLLECTOR_URL

 but entering my data seems not to work

 --
 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/b48c900d-29f8-4b8c-a984-68cdd41b93a1n%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/ope

Re: [openwisp] Network topology

2023-04-04 Thread Michele Salerno


I use openvpn but don't works.

On my openvpn server i have this option "management localhost 7505"
My templates on openwisp is:

#!/bin/sh
COLLECTOR_URL="https://controller.nnxx.ninux.org/api/v1/network-topology/topology/81461fe7-479b-4a6d-96cc-7b873bcd4efe/receive/?key=qGfhxlhfepEllYDiheZIBrNQVRgqcsM0";
DATA=$(cat /var/log/openvpn.stats)
curl -s -X POST -d "$DATA" --header "Content-Type: text/plain" $COLLECTOR_URL

i run this: /usr/sbin/send_topology

{"detail":"Supplied data not recognized as OpenVPN, got exception of type 
\"ConversionException\" with message \"OpenVPN parsing error: expected 'OpenVPN CLIENT LIST' but got 
'OpenVPN STATISTICS'\""}

# more /var/log/openvpn.stats

OpenVPN STATISTICS
Updated,2023-04-02 23:04:29
TUN/TAP read bytes,5005389
TUN/TAP write bytes,19304454
TCP/UDP read bytes,22829623
TCP/UDP write bytes,5995265
Auth read bytes,19304560
pre-compress bytes,0
post-compress bytes,0
pre-decompress bytes,0
post-decompress bytes,0
END

I never understood how to make it work.

Thanks.


Il 29/03/23 14:00, Federico Capoano ha scritto:

The softwares currently supported are:

VPNs:

- OpenVPN
- Wireguard

Format:

- NetJSON NetworkGraph

Dynamic routing demons:

- OLSRd
- Batman-advanced
- other less known routing deamons and formats

It is also possible to write a parser to supply the data to the 
collector in NetJSON NetworkGraph format.


The main question is: what kind of networking technology are you using 
and how does your topology look?

Is it a LAN network, an OSPF network, etc.

The topology module was built mainly to show topologies of wireless 
networks, these networks are usually deployed using routing protocol 
software which are able to collect the topology information.

But the same concept can be adapted to other situations.

Best regards
Federico Capoano


On Tue, 28 Mar 2023 at 17:20, Daniele Cerasuolo 
 wrote:


Hi Federico,
first of all thank you for your quick response and your great job.
Actually the question is if there is something integrated to
retrieve this data. In case it does not exist, what kind of
software do you recommend besides openvpn?

Il lun 27 mar 2023, 16:04 Federico Capoano 
ha scritto:

Hi,

The topology module needs to be fed topology data which is
parsed and sent to the collector.
Usually some networking software like OpenVPN or a dynamic
routing protocol have the topology information which can be
parsed and collected.
From what software do you want to collect the network topology
from?

Federico

On Mon, 27 Mar 2023 at 04:59, Daniele Cerasuolo
 wrote:

hi, I am trying to configure the network topology on my
installation with an openwrt test device installed in a
virtual machine. From directives i can't install an
openvpn server, what is the easiest method to implement
the topology? i tried with the script

   #!/bin/sh
   
BASE_URL="https://network-topology-visualizer.mynetwork.org";
    UUID="4e38397a-4254-4521-89a6-045db25b8de6"
    KEY="S9wCfjeFN8irasZNiV7dGcyK68BTES0m"

COLLECTOR_URL="$BASE_URL/api/receive/$UUID/?key=$KEY"
    DATA=$(echo "/netjsoninfo filter graph ipv4_0" | nc
127.0.0.1 2009)
    curl -s -X POST -d "$DATA" --header "Content-Type:
text/plain" $COLLECTOR_URL

but entering my data seems not to work

-- 
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/b48c900d-29f8-4b8c-a984-68cdd41b93a1n%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/CAAGgX6KHJuE-d8qJnVXSGaZiLWjti7VeYcR66vsG88DW69Y_nA%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

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

2023-04-04 Thread Federico Capoano

This is the error: *Error: self signed certificate.*

For production usage you need a valid SSL certificate.

Best regards
Federico


On Tue, 4 Apr 2023 at 08:57, François Noah  wrote:

> hello,
> i'am trying to use openwisp-wifi-login-pages but i get zrror below
>
> [
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *ERROR 2023-04-04 13:30:39:3039] {[0]   error: Error: self signed
> certificate[0]   at TLSSocket.onConnectSecure
> (node:_tls_wrap:1530:34)[0]   at TLSSocket.emit (node:events:520:28)[0]
>   at TLSSocket.emit (node:domain:475:12)[0]   at
> TLSSocket._finishInit (node:_tls_wrap:944:8)[0]   at
> TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {[0] code:
> 'DEPTH_ZERO_SELF_SIGNED_CERT',[0] config: {[0]   transitional:
> [Object],[0]   adapter: [Function: httpAdapter],[0]
> transformRequest: [Array],[0]   transformResponse: [Array],[0]
> timeout: 2000,[0]   xsrfCookieName: 'XSRF-TOKEN',[0]
> xsrfHeaderName: 'X-XSRF-TOKEN',[0]   maxContentLength: -1,[0]
> maxBodyLength: -1,[0]   validateStatus: [Function: validateStatus],[0]
>   headers: [Object],[0]   method: 'post',[0]   url:
> 'http://api.build.lab/api/v1/radius/organization/default/account/
> ',[0]
>   data: '{"email":"t...@test.com ","username":"t...@test.com
> ","password1":"azerty","password2":"azerty"}'[0] },*
>
> registrration works when a use  api
> https://api.build.lab/api/v1/radius/organization/default/account/
>
> I want to know which certificate is used by openwisp-wifi-login-pages ? is
> it a bug ? anyone know how i can solve it ?
>
>
> --
> 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/7aaa8eed-d857-4c50-81e0-cecee6f1e4c0n%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/CAAGgX6KafVRTuVDyXktjUder2MchBQ_h0H_bto5CD1HLO2jaEQ%40mail.gmail.com.

Re: [openwisp] Aruba AP-225 / AP11

2023-04-04 Thread Federico Capoano

Look in the Table of Supported Hardware of OpenWrt
, if the devices are present you can use
them.

It seems these devices use Broadcom Radio, find out more here:
https://openwrt.org/meta/infobox/broadcom_wifi .

Federico


On Tue, 4 Apr 2023 at 10:23, pierino duemilasette 
wrote:

> HI,
> I have some Aruba AP-225 and AP11 APs. I would like to create a wi-fi
> network using both of them and manage them from a cloud console.
> Is it possible to use OpenWISP ?
>
> Ciao
>
> --
> 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/df984b51-cf6c-4225-a7fe-da0b26996bedn%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/CAAGgX6%2BGcnosj7rcxxWWqHqetEmDmhxmg%2BwcT%2BshTeBAUWZ%3DPg%40mail.gmail.com.

[openwisp] Aruba AP-225 / AP11

2023-04-04 Thread pierino duemilasette

HI,
I have some Aruba AP-225 and AP11 APs. I would like to create a wi-fi 
network using both of them and manage them from a cloud console.
Is it possible to use OpenWISP ?

Ciao

-- 
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/df984b51-cf6c-4225-a7fe-da0b26996bedn%40googlegroups.com.

Re: [openwisp] Firmware Upgrade doubts :reg

2023-04-04 Thread Federico Capoano

The default upgrader class for OpenWrt uses "sysupgrade -c", which
preserves the configurations in /etc/, which means the device will not
register again, it will simply boot with the old configuration.

Federico

On Mon, 3 Apr 2023 at 02:32, Manukumar NM  wrote:

> Greetings...
> Hi team,
>I have doubt on Openwisp2 Firmware
> Upgrade, after updating firmware from openwsip2 server. How the device will
> be re-registered to the specific Organization. I have read the
> documentation of Firmware Upgrade but I didn't understand How the device
> will re-registered after flash.
>
> Thanks in advance.
>
> --
> 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/5b8aac14-670b-4ae3-b98a-a7459ff017bfn%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/CAAGgX6LQMqdQy2oVZEAu_oyC8TnXLqddJpT5jnho_bEjDYjhXA%40mail.gmail.com.

[openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

2023-04-04 Thread François Noah

hello,
i'am trying to use openwisp-wifi-login-pages but i get zrror below 

[






















*ERROR 2023-04-04 13:30:39:3039] {[0]   error: Error: self signed 
certificate[0]   at TLSSocket.onConnectSecure 
(node:_tls_wrap:1530:34)[0]   at TLSSocket.emit (node:events:520:28)[0] 
  at TLSSocket.emit (node:domain:475:12)[0]   at 
TLSSocket._finishInit (node:_tls_wrap:944:8)[0]   at 
TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {[0] code: 
'DEPTH_ZERO_SELF_SIGNED_CERT',[0] config: {[0]   transitional: 
[Object],[0]   adapter: [Function: httpAdapter],[0]   
transformRequest: [Array],[0]   transformResponse: [Array],[0]   
timeout: 2000,[0]   xsrfCookieName: 'XSRF-TOKEN',[0]   
xsrfHeaderName: 'X-XSRF-TOKEN',[0]   maxContentLength: -1,[0]   
maxBodyLength: -1,[0]   validateStatus: [Function: validateStatus],[0] 
  headers: [Object],[0]   method: 'post',[0]   url: 
'http://api.build.lab/api/v1/radius/organization/default/account/',[0] 
  data: 
'{"email":"t...@test.com","username":"t...@test.com","password1":"azerty","password2":"azerty"}'[0]
 
},*

registrration works when a use  
api https://api.build.lab/api/v1/radius/organization/default/account/

I want to know which certificate is used by openwisp-wifi-login-pages ? is 
it a bug ? anyone know how i can solve it ?


-- 
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/7aaa8eed-d857-4c50-81e0-cecee6f1e4c0n%40googlegroups.com.

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

Re: [openwisp] Network topology

Re: [openwisp] Network topology

Re: [openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

Re: [openwisp] Aruba AP-225 / AP11

[openwisp] Aruba AP-225 / AP11

Re: [openwisp] Firmware Upgrade doubts :reg

[openwisp] DEPTH_ZERO_SELF_SIGNED_CERT error

11 matches

Site Navigation

Mail list logo

Footer information