, they will
only be probed to look for modems if Scan() is called explicitly.
Are you saying that there is no more need for acrobatics[1] regarding
analog modems and UPSes connected to the serial ports or via adapters.
poma
[1]
https://lists.fedoraproject.org/pipermail/users/2012-December/428039
On 07.06.2013 23:28, Dan Williams wrote:
On Fri, 2013-06-07 at 18:26 +0200, Aleksander Morgado wrote:
On 06/07/2013 06:16 PM, poma wrote:
Maybe in the very distant future, MM would not probe the serial
device at all - instead I imagine a serial detector software
component, that does all kind
On 09.06.2013 16:16, Aleksander Morgado wrote:
Hey Poma,
On 08/06/13 09:02, poma wrote:
OK, that can be overcome via 'ID_MM_DEVICE_IGNORE' within a custom rule.
As for this device,
http://www.koutech.com/proddetail.asp?linenumber=56[1]
'ID_MM_DEVICE_IGNORE' *must* be applied, if we want
On 10.06.2013 20:28, Aleksander Morgado wrote:
On 06/10/2013 01:55 AM, poma wrote:
I don't think we should probe devices in the 'pci' subsystem unless
whitelisted with ID_MM_PLATFORM_DRIVER_PROBE. Can you grab this patch,
replace 'pnp' with 'pci' and retest?
https://mail.gnome.org/archives
0.9.8.8-1.fc19
If conditions are met, it should work flawless.
Bee awesome.:!
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
On 28.11.2013 20:44, poma wrote:
On 28.11.2013 17:31, Karoline Haus wrote:
Hi there, I'm running a quite old ModemManager 0.4 and I'd like to
use it for connecting to a 3G data network. I'm not too sure if that
is possible and I couldn't find any suitable documentation on this
topic. Can
, anyone
can help?
https://www.redhat.com/mailman/listinfo/rhelv6-list
https://www.redhat.com/mailman/listinfo/libvirt-users
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/
poma
On 30.11.2013 10:51, Marc Murphy wrote:
Hopefully someone can help with this one.
http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Bee awesome.:!
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https
are apparently working in this way also.
Is it planned to support such a mode in the NetworkManager?
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
On 18.12.2013 00:26, Dan Williams wrote:
On Tue, 2013-12-17 at 23:50 +0100, poma wrote:
HUWAEI E1750 NDISDUP
Is the difference between the two modes just the usb_modeswitch
commands? I see they have different USB IDs between first and second
runs.
USB Modeswitch has nothing to do
, wouldn't be more convenient
e.g. 'mmcli -m 0 --simple-connect=apn=1' for the 1st entry. ;)
And of course it will be integrated with NetworkManager's nmcli just
fine as every other modem.
Super duper!
Thanks for your response, as well.
poma
On 18.12.2013 18:57, Dan Williams wrote:
On Wed, 2013-12-18 at 18:38 +0100, poma wrote:
On 18.12.2013 00:26, Dan Williams wrote:
On Tue, 2013-12-17 at 23:50 +0100, poma wrote:
HUWAEI E1750 NDISDUP
Is the difference between the two modes just the usb_modeswitch
commands? I see they have
at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
bNumConfigurations 1
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
All right!
Have a nice weekend!
poma
___
networkmanager-list
info -a -p /sys/class/net/wwp0s4f1u3i1
# udevadm info -q env /sys/class/net/wwp0s4f1u3i1
poma
In addition
# mmcli -m 0 --command=+CLAC
response: 'C
D
F
V
E
I
L
M
Q
V
X
Z
T
P
D
A
H
O
S0
S2
S3
S4
S5
S6
S7
S8
S9
S10
S11
S30
S103
S104
+FCLASS
+ICF
+IFC
+IPR
+GMI
+GMM
+GMR
+GCAP
+GSN
+DR
+DS
+WS46
+CLAC
On 31.01.2014 01:43, Yves S. Garret wrote:
…
Also, I've stopped netctl (stil does not work.) I do have a question, what
is system-netctl.slice?
man 5 systemd.slice
http://freedesktop.org/wiki/Software/systemd/
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
poma
NOPE --
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
On 23.03.2014 15:57, poma wrote:
ifcfg-rh plugin:
~~~
/etc/NetworkManager/NetworkManager.conf:
[main]
plugins=ifcfg-rh
/etc/sysconfig/network-scripts/ifcfg-enp3s0:
...
NM_CONTROLLED=no
$ nmcli device status
DEVICE TYPE STATE CONNECTION
On 23.03.2014 17:43, poma wrote:
On 23.03.2014 15:57, poma wrote:
ifcfg-rh plugin:
~~~
/etc/NetworkManager/NetworkManager.conf:
[main]
plugins=ifcfg-rh
/etc/sysconfig/network-scripts/ifcfg-enp3s0:
...
NM_CONTROLLED=no
$ nmcli device status
DEVICE TYPE
bridge name bridge id STP enabled interfaces
bridge0 8000.001234567830 no enp3s0
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo
On 25.03.2014 02:34, poma wrote:
On 23.03.2014 17:43, poma wrote:
On 23.03.2014 15:57, poma wrote:
ifcfg-rh plugin:
~~~
/etc/NetworkManager/NetworkManager.conf:
[main]
plugins=ifcfg-rh
/etc/sysconfig/network-scripts/ifcfg-enp3s0:
...
NM_CONTROLLED
-8d215387ab8b bridge
bridge0
base0enp3s09e0fafbb-5881-41ba-ab47-98c2f0700915 802-3-ethernet
enp3s0
$ brctl show
bridge name bridge id STP enabled interfaces
bridge0 8000.001234567830 no enp3s0
poma
files, so.
Everything else is up to you. ;)
poma
http://fedoraproject.org/wiki/Tools/NetworkManager
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Networking_Guide/Configure_802_1q_VLAN_Tagging_Using_the_NetworkManager_Command_Line_Tool_nmcli.html
,
The NetworkManager compared to the systemd-networkd - Bridge-static:
http://goo.gl/N9pnYe
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
'NetworkManager-config-server',
/etc/NetworkManager/conf.d/00-server.conf
...
# Ignore the carrier (cable plugged in) state when attempting to
# activate static-IP connections.
ignore-carrier=*
This option tends to break the Bonding andor Bridge DHCP setups.
Is it a bug, or a feature?
poma
git submodule update
./autogen.sh
cd ../
tar ...
Perhaps this is the reason, however it is still a mystery why are
snapshots created with a blank 'libgsystem/'!?
poma
[1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/
___
networkmanager
not a string literal and no format
arguments [-Werror=format-security]
if (!do_helper (iface, DCBTOOL, run_func, user_data, success ? error
: NULL, *iter))
^
cc1: all warnings being treated as errors
...
poma
___
networkmanager-list mailing list
On 02.04.2014 11:05, Thomas Haller wrote:
Hi,
On Wed, 2014-04-02 at 06:32 +0200, poma wrote:
Why the 'libgsystem' is used as a git submodule, and not via the system
wide setup - 'libgsystem/devel'?
Because originally libgsystem was not available in distributions (or not
recent enough
On 02.04.2014 11:18, Thomas Haller wrote:
On Wed, 2014-04-02 at 05:51 +0200, poma wrote:
'NetworkManager-config-server',
/etc/NetworkManager/conf.d/00-server.conf
...
# Ignore the carrier (cable plugged in) state when attempting to
# activate static-IP connections.
ignore-carrier
On 02.04.2014 15:51, Dan Williams wrote:
On Wed, 2014-04-02 at 08:12 -0500, Dan Williams wrote:
On Wed, 2014-04-02 at 07:29 +0200, poma wrote:
...
nm-dcb.c: In function '_dcb_setup':
nm-dcb.c:211:3: error: format not a string literal and no format
arguments [-Werror=format-security
On 02.04.2014 16:36, Dan Williams wrote:
On Wed, 2014-04-02 at 09:18 -0500, Dan Williams wrote:
Even ignore-carrier devices need to be aware of carrier-up events so
they can continue DHCP when the link comes up. They just ignore all
carrier-down events.
Acked by thaller danw on IRC,
On 02.04.2014 18:41, Thomas Haller wrote:
On Wed, 2014-04-02 at 14:03 +0200, poma wrote:
On 02.04.2014 11:05, Thomas Haller wrote:
Hi,
On Wed, 2014-04-02 at 06:32 +0200, poma wrote:
Why the 'libgsystem' is used as a git submodule, and not via the system
wide setup - 'libgsystem/devel
RTM_NEWLINK message for unmanaged link
:29:27 : enp0s4f0u2c3i8: link already exists, ignoring
:29:43 : enp0s4f0u2c3i8: received RTM_NEWLINK message for unmanaged link
Respect!
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https
As you can see in Side by Side, this is solved.
Thank you once again NM Team!
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
=NetworkManagercomponent=nm-applet
[enh] Add support to Access Point mode
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
$ rpmbuild -bp NetworkManager.spec
error: line 47: Illegal sequence .. in: Release: 10.git20140508..429023b.fc21
Signed-off-by: poma pomidorabelis...@gmail.com
---
contrib/fedora/rpm/NetworkManager.spec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/fedora/rpm
Signed-off-by: poma pomidorabelis...@gmail.com
---
src/dns-manager/nm-dns-manager.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/src/dns-manager/nm-dns-manager.c b/src/dns-manager/nm-dns-manager.c
index fe8cf6c..d0268e2 100644
--- a/src/dns-manager/nm-dns
On 11.05.2014 17:52, Thomas Haller wrote:
On Fri, 2014-05-09 at 11:57 -0500, Dan Williams wrote:
On Fri, 2014-05-09 at 05:30 +0200, poma wrote:
$ rpmbuild -bp NetworkManager.spec
error: line 47: Illegal sequence .. in: Release:
10.git20140508..429023b.fc21
Signed-off-by: poma pomidorabelis
On 09.05.2014 18:58, Dan Williams wrote:
On Fri, 2014-05-09 at 05:44 +0200, poma wrote:
Signed-off-by: poma pomidorabelis...@gmail.com
Though this really is a Fedora specific patch since it references things
that only the ifcfg-rh plugin does. So I'm not sure it's really
suitable
a message
3. Interface to view collected data and set/reset counters.
It is possible to extend this wish list, but these functions would cover most
roaming user's with limited network connection needs.
poma
Ref. app.
vnStat
http://humdi.net/vnstat
On 22.09.2014 16:30, Thomas Haller wrote:
On Mon, 2014-09-01 at 10:26 -0400, Gene Czarcinski wrote:
OK, I give up ... what is the magic dance I need to do to restore a
forgotten NIC?
I was playing with gnome's network editor and on the reset page for a
device, I hit the Forget button.
this
interface.
etc. etc.. etc...
- nmcli device
DEVICE TYPE STATECONNECTION
wlp0s4f1u1 wifi unavailable --
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo
On 29.09.2014 21:46, Dan Williams wrote:
On Mon, 2014-09-29 at 11:29 +0200, poma wrote:
[platform/nm-platform.c:806] nm_platform_link_set_up(): link: setting up
'wlp0s4f1u1' (4)
[platform/nm-linux-platform.c:2356] link_change_flags(): link: change 4:
flags set 'up' (1)
[platform/nm-linux
On 02.10.2014 12:44, Christian Lamparter wrote:
Am 02.10.2014 05:45 schrieb poma pomidorabelis...@gmail.com:
On 29.09.2014 21:46, Dan Williams wrote:
On Mon, 2014-09-29 at 11:29 +0200, poma wrote:
[platform/nm-platform.c:806] nm_platform_link_set_up(): link: setting
up 'wlp0s4f1u1' (4
If I'd only read this,
http://www.spinics.net/lists/linux-wireless/msg126108.html
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
-wext.c:160]
wifi_wext_set_mode(): (ra0): error setting mode 2
IBSS works via Wicd although not reliable.
BTW AP/WPA2, is it possible at all?
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman
On 08.10.2014 20:31, Dan Williams wrote:
On Wed, 2014-10-08 at 00:10 +0200, poma wrote:
Starting Network Manager...
info NetworkManager (version 0.9.10.0-5.git20140704.fc21) is starting...
info WEXT support is enabled
info WiFi hardware radio set enabled
info Loaded device plugin:
/usr/lib
- /etc/sysconfig/wpa_supplicant:
# Use the flag -i before each of your interfaces, like so:
# INTERFACES=-ieth1 -iwlan0
INTERFACES=
# Use the flag -D before each driver, like so:
# DRIVERS=-Dwext
DRIVERS=
# Other arguments
# -u Enable the D-Bus interface (required for use with
- /etc/wpa_supplicant/wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid=RTL8188SU(r8712u)
mode=1
psk=passphrase
}
- wpa_supplicant -ddtu -i wlp0s4f1u3 -c /etc/wpa_supplicant/wpa_supplicant.conf
-D wext
1413042118.189050:
- /etc/wpa_supplicant/wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid=MT7601U(mt7601Usta)
mode=1
psk=passphrase
}
- wpa_supplicant -ddtu -i ra0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext
1413068399.834805:
handled correctly.
Where the actual branch is, care to show a link?
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
(NETDEV_UP): wlp0s4f1u3: link is not ready
[ 1691.376981] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s4f1u3: link becomes ready
http://goo.gl/3O3Tz4
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https
On 14.10.2014 09:40, Lubomir Rintel wrote:
On Mon, 2014-10-13 at 17:06 +0200, poma wrote:
On 27.02.2013 12:12, Dan Williams wrote:
On Wed, 2013-02-27 at 10:53 +0100, Dan Winship wrote:
On 02/26/2013 08:38 PM, Jauhien Piatlicki wrote:
But when I try to 'Create New Wi-Fi Network' it tries
On 13.10.2014 17:06, poma wrote:
On 27.02.2013 12:12, Dan Williams wrote:
On Wed, 2013-02-27 at 10:53 +0100, Dan Winship wrote:
On 02/26/2013 08:38 PM, Jauhien Piatlicki wrote:
But when I try to 'Create New Wi-Fi Network' it tries to create an
Ad-Hoc connection. Where can be the problem?
nm
On 14.10.2014 16:03, poma wrote:
On 14.10.2014 13:47, poma wrote:
On 14.10.2014 09:40, Lubomir Rintel wrote:
On Mon, 2014-10-13 at 17:06 +0200, poma wrote:
On 27.02.2013 12:12, Dan Williams wrote:
On Wed, 2013-02-27 at 10:53 +0100, Dan Winship wrote:
On 02/26/2013 08:38 PM, Jauhien Piatlicki
On 14.10.2014 21:30, poma wrote:
On 14.10.2014 16:03, poma wrote:
On 14.10.2014 13:47, poma wrote:
On 14.10.2014 09:40, Lubomir Rintel wrote:
On Mon, 2014-10-13 at 17:06 +0200, poma wrote:
On 27.02.2013 12:12, Dan Williams wrote:
On Wed, 2013-02-27 at 10:53 +0100, Dan Winship wrote:
On 02
On 14.10.2014 16:03, poma wrote:
On 14.10.2014 13:47, poma wrote:
On 14.10.2014 09:40, Lubomir Rintel wrote:
On Mon, 2014-10-13 at 17:06 +0200, poma wrote:
On 27.02.2013 12:12, Dan Williams wrote:
On Wed, 2013-02-27 at 10:53 +0100, Dan Winship wrote:
On 02/26/2013 08:38 PM, Jauhien Piatlicki
Dan?
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
/devel/2014-September/202337.html
gtk3-3.14.1 - irregular appearance - nm-applet systray icons menu
https://bugzilla.redhat.com/show_bug.cgi?id=1149335
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org
On 15.10.2014 04:20, poma wrote:
On 14.10.2014 22:22, Dan Williams wrote:
On Tue, 2014-10-14 at 02:59 +0200, poma wrote:
Realtek RTL8188SU/RTL8191SU/RTL8192SU driver
https://github.com/chunkeey/rtl8192su
RTL8188SU
It looks like everything worked correctly here for AP mode, at least
from
│
│ │ │ │ mechanism.
│
├─┼─┼───┼┤
...
Not working!?
poma
___
networkmanager-list mailing list
[ 648.740663] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s4f1u3: link becomes ready
~~
# nmcli device
DEVICE TYPE STATE CONNECTION
wlp0s4f1u3 wifi connected AP
but is there a better way to do it?
poma
be explicitly set?
Whether the manual is precise enough.
man 5 nm-settings(Table 8. connection setting)
poma
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
On 28.10.2014 00:15, Lennart Poettering wrote:
On Mon, 27.10.14 23:43, poma (pomidorabelis...@gmail.com) wrote:
but is there a better way to do it?
This appears to be a kernel driver bug. Please report this issue
against the kernel driver in question, systemd is not the right place
On 30.10.2014 09:52, Lubomir Rintel wrote:
On Tue, 2014-10-28 at 00:43 +0100, poma wrote:
On 28.10.2014 00:15, Lennart Poettering wrote:
On Mon, 27.10.14 23:43, poma (pomidorabelis...@gmail.com) wrote:
but is there a better way to do it?
This appears to be a kernel driver bug. Please
Will this go sotobrazzo, otherwise what is the current state of the AP support?
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
On 10.12.2014 16:25, Dan Williams wrote:
Unfortunately the same issues as before are still an issue, WRT the
connection editor and AP mode. So at this point I don't think it will
hit 1.0.
Regardless, thank you for your work, everyone on the team.
On 06.02.2015 18:42, Ferry Toth wrote:
poma wrote:
On 05.02.2015 22:00, Ferry Toth wrote:
poma wrote:
On 05.02.2015 20:12, Ferry Toth wrote:
Would that be after a certain kernel? But I used 14.04 with kernel 3.17
(no problem) and 14.10 with 3.17 (and now 3.18)
See if it can help
On 02.02.2015 19:58, David Herrmann wrote:
Hi
On Sun, Feb 1, 2015 at 10:50 AM, poma pomidorabelis...@gmail.com wrote:
MiracleCast - Howto
Current State
[snip]
Can folks from the NetworkManager team systemd-networkd team answer
regarding the current status in this matter
On 05.02.2015 22:00, Ferry Toth wrote:
poma wrote:
On 05.02.2015 20:12, Ferry Toth wrote:
Would that be after a certain kernel? But I used 14.04 with kernel 3.17
(no problem) and 14.10 with 3.17 (and now 3.18)
See if it can help
https://wireless.wiki.kernel.org/en/users/drivers/ath9k
On 03.02.2015 18:43, David Herrmann wrote:
Hi
On Tue, Feb 3, 2015 at 6:36 PM, poma pomidorabelis...@gmail.com wrote:
On 02.02.2015 19:58, David Herrmann wrote:
As I'm not really interested in hacking on network-managers, I've
decided to stop working on MiracleCast. If, some day, there's
On 12.02.2015 03:30, poma wrote:
On 11.02.2015 21:49, Ranjan Maitra wrote:
Hi,
On a new F21 installation from scratch, I am getting the following message:
% nm-applet
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will
not be saved or shared with other applications
On 01.02.2015 10:18, poma wrote:
On 01.02.2015 05:38, poma wrote:
On 31.01.2015 17:28, Patrick O'Callaghan wrote:
I have a smart TV (Sony Bravia) and can use Android Cast Screen from my
phone or tablet to see content. Apparently it also works with the Apple
equivalent. Is there a way to do
On 05.02.2015 20:12, Ferry Toth wrote:
Would that be after a certain kernel? But I used 14.04 with kernel 3.17 (no
problem) and 14.10 with 3.17 (and now 3.18)
See if it can help
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/bugs
___
On 07.01.2015 18:29, Dan Williams wrote:
On Mon, 2015-01-05 at 19:14 +0100, Thomas Schneider wrote:
Hello!
I have installed latest version of NetworkManager and nmcli
respectively + OpenVPN plugin or NetworkManager.
user@pc1-asus:~$ apt-cache policy network-manager
network-manager:
On 20.02.2015 15:58, Garrison Ricketson wrote:
Hello all.
Recently I had some problems, my desktop would not load, and I needed
to connect online, to try to re-install , how ever normally I start my
internet connection from the desktop, and had never tried this from the
command-line,which is
On 10.04.2015 20:33, Dan Williams wrote:
On Fri, 2015-04-10 at 16:48 +0200, Valerio D'Antino wrote:
Hello Dan,
thank you for the answer.
Really, there isn't so much to explain: I only noted that the Network
Manager icon disappeared from the notification area of my panel in Xfce,
when I
On 22.04.2015 12:29, Pavlo Rudyi wrote:
On Sun, 2015-04-19 at 15:36 -0600, Chris Murphy wrote:
On Sun, Apr 19, 2015 at 2:57 PM, Dan Mossor danofs...@gmail.com
wrote:
I've noticed something else,also - I can't get F22 to see my wired
interface
to compare with wireless to see if I can
Backport to stable nm-0-9-10,
bridge device availability due to disabling 'networking' prior to reboot.
See:
https://mail.gnome.org/archives/networkmanager-list/2015-April/msg00013.html
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=568a8d1
Nevertheless systemctl restart
Backport to stable nm-0-9-10,
make it possible for non-root user to NetworkManager --help / --version.
Before:
$ NetworkManager
You must be root to run NetworkManager!
$ NetworkManager --help
You must be root to run NetworkManager!
$ NetworkManager --version
You must be root to run
On 05/11/2015 10:03 AM, Lubomir Rintel wrote:
On Fri, 2015-05-08 at 13:26 +0200, poma wrote:
$ dmesg
...
[ 61.167012] net/bridge/br_private.h:626 suspicious
rcu_dereference_check() usage!
Is this material for linux-kernel@ ?
Yes.
Lubo
This seems as a dedicated mailing list
$ dmesg
...
[ 46.016137] device enp3s0 entered promiscuous mode
[ 46.017679] bridge0: port 1(enp3s0) entered forwarding state
[ 46.018795] bridge0: port 1(enp3s0) entered forwarding state
[ 61.166921] bridge0: port 1(enp3s0) entered forwarding state
[ 61.166978]
$ nmcli networking
enabled
$ nmcli networking connectivity
full
$ brctl show
bridge name bridge id STP enabled interfaces
bridge0 8000.001234567830 no enp3s0
$ nmcli device
DEVICE TYPE STATE CONNECTION
bridge0 bridge
$ NetworkManager --version
You must be root to run NetworkManager!
$ NetworkManager --help
You must be root to run NetworkManager!
$ su
Password:
# NetworkManager --version
1.0.0-8.fc21
For comparison:
$ /usr/lib/systemd/systemd --version
systemd 216
+PAM +AUDIT +SELINUX +IMA -APPARMOR
On 07.04.2015 18:26, Aleksander Morgado wrote:
On Tue, Apr 7, 2015 at 6:17 PM, poma pomidorabelis...@gmail.com wrote:
$ ModemManager --version
** (ModemManager:4483): WARNING **: Unknown option --version
You get a warning there? No pun intended, what MM version is that?
$ rpm -q
On 07.04.2015 18:34, Lubomir Rintel wrote:
On Tue, 2015-04-07 at 18:15 +0200, poma wrote:
$ NetworkManager --version
You must be root to run NetworkManager!
$ NetworkManager --help
You must be root to run NetworkManager!
Seems it's already fixed in master.
Lubo
True.
$ src
On 07.04.2015 18:15, poma wrote:
$ NetworkManager --version
You must be root to run NetworkManager!
$ NetworkManager --help
You must be root to run NetworkManager!
$ su
Password:
# NetworkManager --version
1.0.0-8.fc21
For comparison:
$ /usr/lib/systemd/systemd --version
On 07.04.2015 18:26, poma wrote:
$ nmcli networking
enabled
$ nmcli networking connectivity
full
$ brctl show
bridge name bridge id STP enabled interfaces
bridge0 8000.001234567830 no enp3s0
$ nmcli device
DEVICE TYPE
On 07.04.2015 18:36, Aleksander Morgado wrote:
On Tue, Apr 7, 2015 at 6:28 PM, poma pomidorabelis...@gmail.com wrote:
$ ModemManager --version
** (ModemManager:4483): WARNING **: Unknown option --version
You get a warning there? No pun intended, what MM version is that?
$ rpm -q
On 07.04.2015 22:18, Dan Williams wrote:
On Tue, 2015-04-07 at 18:47 +0200, poma wrote:
On 07.04.2015 18:26, poma wrote:
$ nmcli networking
enabled
$ nmcli networking connectivity
full
$ brctl show
bridge name bridge id STP enabled interfaces
bridge0
On 04.06.2015 13:46, Tony Espy wrote:
On 06/04/2015 03:38 AM, poma wrote:
On 04.06.2015 02:37, Tony Espy wrote:
On 06/03/2015 04:24 PM, Pieter Cardoen wrote:
I've tested it with WiFi but I also need to know the behaviour of the
wwan case. WiFi scanning interval was set to 10 seconds. I'll try
On 04.06.2015 02:37, Tony Espy wrote:
On 06/03/2015 04:24 PM, Pieter Cardoen wrote:
I've tested it with WiFi but I also need to know the behaviour of the
wwan case. WiFi scanning interval was set to 10 seconds. I'll try it
again tomorrow and verify the scan interval in advance.
The
NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5
This does not work:
By default, NetworkManager creates a temporary wired connection for any
Ethernet device
that is managed and doesn't have a connection configured.
Known bug?
___
networkmanager-list
On 22.06.2015 18:36, poma wrote:
NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5
This does not work:
By default, NetworkManager creates a temporary wired connection for any
Ethernet device
that is managed and doesn't have a connection configured.
Known bug?
NetworkManager journal
On 24.06.2015 21:53, Thomas Haller wrote:
On Wed, 2015-06-24 at 20:08 +0200, poma wrote:
NetworkManager-1.0.4-0.1.git20160624.f245b49a
PASSED
Good to know. Thank you for testing...
But locking at the history (git diff 8cffaf3bf5 f245b49a), it's not
clear to me why it was broken
On 24.06.2015 14:29, Thomas Haller wrote:
On Mon, 2015-06-22 at 18:36 +0200, poma wrote:
NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5
This does not work:
By default, NetworkManager creates a temporary wired connection for
any Ethernet device
that is managed and doesn't have a connection
NetworkManager-1.0.4-0.1.git20160624.f245b49a
PASSED
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
http://fedoramagazine.org/f23-networkmanager-test-day-august-20th
https://fedoraproject.org/wiki/Test_Day:2015-08-20_NetworkManager#Mobile_connectivity
https://fedoraproject.org/wiki/QA/TestCases/NM_Mobile_Broadband
TestCases/NM Mobile Broadband
The ability of NetworkManager to establish a
On 19.08.2015 15:24, Lubomir Rintel wrote:
On Wed, 2015-08-19 at 11:14 +0200, poma wrote:
On 18.08.2015 15:24, Lubomir Rintel wrote:
On Sun, 2015-08-16 at 09:54 +0200, poma wrote:
...
Fedora 23 - mobile broadband components versions:
- ModemManager-1.4.6-2.fc23.x86_64
- libqmi-1.12.4-3.fc23
On 18.08.2015 15:24, Lubomir Rintel wrote:
On Sun, 2015-08-16 at 09:54 +0200, poma wrote:
...
Fedora 23 - mobile broadband components versions:
- ModemManager-1.4.6-2.fc23.x86_64
- libqmi-1.12.4-3.fc23.x86_64
- libmbim-1.12.0-2.fc23.x86_64
- usb_modeswitch-2.2.1-2.fc23.x86_64
While testing NetworkManager's applet/con-con editor super duper Hotspot
feature, I noticed:
Hotspot:
# journalctl
[ 100.890742] hotspot dnsmasq-dhcp[1162]: DHCPREQUEST(wlp0s6f7u2) 10.42.0.87
00:0a:1b:2c:3d:4e
[ 100.891790] hotspot dnsmasq-dhcp[1162]: DHCPACK(wlp0s6f7u2) 10.42.0.87
1 - 100 of 164 matches
Mail list logo
