The same happens after factory reset.
--
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, vis
Hello
I'm building a firmware with openwisp pre-installed but whenI flash the
firmware openwisp acts a bit weird right after the image is flashed. It
retieves the configuration from server a applies it but does not restart
the services so that the configuration is not really applied. It takes
Have you checked under ORGANIZATIONS > YOUR ORGANIZATION > CONFIGURATION
MANAGEMENT SETTINGS > Auto-registration enabled?
Em segunda-feira, 12 de agosto de 2019 10:51:25 UTC-3, matteo fedeli
escreveu:
>
> In the device section there isn't anyone AP... It's empty.
>
> Il giorno lunedì 12 agosto
Have you checked under ORGANIZATIONS > YOUR ORGANIZATION > CONFIGURATION
MANAGEMENT SETTINGS > Auto-registration enabled?
Em segunda-feira, 12 de agosto de 2019 10:51:25 UTC-3, matteo fedeli
escreveu:
>
> In the device section there isn't anyone AP... It's empty.
>
> Il giorno lunedì 12 agosto
Hello
Is that a previously registered device? I had some issues with that and the
soulution we came up was to delete the device from Openwisp and register
it again.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group a
I've been running around 600 TP-Link devices for the last two years, so far
they've been astonishingly reliable.
--
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 op
I think there is not an option for that, can't you just set "option
interval" in /etc/config/oepnwisp to something that will suit you?
Alternativelly you can automate that with ansible since you can access the
devices via SSH.
Ps.: In case you automate you just need to reload the service
open
Great, that worked for me.
I've been using openwisp for so long that sometimes I forget there is a
basic mode that i can use to generate the json.
Thanks!
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop re
Need to generate some configuration but I'm finding some issues. I need tot
bridge both eth0 and eth1 in a lan. As well as disable the existing wan
(eth1). Openwisp/netjsonconfig does not accept the following line:
"name": "eth0 eth1", like in:
{
"interfaces": [
{
"type
ok!
--
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.
For more options, visit https://groups.google.com/d/optout.
Ok. This json generates a file without the last two characters. This
problem happens only using the web interface not the netjsonconfig command
line.
{
"files": [
{
"contents":
"#!/bin/sh\n\npostar_arquivo_no_servidor(){\n\tTIPO=$1\n\tARQUIVO=$2\n\tlogger
\"Script Monit
Hi Federico. yes, it shows up in the preview.
I couldn't find why the problem is happening but I managed to figure out a
workaround. Since only the final characters are removed I added the same
amount of characters (white spaces) at the end of the file.
Let me know if you really want to go deep
w up in the preview? If not, what other steps can be done to
> reproduce it?
>
> Thanks
> Federico
>
>
> On Friday, November 16, 2018 at 5:49:06 PM UTC+1, henriqsc wrote:
>>
>> Hi, I'm trying to transfer a shell script to my devices but the file
>> generat
Hi, I'm trying to transfer a shell script to my devices but the file
generated by openwisp is incomplete. It's the first time it happens to me.
The json in the advanced mode is ok and the output from the command line (
netjsonconfig --config file.json --backend openwrt --method render) returns
Great work, congrats.
--
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.
For more options, visit https://groups.google.com/d/opto
Hi
any particular reason to run upgrades from the local machine as it's
suggested in the manual?
https://libraries.io/github/wanman/ansible-openwisp2
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiv
gt;
> If you make a backup and upgrade now, then you can create a new VM with a
> more recent OS (eg: ubuntu 18) and migrate the database.
> This way you won't be affected when we drop support for python 2.7.
>
> Federico
>
> On Wed, Sep 5, 2018 at 7:38 PM henriqsc > w
Hi Federico
when will it happen? I'm still using one of the first Openwisp2 versions
and Python 2.7.9 and I'm planning an upgrade.
--
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, s
Hello, that could be created a space on github for us to post a brief
description on how we've been using openwisp (use cases) if github allows
that.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving
I'm only an user of openwisp but I'll try to answer some of your questions:
1. Openwisp is pretty mature in what is supposed to do: deliver uci
configuration to openwrt devices. Because openwisp has this very specific
goal it's hard to compare it to commercial wifi solutions like Cisco's.
Those
I'm only an user f openwisp but I'll try to answer some of you questions:
1. Openwisp is pretty mature in what is supposed to do: deliver uci
configuration to openwrt devices. Because openwisp has this very specific
goal it's hard to compare it to commercial wifi solutions like Cisco's.
Those s
Traduzir mensagem para português
Well we built a 16MB image so there was plenty of space to install anything.
Only thing I can say is that a customized firmware with the shared_key
embedded for automatic registration works like a charm, even if devices are
reset they will retrieve the configur
Well we built a 16MB image so pretty much space to install anything.
Only thing I can say is that a customized firmware with the shared_key
embedded for automatic registration works like a charm, even if devices are
reset they will retrieve the configuration from openwisp2 afterwards.
--
You r
Well we built a 16MB image so pretty much space to install anything.
Only thing I can say is that a customized firmware with the shared_key
embedded for automatic registration works like a charm, even if devices are
reset they will retrieve the configuration from openwisp afterwards.
Em segund
Good news:
https://lede-project.org/#announcing_the_openwrtlede_merge
--
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.
For mor
Alright I will try something but I'm actually creating a new server and
trying to transfer the existing database (sqlite) to this new server. Just
copying the existing database to the new server works fine for
authentication and templates, but not for the Devices (aka Configurations)
section.
Hi Federico, openwisp2.
I removed the question cause I would study ansible tasks to see if there is
something that does that when it finds an existing database.
Anyway the question is that I have an older version from around march
running in production but I want to install a new one for contin
Is there a straightforward way to install a database from an older openwisp
version or should I figure out how to convert it to the new schema?
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving email
Is there a straightforward way to install a database from an older openwisp
versions or should I figure out how to convert it to the new schema?
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving email
Thats interesting. I've been using /etc/uci-defaults, openwrt will run
every script it finds inside this folder at boot time. The problem is it
needs someone to reboot the router.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from
Thats interesting. I've been using /etc/uci-defaults, openwrt will run
every script it finds inside this folder at boot time. The problem is it
needs someone to reboot the router.
Em terça-feira, 10 de outubro de 2017 14:36:31 UTC-3, Federico Capoano
escreveu:
>
> HI Saurabh,
>
> very intere
Yes, that can be a bit confusing when you start using openwisp2 and you are
not fully aware of how openwisp firmware works.
--
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 em
ederico Capoano
escreveu:
>
> Writing to the flash too often accelerates the
> "aging" of the flash memory of device (lend me the term).
>
> Applying the configuration at boot shouldnt have any side effect, are you
> noticing any downside?
>
> Federico
>
> Il me
Hello everyone!
that might not be related to the original question but it always called my
attention that the configuration file is downloaded to /temp/ where it's
lost everytime the device is rebooted forcing the device to download and
apply the configuration even if there is no actual update
Right, the following json did it for me.
{
"firewall": [
{
"config_name": "rule",
"config_value": "SSH_WAN",
"proto": "tcp",
"dest_port": "22",
"target": "ACCEPT",
"src": "wan"
}
]
}
--
You received th
{
"firewall": [
{
"config_name": "rule",
"config_value": "SSH_WAN",
"proto": "tcp",
"dest_port": "22",
"target": "ACCEPT",
"src": "wan"
}
]
}
--
You received this message because you are subscribed to
Right, the following json did it for me.
{
"firewall": [
{
"config_name": "rule",
"config_value": "Acesso_SSH_from_WAN",
"proto": "tcp",
"dest_port": "22",
"target": "ACCEPT",
"src": "wan"
}
]
}
--
Yo
Ok: https://github.com/openwisp/netjsonconfig/issues/96
But I'm not sure it's happening in newer versions since renderes.py is no
more a file, it's now renamed to renderer.py which is a much smaller file.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" g
Hi Federico
{
"ip_rules": [
{
"src":"wan",
"enabled":"1",
"proto":"tcp",
"dest_port":"22",
"target": "ACCEPT"
}
]
}
I think it's happening because I'm using an older version of netjsonconfig
where there is still a file called renderers.py which calls ip_network for
that property (src) genratin
Hello
I think the openwrt backend has a small problem related to the validation
of option "src" in the ip_rules dictionary. According to Openwrt
documentation (https://wiki.openwrt.org/doc/uci/firewall) option src is
supposed to be a zone but the backend requires the value to be an octet.
Am I
Thanks Federico, still learning how to use git, should have called you via
chat.
Em segunda-feira, 7 de agosto de 2017 14:21:02 UTC-3, Federico Capoano
escreveu:
>
> Done:
> https://github.com/openwisp/ansible-openwisp2/commit/4272db8bbe428737fdc0bb04435acf67cac0d3e7
>
--
You received this me
t;
> It would be an awesome contribution for being the first one!
>
> Federico
>
>
> On Mon, Jul 17, 2017 at 9:21 PM henriqsc > wrote:
>
>> Hi all, I actually needed to test openwrt clients. Tested it today and
>> they can register and get configurations even if they we
Hi all, I actually needed to test openwrt clients. Tested it today and they
can register and get configurations even if they were outside
openwisp2_admin_allowed_network.
Right now I'm using the following.
location /admin {
error_page 403 = 204;
try_files /opt/openwisp2/public_h
Ok, apparently adding the following lines solved the problem at least for
the console part.
location /admin {
try_files /opt/openwisp2/public_html/maintenance.html $uri @uwsgi;
allow TRUSTED_NETWORK;
deny all;
}
Unfortunatly right now I don't have a
Hi Federico, added an issue, I hope it's in the correct place, let me know
if it's not.
I will keep trying here and let you know if I have something new.
Thanks.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and s
I want to block console access only from the wan. All clients in the wan
side must reach the controller.
I thought it would be possible because the console is accessed via GET
/admin/ and the clients accesss their configurations using GET
/controller/something
I'm not sure iptables will do but
Has anyone successfully applied access restriction to the management part
of the controller (*/admin) via nginx openwisp sites-enabled file?
I've been trying to block the magement page to non-private IPs but without
much of a success. I tryed the standard location /admin {deny all; allow
privat
Hi Federico thanks for the links. I'm looking for something like:
{
"zone": [
{
"output": "ACCEPT",
"input": "REJECT",
"forward": "REJECT",
"name": "wan"
"network": "wan wan3g"
}
]
}
To get something like:
config zone 'rule_name_here'
option output 'ACCEPT'
option name 'wan'
org/pdf/netjsonconfig/0.3.7/netjsonconfig.pdf
http://nemesisdesign.net/blog/coding/netjsonconfig-convert-netjson-to-openwrt-uci/
>
> On Wednesday, April 26, 2017 at 5:20:50 PM UTC+2, henriqsc wrote:
>>
>> Hello everyone,
>>
>> I noticed that after openwisp_config service
Hello everyone,
I noticed that after openwisp_config service is run for the first time the
/etc/config/firewal is changed, all the rules and zones descriptions are
chaged, for example:
config rule
option dst_port 'xxx'
option taget 'yyy'
is changed to:
config rule 'cfg0c932bd'
opt
Ok, thanks again. I hope I can contribute in some way soon.
--
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.
For more options,
Hi Federico, yep, thanks. Since openwisp_config run as root and "etc" is
owned by root as well as "tmp" what is the problem with writing to "etc"
(in fact it's already creating the empty file)? The only difference I see
between etc and tmp is that the later has writing permissions to non-root
u
has writing permissions to non-root
users.
Regards!
Em terça-feira, 18 de abril de 2017 16:51:54 UTC-3, Federico Capoano
escreveu:
>
> Hey Henrique,
>
> if you use a different path, eg: /tmp/test, do you get a different result?
>
> F.
>
> On Tue, Apr 18, 2017 at 6:30 PM
Not sure why this is happening but when I try to include a file template to
my configuration I get the file but with no content on the other end.
Template's JASON is as follows:
{
"files": [
{
"contents": "teste",
"path": "/etc/config/teste",
"mode"
ge behaviour and you can replicate it, if you
>> could allow me to see the debugging output live with you, it would help me
>> to understand if there's something which could be improved.
>>
>> Federico
>>
>>
>> On Saturday, April 8, 2017 at 2:46:58 PM U
Thanks. Let me know if you need any extra information.
--
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.
For more options, visit
I think I caused some misunderstanding when I said test_config was not set.
I actually meant test_config was not defined in /etc/config/openwsip so
test_config was set to 1 by default.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe
day, April 7, 2017 at 10:35:36 AM UTC+2, Federico Capoano wrote:
>>
>> On Thursday, April 6, 2017 at 7:07:43 PM UTC+2, henriqsc wrote:
>>>
>>> Great. Many thanks.
>>>
>>> It applied the configuration without actualy testing it I guess because
>>&
6 de abril de 2017 13:01:32 UTC-3, Federico Capoano
escreveu:
>
> This is the relevant UCI ppoe block:
>
> On Thu, Apr 6, 2017 at 4:49 PM henriqsc > wrote:
>
>> config interface 'wan'
>> option ifname 'eth0'
>> option proto
'255.255.255.0'
option ip6assign '60'
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
Em quinta-feira, 6 de abril de
Hello
We're trying to set some devices to use pppoe but there is no such option
on the web interface, we also tryed to use the advanced JASON mode but it's
not allowed to set the protocol field as pppoe. Is there any way to
configure pppoe?
Thank you!
--
You received this message because you
Hello
We are trying to set up our routers to get the configuration from the
controller at boot time but we realised that it was not happening probably
because the wan interface was not ready to communicate to the controller
before the firmware itself starts. We tried to solve that by setting
c
Had this same Bad Request (400) issue, it was also making it impossible to
clients to register on the server.
Solved that by modifing /opt/openwisp2/openwisp2/settings.py adding the
domain part of the URL (in our case the IP address of the server) to the
line:
ALLOWED_HOSTS = ['IP_Address', '
Hello
I have some doubts about the use of the Openwisp Openwrt Firmware and how
it works with Openwisp2. I'm pretty new to it, what I have so far is an
Openwrt virtual instance with Openwisp Firmware and Openwisp2 Server
deployed via ansible in another VM.
In the architecture session of openwi
ommand line.
>
> You have to use the init.d script:
> /etc/init.d/openwisp_config start
>
> As documented in the openwisp-config README
> <https://github.com/openwisp/openwisp-config/#install-precompiled-package>
> .
>
> Anyway, glad you found out the issue.
#x27;ve installed the nossl package, pasted the config you provided and the
> deamon started successfully.
>
> I cannot reproduce your problem.
>
> Federico
>
>
> On Friday, March 24, 2017 at 4:41:40 PM UTC+1, henriqsc wrote:
>>
>> Hello Fred
>>
>>
&g
'/usr/sbin/my_pre_reload_hook'
Em sexta-feira, 24 de março de 2017 10:39:58 UTC-3, Federico Capoano
escreveu:
>
> Hi Enrique,
>
> so, I haven't understood well how to replicate your issue.
>
> You installed a precompiled package?
>
> Which one? Could you sen
gt; Hi,
>
> On Thu, Mar 23, 2017 at 9:49 PM henriqsc > wrote:
>
>> Hello I've just installed th e client openwisp-config for openwisp2 on a
>> virtual machine with openwrt for test. I followed the instructions to
>> install the nossl version of the client, everythi
Hello I've just installed th e client openwisp-config for openwisp2 on a
virtual machine with openwrt for test. I followed the instructions to
install the nossl version of the client, everything went ok until I tried
to start the client using "openwisp_config start" which returns me the
message
69 matches
Mail list logo