G'day,
I hope that post will not be long, but I've spent a few hours trying to
narrow down the problem so I can provide as much information without
wasting anyone's time.
I started to debug why NetworkManager-ssh (which I maintain) does not allow
traffic through interfaces (tun interfaces
Hello again...
Having read the recent paper on Wifi tracking by Jeremy Martin, et
al[1], I am concerned this tracking problem based on non-MAC address
metadata may be present for laptop systems as well. The issues involve
WPS unique identifier fields and request sequence numbers.
There is
Hello
As done in LinSSID,
or more generally as in dmesg or journalctl,
it would be also nice addition to nmcli,
the following option.
e.g.
nmcli --follow device wifi list
Continuously list available Wi-Fi access points,
list new APs as they appear in proximity.
On Fri, 2017-04-07 at 13:43 +0100, Radu Rendec wrote:
> I'm trying to setup an IPIP tunnel using nmcli. I can create the
> tunnel
> using, e.g.:
>
> nmcli con add type ip-tunnel mode ipip ifname tun0 remote 10.0.4.1
> local 10.0.8.1
>
> And then I can assign an ipv4 address using:
>
> nmcli con
A couple of things I've noticed in integrating NM with ModemManager:
1. It seems that eth0 doesn't come up - i.e. dhcp client not fired off - until
MM has done it's startup operations on the GSM modem. It so happens that my GSM
has a long power-on pause, and that is holding up the system's eth
> On 07 April 2017 at 17:35 Dan Williams wrote:
>
> On Fri, 2017-04-07 at 17:17 +0100, Colin Helliwell wrote:
>
> > > On 07 April 2017 at 17:15 Colin Helliwell > > ms.com> wrote:
> > >
> > > > On 07 April 2017 at 17:06 Dan Williams