Re: [Freedombox-discuss] Setting up a FreedomBox on an apu1d4. Usb device (phone/modem) not seen by plinth.

2016-04-30 Thread A. F. Cano
On Tue, Apr 26, 2016 at 11:58:18PM -0400, A. F. Cano wrote:
> On Tue, Feb 16, 2016 at 11:41:37PM +0530, Sunil Mohan Adapa wrote:
> > ...
> > 2) When you connect a USB tethered phone it will show us as an Ethernet
> > device.  Which you can configure as 'external' connection in Plinth.  If
> 

Earlier I said:

> Mmm... No such luck.  The only interfaces visible to plinth are the 3
> usual ones: one internal connected to the internal network (enp3s0),
> one internal not connected (enp2s0) and the WAM interface connected to
> the ubiquiti router.  More below.

After more more trial and error, I got a little further.

I can get the ppp connection started:

$ /sbin/route
Kernel IP routing table
Destination Gateway  Genmask Flags Metric RefUse Iface
default 0.0.0.0  0.0.0.0 U 0  00  ppp0
80.sub-66-174-1 0.0.0.0  255.255.255.255 UH0  00  ppp0
192.168.200.0   0.0.0.0  255.255.255.0   U 10000  enp3s0

I can do apt updates/upgrades from the command line (via ssh)

$ sudo apt update && sudo apt upgrade   # this works

This is with the tethered phone connected directly to the freedombox'x
usb port, not via a proxy on another local machine like I described
earlier.

Per the online manual in the wiki, I tried to make the network manager
aware of the new connection:

$ sudo nmcli con add con-name "ppp" ifname "ppp0" type cdma
$ sudo nmcli con modify "ppp" connection.zone external

and the "Networks" page presented by plinth now has the "ppp" connection
listed, but it's inactive.  Clicking the "Activate" button has no
effect.  It says "Activated connection ppp" but the button never turns
green.  Tried this before and after deactivating the "Freedombox WAN"
interface, in case there is a limitation of only one external interface.

After de-activating the Freedombox WAN interface:

$ nmcli connection
NAME   UUID  TYPE
DEVICE 
FreedomBox LAN enp3s0  a8e95667-240c-48bb-98be-0ee4a97c1fc2  802-3-ethernet  
enp3s0 
FreedomBox LAN enp2s0  a7aaf4a1-a558-4cac-9f9e-a7a078492efb  802-3-ethernet  -- 

FreedomBox WAN 51461052-3d5d-4261-8b49-727dd11b6c6b  802-3-ethernet  -- 

pppf2cc6f30-1726-42c2-b580-3ac8a98a21ec  cdma-- 



$ nmcli device
 DEVICE   TYPE  STATE CONNECTION
 enp3s0   ethernet  connected FreedomBox LAN enp3s0 
 ttyACM0  cdma  disconnected  --
 enp1s0   ethernet  disconnected  --
 enp2s0   ethernet  unavailable   --
 lo   loopback  unmanaged --
 ppp0 unknown   unmanaged --   

Looks like I have some confusion as to what the network manager uses to
identify what it deals with.  Why are both ttyACM0 and ppp0 listed under
"DEVICE"?  Is there a way to associate "ttyACM0" with ppp0 under nmcli?
Is this necessary?

No surprise then that anything else is not working from the web
interface.

> > your phone only provides PPP, you will have configure that from 'nmtui'
> > from command line (Plinth does not do PPP connections yet)

Even with the ppp connection up and running, nmtui only sees the 3
ethernet connections.
> ...

Any ideas out there?


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


Re: [Freedombox-discuss] Setting up a FreedomBox on an apu1d4. Usb device (phone/modem) not seen by plinth.

2016-04-26 Thread A. F. Cano
On Tue, Feb 16, 2016 at 11:41:37PM +0530, Sunil Mohan Adapa wrote:
> ...
> 2) When you connect a USB tethered phone it will show us as an Ethernet
> device.  Which you can configure as 'external' connection in Plinth.  If

Mmm... No such luck.  The only interfaces visible to plinth are the 3
usual ones: one internal connected to the internal network (enp3s0),
one internal not connected (enp2s0) and the WAM interface connected to
the ubiquiti router.  More below.

> your phone only provides PPP, you will have configure that from 'nmtui'
> from command line (Plinth does not do PPP connections yet)

It's not visible to nmtui either.  Of course my first impulse was to run
lsusb, but it's not installed.  The only hint I get is from

$ cat /proc/devices
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
  10 misc
  13 input
  21 sg
  29 fb
  128 ptm
  136 pts
  166 ttyACM<=== this is the device
  180 usb
  189 usb_device
  251 tpm
  252 bsg
  253 watchdog
  254 rtc

and upon connection the proper device is created:

$ ls -l /dev/ttyACM0
crw-rw 1 root dialout 166, 0 Feb 11 12:30 /dev/ttyACM0

As expected, the device goes away when the usb phone is disconnected.

So, the kernel and the usb sub-system see it.

Incidentally, this is on a freshly upgraded system to 9.1 as of April 26,
2016.  I managed to update/upgrade (sudo apt update && sudo apt upgrade
per the instructions) without having an internet connection on the
outside interface by creating /etc/apt/apt.conf with this in it:

Acquire::http::Proxy "http://192.168.200.7:8118/;;

This pointed apt to an internal machine (on the internal network)
running privoxy on port 8118.  On that machine, the usb tethered phone
provided the internet connection.  Since this only re-directs apt, the
downloading of the certificates failed.

Yes, crappy solution but that's all I have at the moment.  I'd really
like to be able to use the usb tethered phone as an outside interface
on the freedombox itself, with all the services pointed to it.  Any hints?

Thanks!


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