Prev: src/usr.sbin/portsnap .cvs & .svn directories.
Next: graphics/sane-backends 1.0.21 fails
From: Matthias Andree on 27 May 2010 11:19
Am 26.05.2010 22:24, schrieb Jerry:

> I inquired about it a month or so ago. Other posters replied favorable
> regarding it. However, since there is a dearth of drivers for any of the
> newer chip sets that support the 'N' wireless protocol, it might well
> be of limited usefulness.

Porting NetworkManager is *not* going to repair the absense of a driver.

--
Matthias Andree
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Jerry on 27 May 2010 19:28
On Thu, 27 May 2010 17:19:50 +0200
Matthias Andree <matthias.andree(a)gmx.de> articulated:


> Am 26.05.2010 22:24, schrieb Jerry:
>
> > I inquired about it a month or so ago. Other posters replied
> > favorable regarding it. However, since there is a dearth of drivers
> > for any of the newer chip sets that support the 'N' wireless
> > protocol, it might well be of limited usefulness.
>
> Porting NetworkManager is *not* going to repair the absense of a
> driver.

Precisely my point.

--
Jerry
FreeBSD-Ports.user(a)seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: David DEMELIER on 28 May 2010 06:11
2010/5/26 Matthias Andree <mandree(a)freebsd.org>:
> Am 26.05.2010 14:19, schrieb Jesse Smith:
>> I was told that requests for new ports should be submitted here. There's
>> one tool which I would like to see brought into the Ports system and
>> that's Network Manager
>> (http://fedoraproject.org/wiki/Tools/NetworkManager)
>>
>> It's the only networking tool I've found so far which will properly
>> handle my Novatel mobile modem and I would really like to be able to
>> make use of the modem while running FreeBSD.
>
> Hi Jesse,
>
> Network Manager (NM) will just automate steps you can do with other means, too.
> It is not doing magic of any kind, and chances are your modem needs firmware
> that is available for Linux but not for FreeBSD, but I know nothing about your
> Novatel device.
>
> Regarding a FreeBSD port:
>
> (a) NM needs major porting efforts, and is an open, non-trivial, project of the
> GNOME team, see <http://www.freebsd.org/gnome/docs/volunteer.html>
>
> (b) I personally find that NM is an abomination that - particularly on Laptops -
> causes more problems than it could possibly solve for me.
>    I routinely deinstall NetworkManager from openSUSE, Fedora, and Ubuntu Linux
> distributions, because it frequently fails to configure WPA2-Enterprise with
> EAP-TLS or EAP-TTLS, fails to detect online state (making several applications
> start in offline mode or refuse to even attempt to connect), fails to configure
> hidden 802.11 (WiFi/WLAN) networks, and causes other artifacts I don't have
> without NM.
>
> I'd personally also say Network Manager needs upstream bugfixing much more than
> a port. Haven't tried Fedora 13 "Goddard" yet though.
>

I agree, personally I would prefer a wpa_supplicant / dhclient
graphical user interface instead of the sucky NetworkManager. For the
moment there is sysutils/wifimgr iirc but it's a quite unstable.

wpa_supplicant does everything, scanning for access points
automatically even you don't have X running, all WPA means of
associations, it's just perfect.

--
Demelier David
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Lars Engels on 28 May 2010 06:19
On Fri, May 28, 2010 at 12:11:10PM +0200, David DEMELIER wrote:
>
> I agree, personally I would prefer a wpa_supplicant / dhclient
> graphical user interface instead of the sucky NetworkManager. For the
> moment there is sysutils/wifimgr iirc but it's a quite unstable.
>
> wpa_supplicant does everything, scanning for access points
> automatically even you don't have X running, all WPA means of
> associations, it's just perfect.

Take a look at this:
> make -C /usr/ports quicksearch name=pcbsd-
Port: pcbsd-netmanager-8.0_1
Path: /usr/ports/net/pcbsd-netmanager
Info: PC-BSD Networking Utilities for KDE4

From: James Butler on 28 May 2010 20:42
On 28 May 2010 22:19, Lars Engels <lars.engels(a)0x20.net> wrote:
> On Fri, May 28, 2010 at 12:11:10PM +0200, David DEMELIER wrote:
>>
>> I agree, personally I would prefer a wpa_supplicant / dhclient
>> graphical user interface instead of the sucky NetworkManager. For the
>> moment there is sysutils/wifimgr iirc but it's a quite unstable.
>>
>> wpa_supplicant does everything, scanning for access points
>> automatically even you don't have X running, all WPA means of
>> associations, it's just perfect.
>
> Take a look at this:
>> make -C /usr/ports quicksearch name=pcbsd-
> Port:   pcbsd-netmanager-8.0_1
> Path:   /usr/ports/net/pcbsd-netmanager
> Info:   PC-BSD Networking Utilities for KDE4
>

Or (still QT4-based, but doesn't depend on KDE libs) net/wpa_gui - not
that I've actually tried it.

I briefly had a look at what would be required to implement a basic
PyGTK-based wpa_supplicant GUI. One annoying thing is that (arguably)
the easiest way for an external app to communicate with wpa_supplicant
is via dbus, but wpa_supplicant in FreeBSD is built without dbus
support; another option would be to use something like
http://projects.otaku42.de/browser/python-wpactrl.

-James Butler
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

First  |  Prev  | 
Pages: 1 2
Prev: src/usr.sbin/portsnap .cvs & .svn directories.
Next: graphics/sane-backends 1.0.21 fails