Re: [Freedombox-discuss] Lorawan IoT protocol

[permondes - sagen]

Yes, LoraWan is for low volume data traffic, such as sensors. Cycle
rate should be at 1% to the most, so the idea is that the sensor give
their value, including some hand-shaking, (e.g. temperature) and that's
it. In the other direction there is handshaking and occasionally
firmware upgrades for the sensors.So this technology cannot carry WLAN
traffic, to the most it could provide info about the health status of
your WLAN antennas.
Dietmar
Am Mittwoch, den 21.03.2018, 15:29 + schrieb Graham Cobb:
> On 21/03/18 13:23, s...@bristolwireless.net wrote:
> > It is an interesting tech
> 
> Indeed. But LoRaWAN is primarily a Low Power WAN (LPWAN) technology:
> the
> focus is on power saving, large number of nodes and long distance. My
> understanding is that data rates are very low (27kbps as an absolute
> maximum using the LoRa technology and much lower rates are needed if
> long distances are involved), packet sizes are normally very small
> and
> reliability can be poor (and all these trade off against each other).
> 
> So IoT and emergency messaging (both often low bandwidth) are very
> relevant use cases. Mesh networking doesn't fit well: user
> expectation
> will be for much higher data rates, and the mesh means that every
> message has to be transmitted several times, reducing effective
> capacity
> even further (LoRaWAN devices communicate with their local gateway
> which
> then normally connects onwards using conventional IP networks).
> 
> Note that TheThingsNetwork is a very interesting initiative, but it
> limits capacity even further in order to provide better "fairness"
> for a
> larger number of devices (the issue is the amount of time any single
> device is able to transmit: TTN limits it to 30s per day per device
> --
> less than 100K bytes per day).
> 
> So, an interesting technology to experiment with (I plan to do so
> when I
> get some time). But pretty limited in applications.
> 
> There is an interesting paper apparently published in IEEE
> Communications Magazine available at:
> https://arxiv.org/pdf/1607.08011.pdf
> 
> Graham
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-di
> scuss___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Error installing mediawiki

[permondes - sagen]

The issue was that there was left for some reason libapache2-mod-
php7.0, additionally to 7.2.I removed that, then enabled mbstring and
xml and got no error.So I think my installation is kind of clean
now.However, when going to mediawiki, I only see
> run();
on the browser.
Best would be to re-install mediawiki via Plinth, I think. How do I
make Plinth understand mediawiki is not installed? I could remove it
via aptitude to have a clean situation.
   Dietmar
Am Sonntag, den 18.03.2018, 13:53 +0100 schrieb permondes - sagen:
> Here is kind of solution for this: https://www.mediawiki.org/wiki/Man
> ual:Running_MediaWiki_on_Debian_or_Ubuntu
> The extensions mbstring and xml are not registered. The wiki
> recommends to run
> > sudo phpenmod mbstring
> etc. 
> 
> However, this results in an error:
> > $ sudo phpenmod mbstring
> > WARNING: Module mbstring ini file doesn't exist under
> > /etc/php/7.0/mods-available
> > WARNING: Module mbstring ini file doesn't exist under
> > /etc/php/7.0/mods-available
> > 
> Which is actually correct. The ini files are located under 7.2.
> How do I make php understand that it is running under 7.2 and not
> 7.0?
> 
> mediawiki is stretching my nerves. Am I the only one using it???
> 
>   Dietmar
> 
> Am Samstag, den 17.03.2018, 17:39 +0100 schrieb permondes - sagen:
> > There is a broken link for LocalSettings.php. The file does not
> > exist in the target directory. There is only file mediawiki.conf.
> > But I am not sure if this is related.
> > 
> > Dietmar
> > 
> > :/var/lib/mediawiki$ ls -l
> > ...
> > lrwxrwxrwx 1 root root  32 Dez  3 09:20 LocalSettings.php
> > -> /etc/mediawiki/LocalSettings.php
> > 
> > Am Samstag, den 17.03.2018, 15:12 +0100 schrieb permondes - sagen:
> > > After a restart and some messing around (cannot go into details,
> > > just tried to clean up old config files and undid this
> > > afterwards), the app is installing.
> > > But now I get an error message running mediawiki: 
> > > > MediaWiki 1.27 internal error   
> > > > Installing some PHP extensions is required. 
> > > > 
> > > > Required components 
> > > > You are missing a required extension to
> > > > PHP that MediaWiki  requires to run. Please
> > > > install:
> > > > mbstring (more">https://secure.php.net/mbstring
> > > > ">more information)xml (more information)   
> > > 
> > > But both are installed:
> > > > :~$ apt list php-xml php-mbstring
> > > > Auflistung... Fertig
> > > > php-mbstring/stable,stable 1:7.0+49 all
> > > > php-xml/stable,stable 1:7.0+49 all
> > > 
> > > According to aptitude all dependencies are installed.
> > > 
> > > A restart did not change the situation this time. What is
> > > missing?
> > > 
> > >   Dietmar
> > > Am Samstag, den 17.03.2018, 10:19 +0100 schrieb permondes -
> > > sagen:
> > > > Hi,
> > > > 
> > > > I received the following error when trying to install
> > > > mediawiki. I am on Plinth 0.24 (testing). Downloading worked,
> > > > the error appeared versus the end of the installation process.
> > > > 
> > > > > [2018-03-17 09:55:30,199] plinth.actions INFO Executing
> > > > > command - ['sudo', '-n',
> > > > > '/usr/share/plinth/actions/packages', 'is-package-manager-
> > > > > busy']
> > > > > [2018-03-17 09:55:32,773] plinth.setup   ERRORError
> > > > > running setup - PackageException(error_string="Error during
> > > > > installation", error_details="E: Sub-process /usr/bin/dpkg
> > > > > returned an error code (1)
> > > > > ")
> > > > > Traceback (most recent call last):
> > > > >   File "/usr/lib/python3/dist-packages/plinth/setup.py", line
> > > > > 88, in run
> > > > > self.module.setup(self, old_version=current_version)
> > > > >   File "/usr/lib/python3/dist-
> > > > > packages/plinth/modules/mediawiki/__init__.py", line 76, in
> > > > > setup
> > > > > helper.install(managed_packages)
> > > > >   File "/usr/lib/python3/dist-packages/plinth/setup.py", line
> > > > &

Re: [Freedombox-discuss] Error installing mediawiki

[permondes - sagen]

Here is kind of solution for this: https://www.mediawiki.org/wiki/Manua
l:Running_MediaWiki_on_Debian_or_UbuntuThe extensions mbstring and xml
are not registered. The wiki recommends to run
> sudo phpenmod mbstring
etc. 
However, this results in an error:
> $ sudo phpenmod mbstring
> WARNING: Module mbstring ini file doesn't exist under
> /etc/php/7.0/mods-available
> WARNING: Module mbstring ini file doesn't exist under
> /etc/php/7.0/mods-available
> 
Which is actually correct. The ini files are located under 7.2.How do I
make php understand that it is running under 7.2 and not 7.0?
mediawiki is stretching my nerves. Am I the only one using it???
Dietmar
Am Samstag, den 17.03.2018, 17:39 +0100 schrieb permondes - sagen:
> There is a broken link for LocalSettings.php. The file does not exist
> in the target directory. There is only file mediawiki.conf.
> But I am not sure if this is related.
> 
>   Dietmar
> 
> :/var/lib/mediawiki$ ls -l
> ...
> lrwxrwxrwx 1 root root  32 Dez  3 09:20 LocalSettings.php ->
> /etc/mediawiki/LocalSettings.php
> 
> Am Samstag, den 17.03.2018, 15:12 +0100 schrieb permondes - sagen:
> > After a restart and some messing around (cannot go into details,
> > just tried to clean up old config files and undid this afterwards),
> > the app is installing.
> > But now I get an error message running mediawiki: 
> > > MediaWiki 1.27 internal error 
> > >   Installing some PHP extensions is required. 
> > >   Required components 
> > >   You are missing a required extension to PHP that
> > > MediaWiki requires to run. Please install:
> > >   mbstring (more">https://secure.php.net/mbstring;>more
> > > information)xml (more information)
> > 
> > But both are installed:
> > > :~$ apt list php-xml php-mbstring
> > > Auflistung... Fertig
> > > php-mbstring/stable,stable 1:7.0+49 all
> > > php-xml/stable,stable 1:7.0+49 all
> > 
> > According to aptitude all dependencies are installed.
> > 
> > A restart did not change the situation this time. What is missing?
> > 
> > Dietmar
> > Am Samstag, den 17.03.2018, 10:19 +0100 schrieb permondes - sagen:
> > > Hi,
> > > 
> > > I received the following error when trying to install mediawiki.
> > > I am on Plinth 0.24 (testing). Downloading worked, the error
> > > appeared versus the end of the installation process.
> > > 
> > > > [2018-03-17 09:55:30,199] plinth.actions INFO Executing
> > > > command - ['sudo', '-n', '/usr/share/plinth/actions/packages',
> > > > 'is-package-manager-busy']
> > > > [2018-03-17 09:55:32,773] plinth.setup   ERRORError running
> > > > setup - PackageException(error_string="Error during
> > > > installation", error_details="E: Sub-process /usr/bin/dpkg
> > > > returned an error code (1)
> > > > ")
> > > > Traceback (most recent call last):
> > > >   File "/usr/lib/python3/dist-packages/plinth/setup.py", line
> > > > 88, in run
> > > > self.module.setup(self, old_version=current_version)
> > > >   File "/usr/lib/python3/dist-
> > > > packages/plinth/modules/mediawiki/__init__.py", line 76, in
> > > > setup
> > > > helper.install(managed_packages)
> > > >   File "/usr/lib/python3/dist-packages/plinth/setup.py", line
> > > > 122, in install
> > > > transaction.install()
> > > >   File "/usr/lib/python3/dist-packages/plinth/package.py", line
> > > > 83, in install
> > > > self.package_names)
> > > >   File "/usr/lib/python3/dist-packages/plinth/package.py", line
> > > > 107, in _run_apt_command
> > > > raise PackageException(_('Error during installation'),
> > > > self.stderr)
> > > > plinth.package.PackageException:
> > > > PackageException(error_string="Error during installation",
> > > > error_details="E: Sub-process /usr/bin/dpkg returned an error
> > > > code (1)
> > > > ")
> > > > [2018-03-17 09:56:00,309] plinth.actions INFO Executing
> > > > command - ['sudo', '-n', '/usr/share/plinth/actions/packages',
> > > > 'is-package-manager-busy']
> > > 
> > > The last info in /var/log/dpkg.log is:
>

[Freedombox-discuss] Error installing mediawiki

[permondes - sagen]

Hi,

I received the following error when trying to install mediawiki. I am
on Plinth 0.24 (testing). Downloading worked, the error appeared versus
the end of the installation process.

> [2018-03-17 09:55:30,199] plinth.actions INFO Executing command -
> ['sudo', '-n', '/usr/share/plinth/actions/packages', 'is-package-
> manager-busy']
> [2018-03-17 09:55:32,773] plinth.setup   ERRORError running setup
> - PackageException(error_string="Error during installation",
> error_details="E: Sub-process /usr/bin/dpkg returned an error code
> (1)
> ")
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/plinth/setup.py", line 88, in
> run
> self.module.setup(self, old_version=current_version)
>   File "/usr/lib/python3/dist-
> packages/plinth/modules/mediawiki/__init__.py", line 76, in setup
> helper.install(managed_packages)
>   File "/usr/lib/python3/dist-packages/plinth/setup.py", line 122, in
> install
> transaction.install()
>   File "/usr/lib/python3/dist-packages/plinth/package.py", line 83,
> in install
> self.package_names)
>   File "/usr/lib/python3/dist-packages/plinth/package.py", line 107,
> in _run_apt_command
> raise PackageException(_('Error during installation'),
> self.stderr)
> plinth.package.PackageException: PackageException(error_string="Error
> during installation", error_details="E: Sub-process /usr/bin/dpkg
> returned an error code (1)
> ")
> [2018-03-17 09:56:00,309] plinth.actions INFO Executing command -
> ['sudo', '-n', '/usr/share/plinth/actions/packages', 'is-package-
> manager-busy']

The last info in /var/log/dpkg.log is:
> 2018-03-17 09:55:20 startup packages configure
> 2018-03-17 09:55:20 configure mariadb-server-10.1:armhf 1:10.1.29-6
> 
> 2018-03-17 09:55:20 status half-configured mariadb-server-10.1:armhf
> 1:10.1.29-6

Then 12s later it crashes.

In aptitude I find that 2 packages are partly installed:
- default-mysql-server: u (unpacked)
- mariadb-server-10.1: C (half configured)

Giving it a GO in aptitude gives this log:

> Performing actions...
> mariadb-server-10.1 (1:10.1.29-6) wird eingerichtet ...
> dpkg: Fehler beim Bearbeiten des Paketes mariadb-server-10.1 (
> --configure):
>  installed mariadb-server-10.1 package post-installation script
> subprocess returned error exit status 1
> dpkg: Abhängigkeitsprobleme verhindern Konfiguration von default-
> mysql-server:
>  default-mysql-server hängt ab von mariadb-server-10.1; aber:
>   Paket mariadb-server-10.1 ist noch nicht konfiguriert.
> 
> dpkg: Fehler beim Bearbeiten des Paketes default-mysql-server (
> --configure):
>  Abhängigkeitsprobleme - verbleibt unkonfiguriert
> Fehler traten auf beim Bearbeiten von:
>  mariadb-server-10.1
>  default-mysql-server
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> mariadb-server-10.1 (1:10.1.29-6) wird eingerichtet ...
> dpkg: Fehler beim Bearbeiten des Paketes mariadb-server-10.1 (
> --configure):
>  installed mariadb-server-10.1 package post-installation script
> subprocess returned error exit status 1
> dpkg: Abhängigkeitsprobleme verhindern Konfiguration von default-
> mysql-server:
>  default-mysql-server hängt ab von mariadb-server-10.1; aber:
>   Paket mariadb-server-10.1 ist noch nicht konfiguriert.
> 
> dpkg: Fehler beim Bearbeiten des Paketes default-mysql-server (
> --configure):
>  Abhängigkeitsprobleme - verbleibt unkonfiguriert
> Fehler traten auf beim Bearbeiten von:
>  mariadb-server-10.1
>  default-mysql-server
> Press Return to continue, 'q' followed by Return to quit.
> 

Something inhibits mariadb to be configured. Any ideas?

Dietmar
-- ___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] Our wikis: ikiwiki, mediawiki

[permondes - sagen]

With version 0.20 we have 2 wikis in Freedombox: ikiwiki and mediawiki.
I think we should provide guidance to our users which one to use when.
I made myself familiar with ikiwiki (running a homepage on it now) and
I know mediawiki from Wikipedia. 

So I'd like to collect material for our manual. Wikipedia could be a
starting point, (https://en.wikipedia.org/wiki/Comparison_of_wiki_softw
are ) has some info but it looks not so complete, e.g. ikiwiki is only
rarely mentioned. 

So to start the collection, what was the reasoning to include both?
What target audience are they for? Who should use which? Or is it just
the syntax? 

Once sufficient material is available, I am thinking of putting a page
"Wiki / Homepage" into the manual that re-directs to ikiwiki and
mediawiki. That page would contain this guidance.

Dietmar___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Personal Web Server

[permondes - sagen]

Hi Joseph,
Am Donnerstag, den 07.12.2017, 11:22 +0530 schrieb Joseph Nuthalapati:
> Adding to Daddy's reply.
> 
> 
> 
> We have plans for including a blog application with FreedomBox,
> but
> if you want to host a website, you can simply host it from Apache
> by
> adding the files in /var/www/html.
> 
> 
> 
> FreedomBox serves Plinth by default. This configuration is in
> /etc/apache2/conf-available/freedombox.conf. Delete the following
> line from the file and Apache will serve your website files
> instead.
> You can still access Plinth from /plinth.
> 
> 
> 
> RedirectMatch "^/$" "/plinth"

Thanks for working out this solution.If there is an update e.g. of
apache, will this cause a debconf prompt? Those are always an issue
with unattended upgrades.
By the way, I am currently using ikiwiki to generate my homepage.
   Dietmar___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] SMB File Share

[sagen]

Am 30. November 2017 18:06:11 MEZ schrieb Josh Blagden :
>Is it possible to use a Freedombox as a file share? For example, for
>hosting movies and TV shows for in-house streaming?
>
>
>
>Josh

Check out syncthing.
It does not share but rather synchronize between devices.

Dietmar

___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Connect Freedombox to Router

[permondes - sagen]

Hi Josh,
Am Mittwoch, den 29.11.2017, 13:09 -0500 schrieb Josh Blagden:
> Hi guys,
> 
> I just joined the mailing list. I'm
> interested in setting up a Freedombox, but I'm afraid that
> its
> range may be insufficient and I also prefer wired Internet
> connections better than wireless. Is it possible to connect a
> Freedombox to router so you can get better range and
> connectivity than what you could get with either an SBC's
> internal wireless card or an external USB one? If it is, is
> it
> possible to do that in a way in which you can still have
> gigabit
> speeds when using a wired connection?
> 
> 
> 
>   
> 
> 
> 
>   
> 
> Josh

the usual connection is actually to connect the Freedombox via cable to
the router (NAT). It then just depends on the network card of your
hardware, how fast the communication will go. You then can connect your
PC etc. via WLAN or cable to that router and give them local or
internet access to the box. The optional WLAN connection of the
Freedombox e.g. via USB stick can serve as WLAN access point, e.g. if
your router does not have that option.Also have a look at our wiki: htt
ps://wiki.debian.org/FreedomBox/Introduction
Dietmar
>   
> 
>   
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-di
> scuss___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Creating LDAP user failed.

[permondes - sagen]

Am Mittwoch, den 22.11.2017, 22:10 +0100 schrieb permondes - sagen:
> Am Mittwoch, den 22.11.2017, 21:51 +0100 schrieb permondes - sagen:
> > Am Mittwoch, den 22.11.2017, 20:57 +0100 schrieb permondes - sagen:
> > > Hi,
> > > 
> > > creating a User in Plinth 0.16 gives this feedback:
> > > * Creating LDAP user failed.
> > > * User hahaha created.
> > > 
> > > Changing the password afterwards fails the LDAP operation but
> > > works successful (as 2nd message).
> > > 
> > > Issue is, that I am trying to set up another user for a radicale
> > > calendar. Trying to create the calendar in Evolution or DAVDroid
> > > gives an authentication error, so I presume it is related to the
> > > LDAP error. Is this right?
> > > 
> > > I have the feeling I had this issue before and managed to resolve
> > > it with the list, but cannot find any trace how I did this.
> > > 
> > >   Dietmar
> > 
> > If I assign groups to the user, there are additional error
> > messages:
> > * Failed to add new user to admin group.
> > 
> > * Failed to add new user to wiki group.
> >   
> > ___
> 
> I just found the log file  plith/status.log:
> > [2017-11-22 22:03:52,123] plinth.actions INFO Executing command
> > - ['sudo', '-n', '/usr/share/plinth/actions/users', 'create-user',
> > 'newuser']
> > [2017-11-22 22:03:54,620] plinth.actions ERRORError executing
> > command - ['sudo', '-n', '/usr/share/plinth/actions/users',
> > 'create-user', 'newuser'], , Traceback (most recent call last):
> >   File "/usr/share/plinth/actions/users", line 371, in 
> > main()
> >   File "/usr/share/plinth/actions/users", line 367, in main
> > subcommand_method(arguments)
> >   File "/usr/share/plinth/actions/users", line 225, in
> > subcommand_create_user
> > _run(['ldapadduser', arguments.username, 'users'])
> >   File "/usr/share/plinth/actions/users", line 357, in _run
> > return subprocess.run(arguments, **kwargs)
> >   File "/usr/lib/python3.6/subprocess.py", line 418, in run
> > output=stdout, stderr=stderr)
> > subprocess.CalledProcessError: Command '['ldapadduser', 'newuser',
> > 'users']' returned non-zero exit status 1.
> 
> and in ldapscripts.log:
> > Nov 22 22:03:53 freedombox ldapscripts: ldapadduser(root):
> > /usr/sbin/ldapadduser newuser users
> > SASL/EXTERNAL authentication started
> > SASL username:
> > gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
> > SASL SSF: 0
> > No such object (32)
> > Matched DN: dc=thisbox
> > SASL/EXTERNAL authentication started
> > SASL username:
> > gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
> > SASL SSF: 0
> > SASL/EXTERNAL authentication started
> > SASL username:
> > gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
> > SASL SSF: 0
> > ldap_add: No such object (32)
> > matched DN: dc=thisbox
> >   -> Error adding user newuser to LDAP
> 
> So the error is "No such object"
> On the web I found the answer: "You need to add an entry for
> dc=nerdbot,dc=net. You are trying to add
> branches to a tree with no root."
> So my configuration file is broken. How can I fix
> this?___

I discovered in /etc/ldapscripts 2 configuration files. I guess, the
one .dpkg-old was saved when an update overwrote the config file. Here
is the diff:

> xxx:/etc/ldapscripts$ diff ldapscripts.conf ldapscripts.conf.dpkg-old
> 2c2
> < #  Copyright (C) 2006-2017 Gana�l LAPLANCHE
> ---
> > #  Copyright (C) 2006-2016 Gana�l LAPLANCHE
> 90c90
> < PASSWORDGEN="pwgen"
> ---
> > PASSWORDGEN="true"
> 164a165,169
> > SERVER="ldapi://"
> > SASLAUTH="EXTERNAL"
> > SUFFIX="dc=thisbox"
> > USUFFIX="ou=Users"
> > GSUFFIX="ou=Groups"
> 
So the differences are in "PASSWORDGEN" and SERVER and the SUFFIXes.
Are the old settings Freedombox specific? Should I just copy the old
version over the new one?

Dietmar___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Creating LDAP user failed.

[permondes - sagen]

Am Mittwoch, den 22.11.2017, 21:51 +0100 schrieb permondes - sagen:
> Am Mittwoch, den 22.11.2017, 20:57 +0100 schrieb permondes - sagen:
> > Hi,
> > 
> > creating a User in Plinth 0.16 gives this feedback:
> > * Creating LDAP user failed.
> > * User hahaha created.
> > 
> > Changing the password afterwards fails the LDAP operation but works
> > successful (as 2nd message).
> > 
> > Issue is, that I am trying to set up another user for a radicale
> > calendar. Trying to create the calendar in Evolution or DAVDroid
> > gives an authentication error, so I presume it is related to the
> > LDAP error. Is this right?
> > 
> > I have the feeling I had this issue before and managed to resolve
> > it with the list, but cannot find any trace how I did this.
> > 
> > Dietmar
> 
> If I assign groups to the user, there are additional error messages:
> * Failed to add new user to admin group.
> 
> * Failed to add new user to wiki group.
>   
> ___

I just found the log file  plith/status.log:
> [2017-11-22 22:03:52,123] plinth.actions INFO Executing command -
> ['sudo', '-n', '/usr/share/plinth/actions/users', 'create-user',
> 'newuser']
> [2017-11-22 22:03:54,620] plinth.actions ERRORError executing
> command - ['sudo', '-n', '/usr/share/plinth/actions/users', 'create-
> user', 'newuser'], , Traceback (most recent call last):
>   File "/usr/share/plinth/actions/users", line 371, in 
> main()
>   File "/usr/share/plinth/actions/users", line 367, in main
> subcommand_method(arguments)
>   File "/usr/share/plinth/actions/users", line 225, in
> subcommand_create_user
> _run(['ldapadduser', arguments.username, 'users'])
>   File "/usr/share/plinth/actions/users", line 357, in _run
> return subprocess.run(arguments, **kwargs)
>   File "/usr/lib/python3.6/subprocess.py", line 418, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command '['ldapadduser', 'newuser',
> 'users']' returned non-zero exit status 1.

and in ldapscripts.log:
> Nov 22 22:03:53 freedombox ldapscripts: ldapadduser(root):
> /usr/sbin/ldapadduser newuser users
> SASL/EXTERNAL authentication started
> SASL username:
> gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
> SASL SSF: 0
> No such object (32)
> Matched DN: dc=thisbox
> SASL/EXTERNAL authentication started
> SASL username:
> gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
> SASL SSF: 0
> SASL/EXTERNAL authentication started
> SASL username:
> gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
> SASL SSF: 0
> ldap_add: No such object (32)
>   matched DN: dc=thisbox
>   -> Error adding user newuser to LDAP

So the error is "No such object"
On the web I found the answer: "You need to add an entry for
dc=nerdbot,dc=net. You are trying to add
branches to a tree with no root."
So my configuration file is broken. How can I fix this?___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] Creating LDAP user failed.

[permondes - sagen]

Hi,

creating a User in Plinth 0.16 gives this feedback:
* Creating LDAP user failed.
* User hahaha created.

Changing the password afterwards fails the LDAP operation but works
successful (as 2nd message).

Issue is, that I am trying to set up another user for a radicale
calendar. Trying to create the calendar in Evolution or DAVDroid gives
an authentication error, so I presume it is related to the LDAP error.
Is this right?

I have the feeling I had this issue before and managed to resolve it
with the list, but cannot find any trace how I did this.

Dietmar___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] Disks: Error expanding partition

[permondes - sagen]

So I am setting up the box again. 1st step is to expand the 4 GB
partition to cover the entire 32 GB card. However, as the error
correctly says, the partition is being used: by Plinth from which I
started the DISKS command, I assume:

> Error expanding partition: ('disks', '', "Warning:
> Partition /dev/mmcblk0p2 is being used. Are you sure you want to
> continue?\nError expanding partition: Command '['parted',
> '--align=optimal', '--script', '/dev/mmcblk0', 'unit', 'B',
> 'resizepart', '2', '31914983423']' returned non-zero exit status 1
> \n") 
> 

Dietmar


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] New images available for testing

[permondes - sagen]

Am Dienstag, den 07.02.2017, 17:35 +0100 schrieb sa...@permondes.de:
> Mmh, I will try again end of the week.
> 
> I understood the initial set up is a 2 step process. Can I check if it
> did the first step before the reboot?
> How long did it take for you before you saw the device in the network?
> 
> Dietmar
> 
> Am 7. Februar 2017 13:58:06 MEZ schrieb James Valleroy
> <jvalle...@mailbox.org>:
>     On 02/05/2017 11:55 AM, permondes - sagen wrote:
>  
>  I just tried the LIME image, it did _not_ boot.
>   Dietmar
> 
> Lime2 is working for me though.
> 
> BTW does the LIME show any indication of failed boot, like a blinking 
> LED?
> 
> --
> James
> 
Oh sh
It was the µSD card. I bought a new one, from one of the big names, no
no-name, and it just booted!
Such a stupid issue, how can a µSD card resist to boot??? That one goes
into the recycle bin. 
- Okay, I am happy to confirm that the LIME image is working, if issues
arise, I will report them. If not, I will make screen-shots when I am
setting up my new box and update the wiki.
Thanks to all who helped me going through this!

Dietmar 
(still biting his own back - bad translation of a German expression)


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] New images available for testing

[permondes - sagen]

Am Dienstag, den 07.02.2017, 19:15 -0500 schrieb James Valleroy:

> On 02/07/2017 11:35 AM, sa...@permondes.de wrote:
> > Mmh, I will try again end of the week.
> > 
> > I understood the initial set up is a 2 step process. Can I check if it
> > did the first step before the reboot?
> > How long did it take for you before you saw the device in the network?
> > 
> > Dietmar
> 
> Yes, during first boot it should write to /var/log/freedombox-first-run.log.
> 
> I didn't check how long it took. I just plugged it in and then check it
> about 20 minutes later. (But I expect it shouldn't take more than 5
> minutes.)
> 
> --
> James


I wrote the image again to the µSD card, inserted it in the LIME and
booted it up. Then I waited for about 50 minutes. I still could not
access it, nor did it appear in nmap or in the router.

In var/log/ I have these files:

> -rw-r--r-- 1 rootroot  11433 Feb  3 05:06 alternatives.log
> drwxr-x--- 1 rootadm  84 Feb  3 05:06 apache2
> drwxr-xr-x 1 rootroot 60 Feb  3 05:08 apt
> -rw-r--r-- 1 rootroot  51860 Feb  3 05:00 bootstrap.log
> -rw--- 1 rootutmp  0 Feb  3 04:49 btmp
> -rw-r--r-- 1 rootroot 294279 Feb  3 05:08 dpkg.log
> -rw-r--r-- 1 rootroot  24024 Feb  3 05:08 faillog
> -rw-r--r-- 1 rootroot   8651 Feb  3 05:09 freedombox-setup.log
> -rw-r--r-- 1 rootroot  16056 Feb  3 05:08 hardware-setup.log
> -rw-rw-r-- 1 rootutmp 292292 Feb  3 05:08 lastlog
> drwxr-xr-x 1 Debian-exim ssl-cert  0 Jan 28 12:58 ntpstats
> drwxr-xr-x 1 saned   avahi40 Feb  3 05:09 plinth
> drwxr-x--- 1 rootadm   0 Dez 11 11:31 unattended-upgrades
> -rw-rw-r-- 1 rootutmp384 Nov  3 18:18 wtmp


As LIME2 and LIME are the same architecture, I am not sure what goes
wrong on my setup. 

In freedombox-setup.log (no reedombox-first-run.log) ends with

> FreedomBox setup completed
> 

If there are no ideas, I would try the LIME2 image.

Dietmar
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] New images available for testing

[sagen]

Mmh, I will try again end of the week.

I understood the initial set up is a 2 step process. Can I check if it did the 
first step before the reboot?
How long did it take for you before you saw the device in the network?

Dietmar

Am 7. Februar 2017 13:58:06 MEZ schrieb James Valleroy <jvalle...@mailbox.org>:
>On 02/05/2017 11:55 AM, permondes - sagen wrote:
>> 
>> I just tried the LIME image, it did _not_ boot.
>>  Dietmar
>
>Lime2 is working for me though.
>
>BTW does the LIME show any indication of failed boot, like a blinking
>LED?
>
>--
>James
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] New images available for testing

[permondes - sagen]

Am Freitag, den 03.02.2017, 17:33 -0500 schrieb James Valleroy:
> Hello,
> 
> I have uploaded new images based on Debian testing for all targets
> supported by freedom-maker:
> 
> ftp://ftp.freedombox.org/pub/freedombox/testing-20170202/
> 
> Please help in testing these images.
> 
> Some pages on the wiki that should be helpful for installing and testing:
> 
> https://wiki.debian.org/FreedomBox/Download
> https://wiki.debian.org/FreedomBox/Manual/QuickStart
> https://wiki.debian.org/FreedomBox/QualityAssurance
> 
> --
> James

I just tried the LIME image, it did _not_ boot.
Dietmar

> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Can't get android phone to connect to radicale.

[permondes - sagen]

Am Samstag, den 04.02.2017, 21:11 -0500 schrieb A. F. Cano:
> On Sat, Feb 04, 2017 at 02:30:58PM -0500, James Valleroy wrote:
> > On 02/04/2017 01:52 PM, A. F. Cano wrote:
> > > === Android log 
> > >...
> > > 2017-01-28 20:33:55 2 [ui.setup.DavResourceFinder] Checking user-given 
> > > URL: https://192.168.1.27/radicale//
> > > 2017-01-28 20:33:55 2 [HttpClient$1] --> PROPFIND 
> > > https://192.168.1.27/radicale// http/1.1
> > > ...
> > > This is what Davdroid says:
> > > 
> > > Configuration detection
> > > 
> > > Couldn't find CalDAV or CardDAV service.
> > 
> > There shouldn't be any changes needed for the firewall.
> 
> Keep in mind that this is the firewall that's on the phone.
> 
> > What are you using for the Base URL in Davdroid? I just tried
> 
> The one above:  https://192.168.1.27/radicale//
> 
> > https:// and that worked.
> 
> I just tried that (with and without trailing /).  It didn't work.
> Also tried:
> 
> https:///radicale (with and without trailing /)
> https:///radicale/ (with and without trailing /)
> https://.freedombox.rocks (with and without trailing /)
> https://.freedombox.rocks/radicale (with and without trailing /)
> 
> The ones with freedombox.rocks took longer to return the error, so I'm
> wondering if those requests went out on the internet (or the tor
> network - orbot is running on the phone, but tor is not activated on
> the freedombox).  In any case, they all failed.
> 
> > James
> 
> Thanks for replying.  I'm not too familiar with Android and compared to
> the tools I have with linux, it's quite cumbersome to debug.  Any other
> suggestions? Anyone?
> 
> Augustine

On my Android phone with DAVDroid (actually also in Evolution), I have
to add the calendar-name, the link looks like:

https://192.168.1.27/radicale///

The trailing / was mandatory, it did not work without.

   Dietmar
> 
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Upcoming calls

[permondes - sagen]

Am Samstag, den 14.01.2017, 11:36 -0500 schrieb James Valleroy:
> On 01/13/2017 07:53 AM, James Valleroy wrote:
> > Just a reminder of upcoming calls:
> > - Hack call is tomorrow, Jan. 14, at 14;00 UTC.
> > - Progress call is Jan. 22 at 18:00 UTC.
> >
> > Please add any agenda items to the list:
> > https://wiki.debian.org/FreedomBox/ProgressCalls#A.23_Next_Calls
> >
> 
> Here are the notes from today's call:
> https://wiki.debian.org/FreedomBox/ProgressCalls/2017-01-14
> 
> One action item for everyone:
> 
> In the next progress call (next Sunday), we want to put together a
> roadmap/goals for the project for the next 3 months. The reason is that,
> starting soon, there will be several people (including Sunil) able to
> work full-time on FreedomBox. So please bring your ideas!
> 
> --
> James

I am not sure if I will be back in time for the call,  so here are my
thoughts for the roadmap:
- stability
- fully maintaining the FreedomBox without any access to the command
line - never
- we should have alternatives to the big "social media", so things the
non-nerd-user of today uses: e.g. Facebook-alternative Diaspora,
Twitter-alternative (not sure if we already have it, I do not use it),
Instagramm-alternative, Cloud, any ideas to substitute LinkedIn or Xing?
- nice to haves: Web browser Bookmarks (Shaarli, not in Debian any
more?), mesh networks (ideally meshing up with Freifunk and equivalents)

Dietmar
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] LIME does not boot, was: boot partition full

[permondes - sagen]

Am Sonntag, den 08.01.2017, 09:17 +0100 schrieb permondes - sagen:
> Am Samstag, den 07.01.2017, 23:12 +0100 schrieb Jonas Smedegaard: 
> > Quoting permondes - sagen (2017-01-07 21:43:59)
> > > Am Samstag, den 07.01.2017, 15:01 -0500 schrieb James Valleroy:
> > > 
> > > > On 01/07/2017 09:21 AM, permondes - sagen wrote:
> > > > > The currently running boot.scr with kernel 4.3:
> > > > >
> > > > >> ...:/boot$ cat boot.scr
> > > > >> ...
> > > > 
> > > > Maybe this will work, as a temporary workaround:
> > > > 
> > > > Take the old boot.cmd (for kernel 4.3) and update it for kernel 4.8
> > > > (just change the kernel_file and initrd_file to match the files in
> > > > /boot). Then you can produce a new boot.scr with the following:
> > > > 
> > > > mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
> > > > 
> > > > We used to do this in freedom-maker, but we switched (last March) to 
> > > > using flash-kernel to set up the boot script.
> > > 
> > > Wonderful, James, I am in and on kernel 4.8.0-2. Now, to switch to using
> > > flash-kernel, should I reconfig this kernel? The system will do so with
> > > the next update anyway, I guess.
> > ...

So I discussed this on the flash-kernel bug list, bug# 851469.
We were not able to put u-boot in a state that allows the LIME box to
boot. I am currently using the old boot.scr script generated by the
mkimage above.
One last proposal was to find a /etc/fw_env.config file to configure the
environmental variables freshly. This file is missing on my box. Does
anyone have one for this system?
But I am actually now preferring to set up a new device. For this a new
live image with version 0.12 is needed. I already tried a fresh set-up
with version 0.9, which was upgraded during install to 0.12, and came
across the same issue. So everyone, who is trying to use the LIME live
image 0.9 (not sure if it is also valid for LIME2) would now run into
this issue. Therefore I would appreciate if someone could generate this
new live image. No rush, as I have a work around thanks to James, and I
do not have too much time to spend on it for the moment either.

Dietmar


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Samstag, den 07.01.2017, 23:12 +0100 schrieb Jonas Smedegaard:

> Quoting permondes - sagen (2017-01-07 21:43:59)
> > Am Samstag, den 07.01.2017, 15:01 -0500 schrieb James Valleroy:
> > 
> > > On 01/07/2017 09:21 AM, permondes - sagen wrote:
> > > > The currently running boot.scr with kernel 4.3:
> > > >
> > > >> ...:/boot$ cat boot.scr
> > > >> 'V=�ѠV����#�Bi�setenv mmcdev 0
> > > >> setenv mmcpart 1
> > > >>
> > > >> setenv mmcroot /dev/mmcblk0p2 ro
> > > >> setenv mmcrootfstype btrfs rootwait fixrtc
> > > >> setenv mmcrootflags subvol=@
> > > >>
> > > >> setenv console ttyS0,115200n8
> > > >>
> > > >> setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae
> > > >> setenv initrd_file initrd.img-4.3.0-1-armmp-lpae
> > > >> setenv fdtfile sun7i-a20-olinuxino-lime.dtb
> > > >>
> > > >> setenv loadaddr 0x4600
> > > >> setenv initrd_addr 0x4800
> > > >> setenv fdtaddr 0x4700
> > > >>
> > > >> setenv initrd_high 0x
> > > >> setenv fdt_high 0x
> > > >>
> > > >> setenv loadkernel load mmc ${mmcdev}:${mmcpart} ${loadaddr} 
> > > >> ${kernel_file}
> > > >> setenv loadinitrd load mmc ${mmcdev}:${mmcpart} ${initrd_addr} 
> > > >> ${initrd_file}\; setenv initrd_size \${filesize}
> > > >> setenv loadfdt load mmc ${mmcdev}:${mmcpart} ${fdtaddr} 
> > > >> /dtbs/${fdtfile}
> > > >>
> > > >> setenv loadfiles run loadkernel\; run loadinitrd\; run loadfdt
> > > >> setenv mmcargs setenv bootargs console=${console} root=${mmcroot} 
> > > >> rootfstype=${mmcrootfstype} rootflags=${mmcrootflags}
> > > >>
> > > >> run loadfiles; run mmcargs; bootz ${loadaddr} 
> > > >> ${initrd_addr}:${initrd_size} ${fdtaddr}
> > > >
> > > 
> > > Maybe this will work, as a temporary workaround:
> > > 
> > > Take the old boot.cmd (for kernel 4.3) and update it for kernel 4.8
> > > (just change the kernel_file and initrd_file to match the files in
> > > /boot). Then you can produce a new boot.scr with the following:
> > > 
> > > mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
> > > 
> > > We used to do this in freedom-maker, but we switched (last March) to 
> > > using flash-kernel to set up the boot script.
> > 
> > Wonderful, James, I am in and on kernel 4.8.0-2. Now, to switch to using
> > flash-kernel, should I reconfig this kernel? The system will do so with
> > the next update anyway, I guess.
> 
> If the dpkg-reconfigure command works then I doubt that next package 
> update will be any better.
> 
> 
> > Also, I would like to remove the 4.3.0 and the 4.8.0-1 stuff. It does
> > not appear in aptitude. I'd like to have more free space on /boot, just
> > to be safe.
> 
> Now that 4.8.0-2 boots (even if using manual hack) you can safely remove 
> 4.8.0-1 and 4.3.0.

My /boot is clean now, I will later-on give the reconfig of linux-image
another trial. If that should cause the same issue again, I will put
this aside for the moment and rather work on my LDAP issue.
But now it's time to enjoy the hot temperatures (rose to -2 °C from -10)
and the heavy snow we had last night.

> 
> 
>  - Jonas
> 

Have a nice week-end
Dietmar
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Samstag, den 07.01.2017, 15:01 -0500 schrieb James Valleroy:

> On 01/07/2017 09:21 AM, permondes - sagen wrote:
> > The currently running boot.scr with kernel 4.3:
> >
> >> ...:/boot$ cat boot.scr
> >> 'V=�ѠV����#�Bi�setenv mmcdev 0
> >> setenv mmcpart 1
> >>
> >> setenv mmcroot /dev/mmcblk0p2 ro
> >> setenv mmcrootfstype btrfs rootwait fixrtc
> >> setenv mmcrootflags subvol=@
> >>
> >> setenv console ttyS0,115200n8
> >>
> >> setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae
> >> setenv initrd_file initrd.img-4.3.0-1-armmp-lpae
> >> setenv fdtfile sun7i-a20-olinuxino-lime.dtb
> >>
> >> setenv loadaddr 0x4600
> >> setenv initrd_addr 0x4800
> >> setenv fdtaddr 0x4700
> >>
> >> setenv initrd_high 0x
> >> setenv fdt_high 0x
> >>
> >> setenv loadkernel load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
> >> setenv loadinitrd load mmc ${mmcdev}:${mmcpart} ${initrd_addr} 
> >> ${initrd_file}\; setenv initrd_size \${filesize}
> >> setenv loadfdt load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
> >>
> >> setenv loadfiles run loadkernel\; run loadinitrd\; run loadfdt
> >> setenv mmcargs setenv bootargs console=${console} root=${mmcroot} 
> >> rootfstype=${mmcrootfstype} rootflags=${mmcrootflags}
> >>
> >> run loadfiles; run mmcargs; bootz ${loadaddr} 
> >> ${initrd_addr}:${initrd_size} ${fdtaddr}
> >
> 
> Maybe this will work, as a temporary workaround:
> 
> Take the old boot.cmd (for kernel 4.3) and update it for kernel 4.8
> (just change the kernel_file and initrd_file to match the files in
> /boot). Then you can produce a new boot.scr with the following:
> 
> mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
> 
> We used to do this in freedom-maker, but we switched (last March) to using 
> flash-kernel to set up the boot script.

Wonderful, James, I am in and on kernel 4.8.0-2. Now, to switch to using
flash-kernel, should I reconfig this kernel? The system will do so with
the next update anyway, I guess.
Also, I would like to remove the 4.3.0 and the 4.8.0-1 stuff. It does
not appear in aptitude. I'd like to have more free space on /boot, just
to be safe.

Dietmar

> 
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Samstag, den 07.01.2017, 14:59 +0100 schrieb Jonas Smedegaard:

> Quoting permondes - sagen (2017-01-07 14:31:34)
> > Am Samstag, den 07.01.2017, 18:24 +0530 schrieb Sunil Mohan Adapa:
> > 
> > > On 01/07/2017 06:17 PM, permondes - sagen wrote:
> > > [...]
> > > > But the device does not boot!
> > > > I can unplug the micro-SD card to check some log files on my computer, 
> > > > do you have an idea where to start?
> > > 
> > > Unfortunately, you won't have logs stored about this stage of booting.
> > > 
> > > Check if you have uEnv.txt and move it to see if you are able to boot.
> > > 
> > > To restore to earlier state, you can restore boot.scr files from backup.
> > > (flash-kernel also takes a backup with the name boot.scr.bak)
> > > 
> > 
> > I saved boot.scr and copied boot.scr.bak, so I am back in 4.3.0. I am
> > glad that worked, because starting all over again (ikiwiki, radicale,
> > privoxy, IRC) does not look too attractive to me.
> > There was previously the issue with LDAP, where I could not add nor
> > change users in Plinth anymore. I intended to approach that problem
> > afterwards, did not think they are related.
> > 
> > There is no file uEnv.txt in /boot, nothing similar to that.
> > 
> > If you think, my system is totally screwed up and starting from scratch
> > makes more sense, then I'll do that. Slowly, and probably taking
> > tutorial videos, and lots of questions on how to recover (mostly)
> > ikiwiki ;-). Please advice. 
> 
> I think your system is not totally screwed.  Try share both working and 
> non-working boot.scr - they might indicate what configuration file might 
> be wrongly setup to now produce broken boot files.

The currently running boot.scr with kernel 4.3:


> ...:/boot$ cat boot.scr
> 'V=�ѠV����#�Bi�setenv mmcdev 0
> setenv mmcpart 1
> 
> setenv mmcroot /dev/mmcblk0p2 ro
> setenv mmcrootfstype btrfs rootwait fixrtc
> setenv mmcrootflags subvol=@
> 
> setenv console ttyS0,115200n8
> 
> setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae
> setenv initrd_file initrd.img-4.3.0-1-armmp-lpae
> setenv fdtfile sun7i-a20-olinuxino-lime.dtb
> 
> setenv loadaddr 0x4600
> setenv initrd_addr 0x4800
> setenv fdtaddr 0x4700
> 
> setenv initrd_high 0x
> setenv fdt_high 0x
> 
> setenv loadkernel load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
> setenv loadinitrd load mmc ${mmcdev}:${mmcpart} ${initrd_addr} 
> ${initrd_file}\; setenv initrd_size \${filesize}
> setenv loadfdt load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
> 
> setenv loadfiles run loadkernel\; run loadinitrd\; run loadfdt
> setenv mmcargs setenv bootargs console=${console} root=${mmcroot} 
> rootfstype=${mmcrootfstype} rootflags=${mmcrootflags}
> 
> run loadfiles; run mmcargs; bootz ${loadaddr} ${initrd_addr}:${initrd_size} 
> ${fdtaddr}


The one for kernel 4.8, which did not start


> ...:/boot$ cat boot.scr.480
> 'V�or�Xp�Z   _
>  C� boot script W# boot script for Allwinner 
> SunXi-based devices
> 
> # Mainline u-boot v2014.10 introduces a new default environment and
> # a new common bootcmd handling for all platforms, which is not fully
> # compatible with the old-style environment used by u-boot-sunxi.
> # This script therefore needs to check in which environment it
> # is running and set some variables accordingly.
> 
> # On u-boot-sunxi, this script assumes that ${device} and ${partition}
> # are set.
> 
> # The new-style environment predefines ${boot_targets}, the old-style
> # environment does not.
> if test -n "${boot_targets}"
> then
>   echo "Mainline u-boot / new-style environment detected."
>   # Mainline u-boot v2014.10 uses ${devtype}, ${devnum} and
>   # ${bootpart} where u-boot-sunxi uses ${device} and ${partition}.
>   # ${distro_bootpart} replaced ${bootpart} in u-boot v2016.01.
>   if test -z "${device}"; then setenv device "${devtype}"; fi
>   if test -z "${partition}${distro_bootpart}"; then setenv partition 
> "${devnum}:${bootpart}"; fi
>   if test -z "${partition}"; then setenv partition 
> "${devnum}:${distro_bootpart}"; fi
> else
>   echo "U-boot-sunxi / old-style environment detected."
>   # U-boot-sunxi does not predefine kernel_addr_r, fdt_addr_r and
>   # ramdisk_addr_r, so they have to be manually set. Use the values
>   # from mainline u-boot v2014.10, except for ramdisk_addr_r,
>   # which is set to 0x4430 to allow for initrds larger than
>   # 13MB on u-boot-sunxi.
>   setenv kernel_ad

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Samstag, den 07.01.2017, 18:24 +0530 schrieb Sunil Mohan Adapa:

> On 01/07/2017 06:17 PM, permondes - sagen wrote:
> [...]
> > But the device does not boot!
> > I can unplug the micro-SD card to check some log files on my computer, do 
> > you have an idea where to start?
> 
> Unfortunately, you won't have logs stored about this stage of booting.
> 
> Check if you have uEnv.txt and move it to see if you are able to boot.
> 
> To restore to earlier state, you can restore boot.scr files from backup.
> (flash-kernel also takes a backup with the name boot.scr.bak)
> 

I saved boot.scr and copied boot.scr.bak, so I am back in 4.3.0. I am
glad that worked, because starting all over again (ikiwiki, radicale,
privoxy, IRC) does not look too attractive to me.
There was previously the issue with LDAP, where I could not add nor
change users in Plinth anymore. I intended to approach that problem
afterwards, did not think they are related.

There is no file uEnv.txt in /boot, nothing similar to that.

If you think, my system is totally screwed up and starting from scratch
makes more sense, then I'll do that. Slowly, and probably taking
tutorial videos, and lots of questions on how to recover (mostly)
ikiwiki ;-). Please advice. 

Sunil, does the Olinuxino A20 LIME (not LIME2!)run with amd64 as well?
Currently I use armhf

Dietmar


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Samstag, den 07.01.2017, 12:07 +0100 schrieb Jonas Smedegaard:

> Quoting permondes - sagen (2017-01-07 10:39:28)
> > Am Samstag, den 07.01.2017, 12:17 +0530 schrieb Sunil Mohan Adapa:
> > 
> > > On 01/07/2017 05:43 AM, Jonas Smedegaard wrote:
> > > [...]
> > > >> So it is still booting the 4.3 kernel, which is unknown to aptitude.
> > > > 
> > > > Seems your hardware is ARM-based.  Commonly ARM-based hardware need the 
> > > > package flashkernel to copy installed kernel + initramfs to the 
> > > > different (hardware-specific) location where the bootloader looks for 
> > > > it.
> > > 
> > > Indeed you need flash-kernel package.
> > > 
> > > If you have boot.cmd instead of boot.scr and also don't have
> > > flash-kernel package, you must upgrading and running a FreedomBox image
> > > from many releases ago.
> > > 
> > > To fix the situation,
> > > 
> > > 1. Take backup of your SD card.
> > > 
> > > 2. Make sure /boot is ext2fs and not vfat.
> > > 
> > > 3. Install flash-kernel.  This will create the proper /boot/boot.scr
> > > file with a line like "setenv fk_kvers '4.8.0-2-armmp-lpae'".
> > > 
> > > 4. Optionally set /etc/flash-kernel/machine to "Olimex
> > > A20-OLinuXino-LIME2" (depending on your board).  This should not be
> > > required as flash-kernel will properly detect the machine when you are
> > > running it from within the machine.
> > > 
> > > 4. Move /boot/boot.cmd to /boot/boot.cmd.bak.
> > > 
> > > 5. Reboot and check that boot happens properly.
> > > 
> > > If you already have flash-kernel package and /boot/boot.scr, then simply
> > > moving /boot/boot.cmd should fix the situation.
> > > 
> > 
> > Thanks Jonas, Sunil. flash-kernel was indeed missing. However,
> > installing, moving boot.cmd did not help, I am still in 4.3.0 (checked
> > with uname -r), boot.cmd was not newly generated. I realize that the
> > file boot.scr has some non-readable characters at the beginning, this
> > was actually already the case before:
> > 
> > 
> > 
> > > ...:/boot$ cat boot.scr
> > > 'V=�ѠV����#�Bi�setenv mmcdev 0
> > > setenv mmcpart 1
> > > 
> > > setenv mmcroot /dev/mmcblk0p2 ro
> > > setenv mmcrootfstype btrfs rootwait fixrtc
> > > setenv mmcrootflags subvol=@
> > > 
> > > setenv console ttyS0,115200n8
> > > 
> > > setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae
> > > setenv initrd_file initrd.img-4.3.0-1-armmp-lpae
> > > setenv fdtfile sun7i-a20-olinuxino-lime.dtb
> > > ...
> > 
> > Should I move also boot.scr, then reinstall flash-kernel and restart?
> 
> When flash-kernel is installed, it have added a hook to the kernel 
> install routines, so instead of moving things around manually it should 
> be enough (and safer, and easier to debug) that you afterwards run 
> dpkg-reconfigure linux-image-4.8.0-2-armmp-lpae (adjust for the kernel 
> you want to reinstall).
> 
> As for the stuff it beginning of the file: I believe it is opposite: the 
> compiled file as a convenience embeds the cleartext content too at the 
> end ;-)
> 
> 
>  - Jonas


Hi Jonas,

unfortunately, I am rather kind of the target user for the Freedombox,
all these things are far beyond my knowledge of Linux - even though I
celebrated my 10 years with Linux last summer.
So the reconfig went through successfully (I think), here is the output:


> ...:/boot$ sudo dpkg-reconfigure linux-image-4.8.0-2-armmp-lpae
> 
> [sudo] Passwort für Dietmar: 
> 
> /etc/kernel/postinst.d/apt-auto-removal:
> 
> N: Datei »50unattended-upgrades.ucf-dist« in Verzeichnis
> »/etc/apt/apt.conf.d/« wird ignoriert, da sie eine ungültige
> Dateinamen-Erweiterung hat.
> 
> N: Datei »50unattended-upgrades.ucf-dist« in Verzeichnis
> »/etc/apt/apt.conf.d/« wird ignoriert, da sie eine ungültige
> Dateinamen-Erweiterung hat.
> 
> N: Datei »50unattended-upgrades.ucf-dist« in Verzeichnis
> »/etc/apt/apt.conf.d/« wird ignoriert, da sie eine ungültige
> Dateinamen-Erweiterung hat.
> 
> /etc/kernel/postinst.d/initramfs-tools:
> 
> update-initramfs: Generating /boot/initrd.img-4.8.0-2-armmp-lpae
> 
> DTB: sun7i-a20-olinuxino-lime.dtb
> 
> Installing 
> /usr/lib/linux-image-4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb into 
> /boot/dtbs/4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb
> 
> Installing new sun7i-a20-olinuxino-lime.dtb.
> 
> Installing 
> /usr/lib/linux-

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Samstag, den 07.01.2017, 12:17 +0530 schrieb Sunil Mohan Adapa:

> On 01/07/2017 05:43 AM, Jonas Smedegaard wrote:
> [...]
> >> So it is still booting the 4.3 kernel, which is unknown to aptitude.
> > 
> > Seems your hardware is ARM-based.  Commonly ARM-based hardware need the 
> > package flashkernel to copy installed kernel + initramfs to the 
> > different (hardware-specific) location where the bootloader looks for 
> > it.
> 
> Indeed you need flash-kernel package.
> 
> If you have boot.cmd instead of boot.scr and also don't have
> flash-kernel package, you must upgrading and running a FreedomBox image
> from many releases ago.
> 
> To fix the situation,
> 
> 1. Take backup of your SD card.
> 
> 2. Make sure /boot is ext2fs and not vfat.
> 
> 3. Install flash-kernel.  This will create the proper /boot/boot.scr
> file with a line like "setenv fk_kvers '4.8.0-2-armmp-lpae'".
> 
> 4. Optionally set /etc/flash-kernel/machine to "Olimex
> A20-OLinuXino-LIME2" (depending on your board).  This should not be
> required as flash-kernel will properly detect the machine when you are
> running it from within the machine.
> 
> 4. Move /boot/boot.cmd to /boot/boot.cmd.bak.
> 
> 5. Reboot and check that boot happens properly.
> 
> If you already have flash-kernel package and /boot/boot.scr, then simply
> moving /boot/boot.cmd should fix the situation.
> 

Thanks Jonas, Sunil. flash-kernel was indeed missing. However,
installing, moving boot.cmd did not help, I am still in 4.3.0 (checked
with uname -r), boot.cmd was not newly generated. I realize that the
file boot.scr has some non-readable characters at the beginning, this
was actually already the case before:



> ...:/boot$ cat boot.scr
> 'V=�ѠV����#�Bi�setenv mmcdev 0
> setenv mmcpart 1
> 
> setenv mmcroot /dev/mmcblk0p2 ro
> setenv mmcrootfstype btrfs rootwait fixrtc
> setenv mmcrootflags subvol=@
> 
> setenv console ttyS0,115200n8
> 
> setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae
> setenv initrd_file initrd.img-4.3.0-1-armmp-lpae
> setenv fdtfile sun7i-a20-olinuxino-lime.dtb
> ...

Should I move also boot.scr, then reinstall flash-kernel and restart?

Dietmar
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Freitag, den 06.01.2017, 20:25 +0100 schrieb permondes - sagen:

> Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen:
> 
> > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter
> > Reinholdtsen: 
> > 
> > > [permondes - sagen]
> > > > I think that with the kernel and initrd-updates the old version were not
> > > > removed. Can I simply remove them with "rm"? Just keeping the latest
> > > > version?
> > > 
> > > I would instead use 'dpkg -S /boot/v*' to identify packages to remove,
> > > and 'apt purge ' to remove them.
> > > 
> > 
> > I think the issue is related to the fact that I am still running
> > Linux 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded.
> > How do I make FreedomBox use the other kernels? A simple restart did
> > not help.
> 
> I removed packages linux-image 4.5 and 4.7 and purged the conf files
> of 4.5, 4.6 and 4.7. Now I have again about 40 MB free space on boot.
> Apt did some configuration stuff with the 4.8 kernel, but after a
> restart, it booted again into 4.3. How can I make it understand to use
> the most recent kernel?
> Which kernels are you running? 

/boot/boot.cmd contains these 2 lines even after an 
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.8.0-2-armmp-lpae


> setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae
> setenv initrd_file initrd.img-4.3.0-1-armmp-lpae

So it is still booting the 4.3 kernel, which is unknown to aptitude.

> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen:

> Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen: 
> 
> > [permondes - sagen]
> > > I think that with the kernel and initrd-updates the old version were not
> > > removed. Can I simply remove them with "rm"? Just keeping the latest
> > > version?
> > 
> > I would instead use 'dpkg -S /boot/v*' to identify packages to remove,
> > and 'apt purge ' to remove them.
> > 
> 
> I think the issue is related to the fact that I am still running Linux
> 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded.
> How do I make FreedomBox use the other kernels? A simple restart did
> not help.

I removed packages linux-image 4.5 and 4.7 and purged the conf files of
4.5, 4.6 and 4.7. Now I have again about 40 MB free space on boot.
Apt did some configuration stuff with the 4.8 kernel, but after a
restart, it booted again into 4.3. How can I make it understand to use
the most recent kernel?
Which kernels are you running?
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] boot partition full

[permondes - sagen]

Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen:

> [permondes - sagen]
> > I think that with the kernel and initrd-updates the old version were not
> > removed. Can I simply remove them with "rm"? Just keeping the latest
> > version?
> 
> I would instead use 'dpkg -S /boot/v*' to identify packages to remove,
> and 'apt purge ' to remove them.
> 

I think the issue is related to the fact that I am still running Linux
4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded.
How do I make FreedomBox use the other kernels? A simple restart did not
help.
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] boot partition full

[permondes - sagen]

My boot partition is full, so the latest kernel and uboot updates could
not be installed. The partition contains:

boot.cmd   config-4.8.0-1-armmp-lpae
initrd.img-4.7.0-1-armmp-lpae  System.map-4.7.0-1-armmp-lpae
vmlinuz-4.7.0-1-armmp-lpae
boot.scr   config-4.8.0-2-armmp-lpae
initrd.img-4.8.0-1-armmp-lpae  System.map-4.8.0-1-armmp-lpae
vmlinuz-4.8.0-1-armmp-lpae
config-4.3.0-1-armmp-lpae  dtbs   lost+found
System.map-4.8.0-2-armmp-lpae  vmlinuz-4.8.0-2-armmp-lpae
config-4.5.0-2-armmp-lpae  initrd.img-4.3.0-1-armmp-lpae
System.map-4.3.0-1-armmp-lpae  vmlinuz-4.3.0-1-armmp-lpae
config-4.7.0-1-armmp-lpae  initrd.img-4.5.0-2-armmp-lpae
System.map-4.5.0-2-armmp-lpae  vmlinuz-4.5.0-2-armmp-lpae

I think that with the kernel and initrd-updates the old version were not
removed. Can I simply remove them with "rm"? Just keeping the latest
version?

Dietmar

PS: anything I can do to prevent this?
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] radicale rights

[permondes - sagen]

I just let radicale get updated, which was held back since 6-Dec. Now I
cannot access the calender file any more, but it is still existing.
I checked the "config" file and found it is mostly just comments. These
parameters are not set any more:

> [server]
> hosts= ...
> base_prefix=
> [well-known]
> caldav=
> carddav=
> [auth]
> type=remote-user

I checkmarked in Plinth the "owner only" and it is correctly set.
Before re-setting the old parameters, did anything change in the
handling of access rights in radicale?

Dietmar

___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Joining a mesh network with BATMAN

[permondes - sagen]

Am Montag, den 21.11.2016, 01:18 +0100 schrieb Bastien Rocheron:
> Hello again,
> 
> Something very strange happened. As I was logged in through SSH trying
> to understand this issue, suddenly my user was not recognized any more
> and I received a message close to something like: user 1000 unknown, who
> are you?
> 
> Then I logged out from ssh, tried to login again but was unable. The web
> interface disappeared as well. That lasted for long enough that I gave
> up trying.
> 
> After an hour or two I tried again and was greeted again by the web
> interface. The weird thing is that it had changed. I had noticed that I
> did not have the 'Disks' module in the menu and now it is there.
> So I tried immediately to create a new network interface and now the web
> interface accepts the channel and BSSID settings.
> 
> I am really curious as to what happened. It is great that things get
> solved by itself but at the same time I fear automation is out of control.
Maybe during that our the unattended-upgrade was working to bring you to
0.11. This would explain you got "Disks" and can now (partly) work with
mesh.

> 
> Now I have followed the guide again and successfully created the first
> interface for ad-hoc wireless and I can see on my router that this
> interface is connected. But the bat0 interface did not get created in
> the process and the second step is thus not possible.
> 
> I have done a lsmod and realized that no batman module was loaded. So I
> first checked with modprobe that it can be loaded. Then I added
> batman-adv in my /etc/modules-load.d/modules.conf and rebooted.
> I now have batman_adv loaded along with its dependencies.
> But trying again from scratch does not bring up bat0.
I am afraid, I have no experience (yet) on mesh networks. For my system
knowledge, it is still in a too early state and I rather wait for
further development.

> 
> If no suggestion is made I will try to bring it up manually. But I guess
> this will conflict with network manager. I need to understand how it is
> managed.
> 
> Cheers

Dietmar
> 
> On 20/11/16 17:59, Bastien Rocheron wrote:
> > Hello,
> > 
> > I am trying to join an existing mesh network (I have created it and have
> > already various nodes in it) with freedombox.
> > 
> > I am following the instructions found in the manual, specifically
> > 9.3.4.1. Joining a mesh network.
> > 
> > The issue is that various settings are not available in the interface
> > while adding a network connection(I'm using the latest image).
> > For example I can't set the channel nor BSSID, without which, nodes
> > can't join the network (as far as I'm aware).
> > 
> > And thus in the next step I can't locate bat0 as an interface.
> > 
> > Do you have any recommendations?
> > 
> > Cheers.
> > 
> > ___
> > Freedombox-discuss mailing list
> > Freedombox-discuss@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
> > 
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] firewalld upgrade

[permondes - sagen]

Am Samstag, den 19.11.2016, 08:55 -0500 schrieb James Valleroy:

> On 11/19/2016 06:24 AM, permondes - sagen wrote:
> > firewalld has a conffile prompt and I am not sure which version I should
> > use. The changes are:
> > 
> >> -DefaultZone=external
> >> +DefaultZone=public
> >> IPv6_rpfilter=yes
> >> +IndividualCalls=no
> >> +LogDenied=off
> > 
> > Is it save to take the new settings or will e.g. DefaultZone impact
> > FreedomBox?
> 
> FreedomBox does expect the DefaultZone to be external. I think the
> safest option is to:
> 
> 1) Choose 'y' to take the maintainer's version of this file.
> 
> 2) Run "sudo firewall-cmd --set-default-zone=external" to change the
> DefaultZone back to external.
> 
> Of course this is not a good user experience, and will prevent automatic
> upgrades of firewalld whenever the package modifies this file.
> 
> The root cause is that /etc/firewalld/firewalld.conf is a conffile, and
> firewalld modifies this file when we run the above command.
> 
> --
> James

Thanks James, I did that, looks okay.
We have to find a way to handle the special configurations in a
different / user friendly way, I think.

> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] firewalld upgrade

[permondes - sagen]

firewalld has a conffile prompt and I am not sure which version I should
use. The changes are:


> -DefaultZone=external
> +DefaultZone=public
> IPv6_rpfilter=yes
> +IndividualCalls=no
> +LogDenied=off


Is it save to take the new settings or will e.g. DefaultZone impact
FreedomBox?

Dietmar
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] 403 error when connecting from the outside. Also: Shaarli.

[permondes - sagen]

Am Dienstag, den 08.11.2016, 15:52 -0500 schrieb A. F. Cano:

> On Mon, Nov 07, 2016 at 07:51:30PM +0100, permondes - sagen wrote:
> >...
> >  I have been using Bookmarks (Shaarli) from the inside network for a
> >  while now.  I haven't noticed anything to distinguish whether it is,
> >  or should be (or not) accessible from the outside, so I assumed it would
> >  be.
> > 
> >I don't have Shaarli running, as I am using the box based on Testing,
> >which does not include Shaarli.
> 
> It must be a leftover from the time the box was running unstable.  I
> changed to testing shortly after the problem that prevented ssh access.
> 
> I could swear I was able to access Shaarli before, at the url
> http://fbx/shaarli/ but now I only get a blank page, both with chromium and
> firefox.  If I click on the "shaare link" button (that's only installed in
> firefox) it calls up
> 
> http://fbx/shaarli/?do=login=
> 
> And then it works fine.
> 
> But if I go to http://fbx/shaarli/?do=login
> I do get the login page but then I invariably get "Wrong login/password"
> when I type it in, and a blank page when I use the saved (in firefox)
> login/password.  This is the same one that works in the line with the
> post directive above.  Something strange is going on here...

I am afraid, I cannot help on this. This goes beyond my knowledge.
Maybe someone else can step in?

> 
> > ...
> >I am using radicale for my calendar. It's been set up as described in the
> >wiki: [1]https://wiki.debian.org/FreedomBox/Manual/Radicale (those 
> > entries
> >are from me).
> 
> Thanks.  I'll keep trying.  The immediate problem is that my data are in
> a version of Kaddressbook and Korganizer that don't support
> CalDav/CarDav.  I'll have to export and import into a newer version that
> does, it looks like.
> 
> >As you can see, I am using evolution (stable). After the calendar was set
> 
> I found this page:
> 
> http://radicale.org/user_documentation/#idcaldav-and-carddav-clients
> 
> That also has instructions for kde.  Unfortunately it also requires
> Cal/CarDav.
> 
> >...
> >  Those are the 2 applications that are installed at this point.  I am now
> >  thinking that maybe I need to provide the specific paths to the
> >  applications but I can't test that now since I'm on the inside at the
> >  moment.
> 
> Ok, did try that eventually and it didn't work.  Not even from the inside.
> Of course from the inside I just got the blank screen.  I wonder if the
> password issue is somehow related to having installed the letsencrypt
> certificate.  Logically it shouldn't be related, but strenge things are
> happening.
> 
> Incidentally, the duplicate entry for the internal LAN port in the
> networks page went away after a reboot.
> 
> Augustine
> 
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] 403 error when connecting from the outside.

[permondes - sagen]

Am Sonntag, den 06.11.2016, 23:30 -0500 schrieb A. F. Cano:

> On Sun, Nov 06, 2016 at 02:37:24PM +0100, permondes - sagen wrote:
> >Hi Augustine,
> > 
> >which service are you trying to access? E.g. Plinth cannot be accessed
> >from outside of your local network, this gives error 403, but e.g. 
> > ikiwiki
> 
> Mmm... ok.
> 
> >should work.
> 
> I have been using Bookmarks (Shaarli) from the inside network for a
> while now.  I haven't noticed anything to distinguish whether it is,
> or should be (or not) accessible from the outside, so I assumed it would
> be.

I don't have Shaarli running, as I am using the box based on Testing,
which does not include Shaarli.

> 
> The diagnostics page shows radicale as passing all the tests, but I have
> not figured out yet how to import my data from Kaddressbook and Korganizer.
> 
> Of course entering every address book entry, calendar item and todo list
> item by hand is not an option.  Can someone provide some hints about how
> to do this automatically or in a few steps?  I looked into this a while
> ago and found that since all my data is under Debian wheezy kde, it's
> not going to be as painless as it should be.  I might have to export
> everything, import it into a jessie kde system and go from there.
> 
> Has anyone tried to do this?

I am using radicale for my calendar. It's been set up as described in
the wiki: https://wiki.debian.org/FreedomBox/Manual/Radicale (those
entries are from me).
As you can see, I am using evolution (stable). After the calendar was
set up on the box, I simply copied the appointments to the new calendar
by changing the "calendar" entry of each appointment. Then I updated the
calendar (right click and refresh), waited an eternity (processing is
extremely slow, 1h should be sufficient if there are many new entries)
and then checked with my Android mobile phone (also described there). I
think it should be possible to do the same in KDE. Access is possible
from the outside, I used sds-ip.de in the past, now I have my own domain
registered.

> 
> Those are the 2 applications that are installed at this point.  I am now
> thinking that maybe I need to provide the specific paths to the
> applications but I can't test that now since I'm on the inside at the
> moment.
> 
> ...
> 
> >Dietmar
> 
> Thanks for replying.
> 
> >...
> 

Dietmar
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] 403 error when connecting from the outside.

[permondes - sagen]

Hi Augustine,

which service are you trying to access? E.g. Plinth cannot be accessed
from outside of your local network, this gives error 403, but e.g.
ikiwiki should work.

I also have now 2 network connections: eth0 active, Freedombox inactive.
This used to cause issues in the past and I had had to activate the
Freedombox one, but now it works this way, I have no idea why. Probably
it is not connected to your issue.

Dietmar

Am Samstag, den 05.11.2016, 23:58 -0400 schrieb A. F. Cano:

> Hi,
> 
> I have tried to connect to the freedombox from the outside and I get a
> 403 Error: "you do not have permission..."
> 
> The Dynamic DNS Client is set up (gnudip.datasystems24.net) to a domain
> under freedombox.rocks (HUGE thanks to whoever set this up!) and I do
> get to the freedombox.  The message is generated by plinth (it says at
> the bottom of the error page)  but I get the 403 message.  Then I
> obtained a certificate (through the "Certificates (Let's Encrypt)" page
> thinking that this might be the problem, but I still get the same error.
> 
> Certifate status  Website Security
> 
> Expires on Jan 28 18:27:00 2017 GMT   Enabled
> 
> If I "Run Diagnostics" from the "Let's Encrypt" page the result is
> "passed", but when I click on "Diagnostics" on the left of the page and
> the diagnostics for all modules are displayed the letsencrypt module
> diagnostics "failed".
> 
> Interestingly, for "Module diagnostics" this test fails:
> 
> Access URL http://75.250.144.199/plinth/ on tcp4  failed
> 
> This is not the Local IP address returned by ppp (which is
> 75.226.105.71, as shown by the Network Manager log and ifconfig)
> 
> From the "Firewall" page (/plinth/sys/firewall)
> 
> Web ServerEnabled
> http  Permitted
> Web Server over Secure Socket Layer   Enabled
> https Permitted
> 
> But this should not be a factor since the web server is running on the
> freedombox itself, right?
> 
> /etc/apt/sources.list says "testing" and plith is 0.10.0 per the "About"
> page.  The last software upgrade was done this morning.
> 
> What am I missing? Any hints out there?
> 
> There is also something weird that happened to the "Networks" page.
> This apu1d4 box has 3 ethernet interfaces (WAN, enp3s0 and enp2s0) but
> now there are 2 entries for enp3s0, one labeled "enp3s0" which is shown
> correctly as "Active" and "FreedomBox LAN enp3s0" which is shown as
> "Inactive".  When I clicked on "enp3s0" it said that this connection was
> not known to the freedombox, it had firewall zone: none and a message
> said that it should be deleted, so I did.  this caused a 500 internal
> error message and ppp got disconnected.  When network manager went
> through its paces, enp3s0 was again active and "FreedomBox LAN
> enp3s0" was still inactive.  It looks like Network Manager prefers
> "enp3s0"...
> 
> Any hints about this issue would also be welcome.
> 
> Thanks!
> 
> Augustine
> 
> 
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Re: [Freedombox-discuss] Hack call

[permondes - sagen]

Am Montag, den 10.10.2016, 17:39 + schrieb dgj+li...@systemli.org:
> > Also if someone is looking to contribute, we can help them find an 
> > appropriate task.
> 
> I was unable to attend the hack call but would be interested in 
> contributing to the FBX manual. What is the etiquette for doing so? As a 
> non-SysAdmin, does it do more harm to contribute and potentially get 
> something (slightly) wrong than not to contribute? I take extensive 
> notes of what does and doesn't work as a user and would be happy to give 
> back to this community by sharing what has worked for me in getting 
> things working.
> 
> Best,
> DJ

That was also my start, to put my notes on installing and using the Box
in the Wiki. I think this is very important input.

The manual is based on the wiki, if you have a debian wiki account, you
can start working on it. It provides a history, so that anyone can
polish your changes afterwards, so there is no risk. 

We have a todo list for the manual here:
https://wiki.debian.org/FreedomBox/Manual/TODO 

The pages per app should follow a certain structure:
https://github.com/freedombox/freedombox.org/issues/9

The level of completeness of the pages is very varying So there is still
a lot to do. The target reader is a FreedomBox user without deep
understanding of Linux and Debian. Therefore, e.g. I started to put some
topics that require SSH in a separate chapter called "advanced user". 

Have fun
Dietmar
> 
> 
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss


___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] Integrate "Security" into "Users"

[permondes - sagen]

I think, we could integrate the "Security" section into "Users".
>From a users perspective, the security feature is related to how users
are handled in Freedombox, so he would search for it in that section.
Also, there is just one setting in the security section and the overview
of available features is getting cluttered. So we should put ourselves
in the perspective of our target users and assign features to the
sections accordingly.
Before putting this request in git, I would like to hear others'
opinions.

Dietmar
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

[Freedombox-discuss] Quassel

[permondes - sagen]

Is my Quassel-core down or is there an issue with irc.debian.org?


> Connecting to irc.debian.org/freedombox:6667...
> Connection failure: Host not found
> 

Dietmar



___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss