davesteele / comitup Goto Github PK

Hello,
I've cloned a raspberrypi with comitup. So now their comitup name ( comit-xx) got exactly the same as the other one. I guess that was blocking one of them to allow conect to the network. is that the right and expected behaviour, right?

A short try I did that works: remove the comitup package ( sudo apt-get remove comitup ) and install it again ( sudo apt-get install comitup ). The comitup name has changed ok. I've had
to add wifi password to this new one and now both are able to connect at same time.

Is this a good process? Or may be all this was not necesary ;-D

Hi,

As far as I can see the Pi zero W is not supported. The AP just don't show up, even one without SSID.

Is there anything we can do ?

Thanks

Hello

I have a Raspberry Pi ( This is the edge device where I have configured the comitup service ) with the Raspbian ( Stretch ).

Expected Behavior

I have a requirement as follows =>

• I want to connect an edge device to the available network.

• The access point on the edge device will only stop when the edge device is successfully connected to the wireless network.

Reason behind this requirement is that when a wrong password is sent or due to any circumstance it is not possible to connect that wifi then, in that case, I won't get feedback if the edge device is connected successfully or not.

Actual Behavior

I saw a behavior whenever a connect API is called on the edge device it stops the Hotspot ( i.e. It's own AP ) and tries to connect the wireless network / AP

You have also mentioned this in the documentation

If the computer cannot automatically connect to a local wifi access point, comitup will create a custom hotspot, and establish a comitup-web web service on that network.

Steps to Reproduce the Problem

1. Added the line deb http://davesteele.github.io/comitup/repo comitup main inside this file => /etc/apt/sources.list.
2. wget https://davesteele.github.io/key-366150CE.pub.txt
3. sudo apt-key add key-366150CE.pub.txt
4. sudo apt-get update
5. sudo apt-get install comitup
6. I connected the Hotspot that was created by the edge device
7. After that, I went to the <edge_device_ip_address>:80 on the browser and I got all the available network list.
8. I selected the network and typed in the wrong password and pressed the connect.
9. In that case, it turned off the Access point and tried to connect the Wireless network.
10. After a few seconds of try it started it's Hotspot again.

Question

So I was wondering if is it possible to stop the Hotspot only if the Edge device is successfully connected to the wifi?

I have a fairly standard and small raspbian installation on a RPi3B+ and I have installed the latest comitup from the PPA.

Comitup starts, but the wifi clients don't get an IP.
The log suggest that dnsmasq fails to start:

$ sudo systemctl status comitup
● comitup.service - Comitup Wifi Management
   Loaded: loaded (/lib/systemd/system/comitup.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-07-30 14:55:20 UTC; 1min 50s ago
     Docs: man:comitup(8)
 Main PID: 3141 (comitup)
    Tasks: 1 (limit: 2319)
   Memory: 11.8M
   CGroup: /system.slice/comitup.service
           └─3141 /usr/bin/python3 /usr/sbin/comitup

Jul 30 14:54:58 raspberry-find3-01 dnsmasq[3326]: FAILED to start up
Jul 30 14:54:59 raspberry-find3-01 comitup[3141]: dnsmasq: failed to create listening socket for port 53: Address already in use
Jul 30 14:54:59 raspberry-find3-01 dnsmasq[3328]: failed to create listening socket for port 53: Address already in use
Jul 30 14:54:59 raspberry-find3-01 dnsmasq[3328]: FAILED to start up
Jul 30 14:54:59 raspberry-find3-01 comitup[3141]: dnsmasq: failed to create listening socket for port 53: Address already in use
Jul 30 14:54:59 raspberry-find3-01 dnsmasq[3330]: failed to create listening socket for port 53: Address already in use
Jul 30 14:54:59 raspberry-find3-01 dnsmasq[3330]: FAILED to start up
Jul 30 14:55:01 raspberry-find3-01 comitup[3141]: OK
Jul 30 14:55:01 raspberry-find3-01 comitup[3141]: OK
Jul 30 14:55:20 raspberry-find3-01 systemd[1]: Started Comitup Wifi Management.

Would it be interesting to check whether dnsmasq started successfully?

Investigating the port usage it seems systemd-resolved is the culprit:

$ sudo netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      102        9197       201/systemd-resolve 
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      0          27092      3142/python3        
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      102        9204       201/systemd-resolve 
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          12480      362/sshd            
tcp6       0      0 :::5355                 :::*                    LISTEN      102        9200       201/systemd-resolve 
tcp6       0      0 :::22                   :::*                    LISTEN      0          12482      362/sshd            
udp        0      0 0.0.0.0:33251           0.0.0.0:*                           107        12372      291/avahi-daemon: r 
udp        0      0 127.0.0.53:53           0.0.0.0:*                           102        9203       201/systemd-resolve 
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13498      312/dhcpcd          
udp        0      0 169.254.110.128:123     0.0.0.0:*                           104        28177      351/ntpd            
udp        0      0 10.42.0.1:123           0.0.0.0:*                           104        25041      351/ntpd            
udp        0      0 192.168.5.161:123       0.0.0.0:*                           104        12889      351/ntpd            
udp        0      0 127.0.0.1:123           0.0.0.0:*                           0          11247      351/ntpd            
udp        0      0 0.0.0.0:123             0.0.0.0:*                           0          11243      351/ntpd            
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           107        12370      291/avahi-daemon: r 
udp        0      0 0.0.0.0:5355            0.0.0.0:*                           102        9196       201/systemd-resolve 
udp6       0      0 fe80::ba27:ebff:feb:123 :::*                                104        27966      351/ntpd            
udp6       0      0 fe80::bcb6:31fb:6d3:123 :::*                                104        14364      351/ntpd            
udp6       0      0 ::1:123                 :::*                                0          11249      351/ntpd            
udp6       0      0 :::123                  :::*                                0          11240      351/ntpd            
udp6       0      0 :::5353                 :::*                                107        12371      291/avahi-daemon: r 
udp6       0      0 :::5355                 :::*                                102        9199       201/systemd-resolve 
udp6       0      0 :::46971                :::*                                107        12373      291/avahi-daemon: r 

After stopping that service I get an IP address with my WiFi client.

I would like to turn on comitup WI-FI connectivity only when raspberry pi pin 18 is HIGH other wise COMITUP WI-FI connectivity turn off. Is it any possible?

I tried comitup, but I can't connect to a wifi network without a password, the application doesn't accept the empty field "Password(if required)". Congratulation for the application.

Not connect to WPA2 networks - not see the lock icon and it connects to it like these networks are open.

Comitup needs a lot of time to start. Any ideas how I can speed it up?

In playing around getting 1.6-1 running on raspberry pi zero I have found dhcp server continues to hand out 10.41.0.x addresses while device is in connects state. I have a esp8266 that come out of deep sleep and connect to wifi. It appears that comitup is seeing the discover broadcasts and is sending out offers.

This was in 1.5-1 as well. Honestly I have not rebooted once got 1.6-1 running with the networkmanager 2.1-1. I am remote to where the device is and did not want to lose connectivity.

I am trying to use comitup to manage the WiFi connections on an RPI that uses a web application that runs on Docker. I tried setting the web service in comitup.conf to docker.service but Docker starts running anyway.

Hi Dave,
my name is Klaus Eisermann and I have been using comitup privately for one my own maker projects. Professionally am product innovation manager at LabMaker, a company striving to make open source scientific hardware readily available to the scientific community and to researchers not willing or able to build their own hardware. On our website www.labmaker.org we offer the key components of open source equipment in good quality for a fair price while providing all references to the open source repositories of the founding developers. Generally our founding developers feel very positive about having a commercial alternative source rather than having to reject requests from people not prepared to deal with manufacture.
I wanted to make sure with you that you have no objections if we started using comitup as OS for future Raspberry projects. As we deal mostly with scientists reluctant to dig deeper into technical issues the access point would ease setup a lot for them. Naturally we would post a link to your repository and the comitup project would stay entirely under your control.
Please let me know your thoughts

cheers
Klaus

Unicode should be tested as well.

I tried running comitup from the command line:

ImportError: cannot import name persist

@davesteele, when was the last time you tried running setup.py on a fresh image of Raspbian? It appears that many things are broken due to poor maintenance of the GitHub repo.

Hello, is it possible to enable ethernet connectivity and if yes, how do I do that?
Because right now ethernet doesn't get an ip from dhcp

If the specified external_callback script is not owned by the root user and group, comitup crashes on the Popen call, complaining of the prerun function.

Are the user and group calls being made in the wrong order?

Hey
I got some questions

1. Is it possible to disable the SSH functionality when connection to temporary hotspot, so that only setting up the home access point functionality is available?
2. A way to set the commitup-<nnnn> default password so that it isnt connected by someone else accidently.
3. Does it support Enterprise wireless, where generally it requires a username as well with the password? I see that the confirm.html only has the field for password

Some feature request

1. Change the commitup-<nnnn> to commitup-<ipaddr>. This would make it easy for the end user to know the ip addr to navigate straight up witouth a zeroconf browser.

Hi
Very good project, been looking for a while for something like this, not sure why finding this has taken so long.
I'm using a wifi dongle and wanted to know if its possible to disable the hotsport on wlan0 when a connection has been established? Rather than leaving it running. I'm just need a connection on wlan1 (dongle).
Because there is no authentication for connecting to the hotspot I fear this might be a security issue if always left advertised.

thanks

could this update have turned console auto login off?

Hi,
To make pi 3 as an access point and wifi client I tried Comitup wifi manager.
First, I tried with Comitup image which is given in below link. and it was working properly.

https://davesteele.github.io/comitup/

After that, I tried with installing Comitup package with the official raspbian OS. I followed steps which are given in below link but it was not working for me.

https://davesteele.github.io/comitup/ppa.html

After booting I could 't see pi as an access point. Is there any other way to do this thing?
(there is no previous access point available)

Thanks!!

There is a problem connecting to the Comitup hotspot using IOS devices.

Edit - Disputed. Appears to work on modern devices.

In the readme is written

If two wifi interfaces are available, the first will persistently remain the hotspot, and the second will get the external connection. When both are connected, forwarding and masquerading are enabled so that hotspot-connected devices can access external networks.

but here it's exactly the other way around:

wlan0 (build in raspi wifi) connects to choosen network
wlanwlx74da... (USB wifi dongle) seems to be the hotspot

but i cannot see an open hotspot. something is strange here....

is there a way to choose the "primary wlan device" in comitup/nm somehow?

Hey
I have certain scripts that I would like to run when comitup successfully establishes wifi connection. Is it possible to have comitup run them? I dont want to use rc.local or crontab or other ways. I was looking to make it depended on comitup.

In addition to comitup starting scripts on boot, so if wifi temporarily goes out of range, comitup stops those scripts and if the wifi comes back up, comitup re-runs those scripts.

Is it possible?

PS - comitup running in Raspberry Pi3, with one Ruby script and other a python script

hello david,
it is me again.
my micro sd card is perfectly ok.
i ran fdisk on the image file which i downloaded and got this:-

fdisk "2017-03-02-raspbian-jessie-comitup-0.7-03-13.img"

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): v
Total allocated sectors 15237120 greater than the maximum 3096576.

Command (m for help): p

Disk 2017-03-02-raspbian-jessie-comitup-0.7-03-13.img: 1.5 GiB, 1585446912 bytes, 3096576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x432b3940

Device Boot Start End Sectors Size Id Type
2017-03-02-raspbian-jessie-comitup-0.7-03-13.img1 8192 137215 129024 63M c W95 FAT32 (LBA)
2017-03-02-raspbian-jessie-comitup-0.7-03-13.img2 137216 15237119 15099904 7.2G 83 Linux

Command (m for help):

this would explain why i have been unable to dd your disk image to a micro sd card.

best wishes
john
ps still struggling to use ssh on a raspberry pi zero W.

when setting up the wifi on http://raspberrypi.local, the ssh stop responding after.

I reconnect to my router wifi, I can see the device connect to 192.168.1.113. I can ping the device but it not answer to ssh. how do I fix that?

I am trying to bring comitup to a raspberry pi. In order to access the headless raspberry pi, I have a PC with two NICs. On that PC I have configured the second NIC through network manager to share the Internet connection of the other NIC. Network manager seems to use IP addresses in the range of 10.42.0.1/32 for the clients connecting through the second interface. This is the exact range that comitup uses :( I think I experience problems due the IP network ranges being the same.

Would it be possible to detect whether the IP addresses comitup wants to hand out to its clients clashes with a subnet the device is already part of?
As a stop-gap measure, using a different range than the one network manager uses by default might be okay.

FWIW: I have been able to convince network manager to hand out different IPs: https://askubuntu.com/a/829759/207933 but still think that it'd be valuable if comitup did not hand out IPs that it can't handle.

Issue #39 has not been fixed yet.

How difficult would it be to integrate a real captive portal functionality to this package like descriped here?

https://en.wikipedia.org/wiki/Captive_portal#Implementation

My Ubuntu install tells me the Avahi service is disabled as soon as I connect to the comitup hotspot, complaining it is a .local domain.

Hello.

I've done a NOOBS V2.8.1 to install Raspbian Stretch on my Raspberry Pi 3 Model B.

I used the Graphical Preferences Config to change the password, set to boot to gui, enable ssh, set Localization options (Canada English UTF-8), Timezone, Keyboard Layout and WiFi Country (Canada) and rebooted.

Then added deb http://davesteele.github.io/comitup/repo comitup main to /etc/apt/sources.list and did apt-get update, apt-get upgrade, apt-get dist-upgrade and rebooted again.

Finally apt-get install comitup and I'm getting this in /var/log/comitup.log

2018-06-23 23:02:23,771 - comitup - INFO - Setting state to CONNECTING
2018-06-23 23:02:29,000 - comitup - INFO - Setting state to HOTSPOT
2018-06-23 23:02:29,169 - comitup - INFO - Activating hotspot
2018-06-23 23:02:29,304 - comitup - WARNING - Error connecting hotspot
2018-06-23 23:05:30,421 - comitup - INFO - Setting state to CONNECTING
2018-06-23 23:05:35,648 - comitup - INFO - Setting state to HOTSPOT
2018-06-23 23:05:35,827 - comitup - INFO - Activating hotspot
2018-06-23 23:05:35,962 - comitup - WARNING - Error connecting hotspot
2018-06-23 23:08:37,117 - comitup - INFO - Setting state to CONNECTING
2018-06-23 23:08:42,346 - comitup - INFO - Setting state to HOTSPOT
2018-06-23 23:08:42,551 - comitup - INFO - Activating hotspot
2018-06-23 23:08:42,683 - comitup - WARNING - Error connecting hotspot

and no comitup-xxxx wifi is being found.

I've been connecting over the wired interface and eth0 is getting an address from my router. (I just rebooted and disconnected the wired network and getting the same results by checking from the console)

I've also noticed that my interfaces are the old eth0 and wlan0 not the unique ids that some people mention they get with Stretch.

pi@comitup:~ $ nmcli
eth0: connected to eth0
        "0424 ec00"
        ethernet (smsc95xx), B8:27:EB:9F:2C:10, hw, mtu 1500
        ip4 default
        inet4 192.168.137.15/24
        inet4 192.168.137.49/24
        inet6 fe80::30b1:4ac5:d564:b93c/64

wlan0: unavailable
        "Broadcom "
        wifi (brcmfmac), 1A:D1:E1:0D:ED:AC, hw

lo: unmanaged
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 192.168.137.1
        domains: mshome.net
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details.
pi@comitup:~ $ nmcli device
DEVICE  TYPE      STATE        CONNECTION
eth0    ethernet  connected    eth0
wlan0   wifi      unavailable  --
lo      loopback  unmanaged    --
pi@comitup:~ $ sudo nmcli device show wlan0
GENERAL.DEVICE:                         wlan0
GENERAL.TYPE:                           wifi
GENERAL.HWADDR:                         1A:D1:E1:0D:ED:AC
GENERAL.MTU:                            0
GENERAL.STATE:                          20 (unavailable)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
pi@comitup:~ $ sudo nmcli device connect wlan0
Error: Failed to add/activate new connection: A 'wireless' setting is required if no AP path was given.
pi@comitup:~ $ nmcli connection
NAME                UUID                                  TYPE             DEVICE
eth0                610a5933-75ac-4b02-b542-18794fd6bbf9  802-3-ethernet   eth0
Wired connection 1  d943dc02-d073-32c3-a0c8-f61c8e4b894e  802-3-ethernet   --
comitup-3129        c9745511-ee61-4ba8-a4f3-c4437b6eee24  802-11-wireless  --
pi@comitup:~ $ sudo nmcli connection up id comitup-3129
Error: Connection activation failed: No suitable device found for this connection.
pi@comitup:~ $ nmcli connection show comitup-3129
connection.id:                          comitup-3129
connection.uuid:                        c9745511-ee61-4ba8-a4f3-c4437b6eee24
connection.stable-id:                   --
connection.interface-name:              wlan0
connection.type:                        802-11-wireless
connection.autoconnect:                 no
connection.autoconnect-priority:        0
connection.autoconnect-retries:         -1 (default)
connection.timestamp:                   0
connection.read-only:                   no
connection.permissions:
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        -1 (default)
802-11-wireless.ssid:                   comitup-3129
802-11-wireless.mode:                   ap
802-11-wireless.band:                   --
802-11-wireless.channel:                0
802-11-wireless.bssid:                  --
802-11-wireless.rate:                   0
802-11-wireless.tx-power:               0
802-11-wireless.mac-address:            --
802-11-wireless.cloned-mac-address:     --
802-11-wireless.generate-mac-address-mask:--
802-11-wireless.mac-address-blacklist:
802-11-wireless.mac-address-randomization:default
802-11-wireless.mtu:                    auto
802-11-wireless.seen-bssids:
802-11-wireless.hidden:                 no
802-11-wireless.powersave:              default (0)
ipv4.method:                            shared
ipv4.dns:
ipv4.dns-search:
ipv4.dns-options:                       (default)
ipv4.dns-priority:                      0
ipv4.addresses:
ipv4.gateway:                           --
ipv4.routes:
ipv4.route-metric:                      -1
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-timeout:                      0
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv4.dad-timeout:                       -1 (default)
ipv6.method:                            ignore
ipv6.dns:
ipv6.dns-search:
ipv6.dns-options:                       (default)
ipv6.dns-priority:                      0
ipv6.addresses:
ipv6.gateway:                           --
ipv6.routes:
ipv6.route-metric:                      -1
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.addr-gen-mode:                     stable-privacy
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.token:                             --
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --

Any ideas? It looks like wlan0 is not available to NetworkManager?

Hi,

do you think it's possible to get the devicename into the hotspot name somehow?

instead of the "comitup-82" I would like to have "device123-hotspot"

Hi David, I am testing your comitup image.

When I logon to 10.42.0.1 I enter my SSID it takes me to the unencrypted page and I cannot enter a password. I manually removed the 'un' and it worked fine, but still a tiny bug to remove.

http://10.42.0.1/confirm?ssid=XXX&encrypted=unencrypted

Hello, when I use the image provided I get totally different design, than when I use apt-get install comitup. Any possibility to change that?

Hi Dave, thanks for comitup. A painpoint I'm experiencing with comitup is a Raspberry Pi connecting to a Wi-Fi hotspot where the Internet is broken and becoming unreachable with no recourse to move off that SSID. It would be preferable to retain.

1. Can you retain the hotspot while connecting to an access point? (I know it's possible if you use the same Wi-Fi channel as target network)
2. Can you retain the Zeroconf name after connecting?
3. Can I tell comitup to revert to hotspot mode (or just keep it around), when some health check fails?

Thanks!

(Sidenote: the Tutorial/FAQ do not describe how to start comitup after installing via apt-get)

I can't install the new versions comitup from deb package - I have the error "comitup : Depends: python3-networkmanager (>= 2.0) but it is not installable".
I tried to install python-networkmanager, but have the same result.

Hi,

great package!

I'm just wondering how to integrate some css and other assets to the template to pretty up the pages?

Fresh install on Raspberry Pi Zero W.

After connecting to the Hotspot the CaptivePortal shows up. I chose my network and enter the password (if required). The trying-to-connect-page show up und after a few seconds the list of available networks shows up again.

Connecting through comitup-cli to the same network works like a charm.

Hello, I want to add a background image, however I found that i need to add something in the comitupweb.py file, something like this @app.route('/css/<path:path>') def send_css(path): return send_from_directory('templates/css', path)
how do i add an image, for eg. bg.png

Hi Dave,

I am using Comitup from verion 1.4 and updated to 1.5 now but I always encounter an issue that is on every reboot of RPI comitup hotspot shows up. Even when am in same network.

Also I have to connect multiple times with Comitup to choose SSID and to get my RPI connected with internet.

I would like to know if I have not installed it properly or doing something wrong. Am just running a GUI app on startup with /etc/profile.

Thanks

I have just installed comitup from the PPA on my fresh Raspian installation.

I have stopped systemd-resolved (#51) and restarted comitup. It spawned the wifi, I connected and used a Browser to connect to the IP address of the device (10.42.0.1).

I expected a Web interface, but I got this exception:

dbus.exceptions.DBusException

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.12 was not provided by any .service files

Traceback (most recent call last)

File "/usr/lib/python3/dist-packages/flask/app.py", line 2309, in __call__

return self.wsgi_app(environ, start_response)

File "/usr/lib/python3/dist-packages/flask/app.py", line 2295, in wsgi_app

response = self.handle_exception(e)

File "/usr/lib/python3/dist-packages/flask/app.py", line 1741, in handle_exception

reraise(exc_type, exc_value, tb)

File "/usr/lib/python3/dist-packages/flask/_compat.py", line 35, in reraise

raise value

File "/usr/lib/python3/dist-packages/flask/app.py", line 2292, in wsgi_app

response = self.full_dispatch_request()

File "/usr/lib/python3/dist-packages/flask/app.py", line 1815, in full_dispatch_request

rv = self.handle_user_exception(e)

File "/usr/lib/python3/dist-packages/flask/app.py", line 1718, in handle_user_exception

reraise(exc_type, exc_value, tb)

File "/usr/lib/python3/dist-packages/flask/_compat.py", line 35, in reraise

raise value

File "/usr/lib/python3/dist-packages/flask/app.py", line 1813, in full_dispatch_request

rv = self.dispatch_request()

File "/usr/lib/python3/dist-packages/flask/app.py", line 1799, in dispatch_request

return self.view_functions[rule.endpoint](**req.view_args)

File "/usr/share/comitup/web/comitupweb.py", line 61, in index

points = ciu_client.ciu_points()

File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__

**keywords)

File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking

message, timeout)

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.12 was not provided by any .service files

The debugger caught an exception in your WSGI application. You can now look at the traceback which led to the error.

To switch between the interactive traceback and the plaintext one, you can click on the "Traceback" headline. From the text traceback you can also create a paste of it. For code execution mouse-over the frame you want to debug and click on the console icon on the right side.

You can execute arbitrary Python code in the stack frames and there are some extra helpers available for introspection:

dump() shows all variables in the frame

dump(obj) dumps all that's known about the object

Brought to you by DON'T PANIC, your friendly Werkzeug powered traceback interpreter.

Note that I haven't don't anything else but installing the package, most notably, I haven't changed the configuration.

Hey
The new version is introducing issues in installation in Rpi Jessie
Jessie doesn't have python 3.5 yet. Only python 3.4
Manually installing Python 3.5 is not recognized by comitup.

The PI is showing a loss of networking on all interfaces when CONNECTED in the dual wifi interface "router" mode. The outage includes the Ethernet interface.

The problem persists when any of the hotspot iptables rules, 'appliance' iptables rules, or WPA kick logic are disabled.

All appears to work fine if:

• there is only one interface,
• or if there are two interfaces and appliance_mode is false

Note that the usb wifi interface configures to wlan0 on this particular system, and takes the role as hotspot.

The problem extends to older packages and OS images that did not previously have the problem.

Edit - I'm seeing (in CONNECTED single wifi interface) a situation where ethernet connectifity is not there, but the mdns/zeroconf IP discovery is working.

Edit - The introduction of the issue has been traced to the upstream router serving ipv6 DHCP.

After configuring Comitup to successfully connect to a hidden SSID, Comitup seems to discard its configuration if the hotspot goes away for a while, and does not reconnect.

Is there a way to pre-empt comitup, to always connect to a hotspot if it's available?

Alternatively, can I force nmcli to connect with a cronjob every N minutes?

After installing comitup (older and newer versions) don't create the AP networks.
Raspberry Pi Zero W.

Comitup is attempting to write to logs on startup, which prevents it from starting. This is a problem if another process filled the disk, which means you can't get it back online.

When installing using QEMU:

Setting up comitup (1.2.4-1) ...
Failed to connect to generic netlink.
Traceback (most recent call last):
File "/usr/share/comitup/comitup/wificheck.py", line 128, in
run_checks(logit=False)
File "/usr/share/comitup/comitup/wificheck.py", line 109, in run_checks
testresult = testspec.testfn()
File "/usr/share/comitup/comitup/wificheck.py", line 53, in device_supports_ap
deviceinfo = subprocess.check_output(cmd.split()).decode()
File "/usr/lib/python3.5/subprocess.py", line 316, in check_output
**kwargs).stdout
File "/usr/lib/python3.5/subprocess.py", line 398, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['iw', 'phy', 'phy0', 'info']' returned non-zero exit status 1

Hello, is there anyway for me to add a password to my hotspot?

Hello, I have been wondering how do I change the SSID for eg. comitup-<nn> -> Hello.

Hi, comitup can't stop and start apache2 service. If i stop and start it manually all works fine.
The following line is present in the file /etc/comitup.conf:
web_service: apache2.service
it seems that comitup is not able to make the switch from the wifi configuration web server to my apache2 web server. The the wifi configuration web server is always active even when wifi is connected to my router.