464XLAT CLAT implementation available
Hi list, Since we were discussing 464XLAT/CLAT on this list not long ago, I thought you'd be interested in knowing that I've just published an implementation it to https://github.com/toreanderson/clatd/. It integrates with systemd/upstart/NetworkManager (using a dispatcher script) to automatically enable/disable the CLAT when appropriate. TAYGA (http://www.litech.org/tayga) is used for the actual RFC 6145 IPv4<->IPv6 translations in the same way we discussed before. If you'd like to play with it, but your ISP doesn't support NAT64/DNS64, there are a few public instances available which you can configure clatd to use instead: http://ipv6.lt/nat64_en.php http://go6lab.si/current-ipv6-tests/nat64dns64-public-test/ http://www.trex.fi/2011/dns64.html Tore ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ZTE MF60 3G Modem Not Working with ModemManager/NetworkManager
On Mon, Mar 10, 2014 at 7:12 PM, Dan Williams wrote: >> Hi all, >> >> I've been trying to get a ZTE MF60 3G modem working with MM/NM but even >> though recent updates have provided some progress it's still quite not >> working. It's not explicitly listed in the page of Supported Devices [1] >> so I'm not sure whether there is some fundamental problem with the >> device or is this merely a fixable issue somewhere in the stack. > > Posted an update to the bug, at the moment it looks like the device > simply doesn't respond to the StartNetwork request via QMI. Some of the > early hotspots are known not to implement QMI well, but I think we'll > want to test with a Gobi 1K (which is also NAS 1.0 and very early QMI) > just to make sure that still works. Yeah, known issue. The MF60 doesn't play well with the WDS service in QMI; see http://lists.freedesktop.org/archives/libqmi-devel/2012-July/98.html Quoting Bjørn: "3G connection management is done using the built-in web server. Does not look like it can be managed by QMI. But many QMI_NAS and QMI_DMS commands are supported." I actually bought a MF60 mysef in ebay to test it, but the firmware it comes with doesn't allow USB connection, only works as MiFi device... :/ May try to reflash it with some firmware that allows QMI one day... or otherwise re-sell it in ebay... Anyway, I actually delayed QMI support in the ZTE plugin just because of this device. MM 1.2 now allows QMI for ZTE devices, but we should probably setup that blacklist that we talked about some months ago, for devices like this one. -- Aleksander https://aleksander.es ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ZTE MF60 3G Modem Not Working with ModemManager/NetworkManager
On Mon, 2014-03-10 at 19:00 +0200, Marko Myllynen wrote: > Hi all, > > I've been trying to get a ZTE MF60 3G modem working with MM/NM but even > though recent updates have provided some progress it's still quite not > working. It's not explicitly listed in the page of Supported Devices [1] > so I'm not sure whether there is some fundamental problem with the > device or is this merely a fixable issue somewhere in the stack. Posted an update to the bug, at the moment it looks like the device simply doesn't respond to the StartNetwork request via QMI. Some of the early hotspots are known not to implement QMI well, but I think we'll want to test with a Gobi 1K (which is also NAS 1.0 and very early QMI) just to make sure that still works. Dan > I've uploaded system log output to [2] and debugging output to [3] based > on instructions at [4]. It seems that some properties are read > successfully (like signal strength) but the connection is never properly > established. > > Any help would be much appreciated. > > 1) http://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ > 2) https://bugzilla.redhat.com/show_bug.cgi?id=817504#c13 > 3) https://bugzilla.redhat.com/attachment.cgi?id=872797 > 4) http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ > > The versions I've used recently are: > > ModemManager-1.2.0-1.fc21 > ModemManager-glib-1.2.0-1.fc21 > NetworkManager-0.9.9.0-30.git20131003.fc20 > NetworkManager-glib-0.9.9.0-30.git20131003.fc20 > kernel-3.13.3-201.fc20 > libqmi-1.8.0-1.fc21 > usb_modeswitch-1.2.7-3.fc20 > > Thanks, > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [patch NetworkManager] ifcfg-rh writer: do not se TYPE for team ports
Mon, Mar 10, 2014 at 07:11:01PM CET, d...@redhat.com wrote: >On Sat, 2014-03-08 at 12:48 +0100, Jiri Pirko wrote: >> The problem is that initscripts rewrite DEVICETYPE in case TYPE is specified >> which prevents team port from being configured. Fix this by removing TYPE. >> >> Signed-off-by: Jiri Pirko >> >> diff --git a/src/settings/plugins/ifcfg-rh/writer.c >> b/src/settings/plugins/ifcfg-rh/writer.c >> index baa851a..b687bee 100644 >> --- a/src/settings/plugins/ifcfg-rh/writer.c >> +++ b/src/settings/plugins/ifcfg-rh/writer.c >> @@ -1742,6 +1742,7 @@ write_connection_setting (NMSettingConnection *s_con, >> shvarFile *ifcfg) >> else if (nm_setting_connection_is_slave_type (s_con, >> NM_SETTING_TEAM_SETTING_NAME)) { >> svSetValue (ifcfg, "TEAM_MASTER", master, FALSE); >> svSetValue (ifcfg, "DEVICETYPE", TYPE_TEAM_PORT, FALSE); >> +svSetValue (ifcfg, "TYPE", NULL, FALSE); >> } >> } > >Looks good. This is being followed in Red Hat bug 1074160 and the >jk/rh1074160-team-port branch, FWIW. Cheers Dan. Just note that the follow-up read patch is needed as well. > >Dan > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [patch NetworkManager] ifcfg-rh reader: assume type for Team ports
On Mon, 2014-03-10 at 13:07 +0100, Jiri Pirko wrote: > Initscripts compatibility requires that if DEVICETYPE is set, TYPE shall > not be set. So do something similar we already do for Team masters for > Team ports. > > Signed-off-by: Jiri Pirko > --- > src/settings/plugins/ifcfg-rh/reader.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/src/settings/plugins/ifcfg-rh/reader.c > b/src/settings/plugins/ifcfg-rh/reader.c > index ebf2975..dd9a3fe 100644 > --- a/src/settings/plugins/ifcfg-rh/reader.c > +++ b/src/settings/plugins/ifcfg-rh/reader.c > @@ -4999,6 +4999,8 @@ connection_from_file (const char *filename, > if (devtype) { > if (!strcasecmp (devtype, TYPE_TEAM)) > type = g_strdup (TYPE_TEAM); > + if (!strcasecmp (devtype, TYPE_TEAM_PORT) && !type) > + type = g_strdup (TYPE_ETHERNET); > g_free (devtype); > } Thanks! As with the other one, this is being followed in Red Hat bug 1074160 and the jk/rh1074160-team-port branch, where Jirka has added some testcases too. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [patch NetworkManager] ifcfg-rh writer: do not se TYPE for team ports
On Sat, 2014-03-08 at 12:48 +0100, Jiri Pirko wrote: > The problem is that initscripts rewrite DEVICETYPE in case TYPE is specified > which prevents team port from being configured. Fix this by removing TYPE. > > Signed-off-by: Jiri Pirko > > diff --git a/src/settings/plugins/ifcfg-rh/writer.c > b/src/settings/plugins/ifcfg-rh/writer.c > index baa851a..b687bee 100644 > --- a/src/settings/plugins/ifcfg-rh/writer.c > +++ b/src/settings/plugins/ifcfg-rh/writer.c > @@ -1742,6 +1742,7 @@ write_connection_setting (NMSettingConnection *s_con, > shvarFile *ifcfg) > else if (nm_setting_connection_is_slave_type (s_con, > NM_SETTING_TEAM_SETTING_NAME)) { > svSetValue (ifcfg, "TEAM_MASTER", master, FALSE); > svSetValue (ifcfg, "DEVICETYPE", TYPE_TEAM_PORT, FALSE); > + svSetValue (ifcfg, "TYPE", NULL, FALSE); > } > } Looks good. This is being followed in Red Hat bug 1074160 and the jk/rh1074160-team-port branch, FWIW. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
ZTE MF60 3G Modem Not Working with ModemManager/NetworkManager
Hi all, I've been trying to get a ZTE MF60 3G modem working with MM/NM but even though recent updates have provided some progress it's still quite not working. It's not explicitly listed in the page of Supported Devices [1] so I'm not sure whether there is some fundamental problem with the device or is this merely a fixable issue somewhere in the stack. I've uploaded system log output to [2] and debugging output to [3] based on instructions at [4]. It seems that some properties are read successfully (like signal strength) but the connection is never properly established. Any help would be much appreciated. 1) http://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ 2) https://bugzilla.redhat.com/show_bug.cgi?id=817504#c13 3) https://bugzilla.redhat.com/attachment.cgi?id=872797 4) http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ The versions I've used recently are: ModemManager-1.2.0-1.fc21 ModemManager-glib-1.2.0-1.fc21 NetworkManager-0.9.9.0-30.git20131003.fc20 NetworkManager-glib-0.9.9.0-30.git20131003.fc20 kernel-3.13.3-201.fc20 libqmi-1.8.0-1.fc21 usb_modeswitch-1.2.7-3.fc20 Thanks, -- Marko Myllynen ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
[patch NetworkManager] ifcfg-rh reader: assume type for Team ports
Initscripts compatibility requires that if DEVICETYPE is set, TYPE shall not be set. So do something similar we already do for Team masters for Team ports. Signed-off-by: Jiri Pirko --- src/settings/plugins/ifcfg-rh/reader.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/settings/plugins/ifcfg-rh/reader.c b/src/settings/plugins/ifcfg-rh/reader.c index ebf2975..dd9a3fe 100644 --- a/src/settings/plugins/ifcfg-rh/reader.c +++ b/src/settings/plugins/ifcfg-rh/reader.c @@ -4999,6 +4999,8 @@ connection_from_file (const char *filename, if (devtype) { if (!strcasecmp (devtype, TYPE_TEAM)) type = g_strdup (TYPE_TEAM); + if (!strcasecmp (devtype, TYPE_TEAM_PORT) && !type) + type = g_strdup (TYPE_ETHERNET); g_free (devtype); } -- 1.8.5.3 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list