netGo - www.linux-apps.com

netGo

Network

Score 80%

Description:

netGo is a distribution-independent networking tool (written in Qt) for changing network settings quickly and easily. It is intended for laptop owners, who often need to change network settings when relocating.
It allows you to create 'profiles' that contain the network settings such as the IP, netmask, gateway, name servers and wireless options. After creating a profile it can be executed with a single click.

Last changelog:

13 years ago

Update: Added Debian packages and RPMS. netGo is also available in Gentoo's portage (emerge netgo).

Info Update
===========

Just wanted to let you know that I've decided to start working on a new version of netGo. The reason is all the positive feedback I've recieved and I have still got a couple of features and improvements I would like to implement in netGo. If you have any suggestions or ideas I'd be happy to hear them, now is the time.
See the updated homepage for further info: http://netgo.hjolug.org

bedahr
11 years ago

Would you consider extending your tool to include proxy on/off-switching support?

I, for example, have a notebook which I use for home and for work. At home I connect over a wireless network to an access point - without a proxy.

At work I have to use our school's proxy - and I have to reactivate it every time (and deactivate it when I come home).

So a one-click solution for switching the whole network setup from home to work would be great.

acidtonic
11 years ago

*sigh*. Reading through above I noticed the include line was also destroyed by the forum, put unistd.h inside < and >

acidtonic
11 years ago

Somehow my post got duplicated, i didnt refresh or go back. Sorry for the dupes

acidtonic
11 years ago

I noticed on my slackware laptop that the process of killing the dhcpcd daemon was moving on too quickly to the next step of starting the dhcpcd daemon again in which it would complain its still running and exit. I simply added a 2 second wait between killing the dhcpcd process and starting the new one. Now I must say this app is awesome, nothing else works very well on slackware or even compiles for most things.

In the file Process.cpp

add
#include ;
to the includes

(The code had html bold tags that get ruined by this forum, they got removed)

and then insert
browser->setText(browser->text() + "* Waiting for DHCP Process to stop on " + Profile::profiles.at(current).iface + "*linebreak*");
qWarning(green + "* Waiting for DHCP Process to stop...");

usleep(2000000.00);

right under "CURRENT_PROC = NONE;" at about line 411

Let me know what you guys think :)

acidtonic
11 years ago

I noticed on my slackware laptop that the process of killing the dhcpcd daemon was moving on too quickly to the next step of starting the dhcpcd daemon again in which it would complain its still running and exit. I simply added a 2 second wait between killing the dhcpcd process and starting the new one. Now I must say this app is awesome, nothing else works very well on slackware or even compiles for most things.

In the file Process.cpp

add
#include ;
to the includes

(The code had html bold tags that get ruined by this forum, they got removed)

and then insert
browser->setText(browser->text() + "* Waiting for DHCP Process to stop on " + Profile::profiles.at(current).iface + "*linebreak*");
qWarning(green + "* Waiting for DHCP Process to stop...");

usleep(2000000.00);

right under "CURRENT_PROC = NONE;" at about line 411

Let me know what you guys think :)

acidtonic
11 years ago

I noticed on my slackware laptop that the process of killing the dhcpcd daemon was moving on too quickly to the next step of starting the dhcpcd daemon again in which it would complain its still running and exit. I simply added a 2 second wait between killing the dhcpcd process and starting the new one. Now I must say this app is awesome, nothing else works very well on slackware or even compiles for most things.

In the file Process.cpp

add
#include ;
to the includes

(The code had html bold tags that get ruined by this forum, they got removed)

and then insert
browser->setText(browser->text() + "* Waiting for DHCP Process to stop on " + Profile::profiles.at(current).iface + "*linebreak*");
qWarning(green + "* Waiting for DHCP Process to stop...");

usleep(2000000.00);

right under "CURRENT_PROC = NONE;" at about line 411

Let me know what you guys think :)

megalex
12 years ago

will this configure WPA too ? if not is this planned ?

panzar
12 years ago

We started a discussion about WPA in the previous page, but I still haven't decided. It seems like there's a big demand for WPA support.

This would require integrating wpa_supplicant in netGo and since I'm not using wpa_supplicant myself I haven't got a clue of how it works at the moment. So, if you're a wpa_supplicant user and have suggestions or ideas about how to integrate wpa_supplicant in netGo the best way, please drop me a mail: per.j@hjolug.org

There's also a little note about WPA in the FAQ at the netGo homepage: http://netgo.hjolug.org/faq.php

probono
12 years ago

klik://netgo for those who prefer to klik :-)

(See http://klik.atekon.de/ or http://www.kde-apps.org/content/show.php?content=12841 for a description of klik)

Note that unlike other klik apps, this one requires the root password when it is run.

kennethr
12 years ago

Why option "Search domain" in NetGo convert to parameter "nameserver" otherwise "search" in file /etc/resolv.conf ? It's bug or my mistake.

panzar
12 years ago

I'm sorry, this is a known bug. I have created an entry for it in the FAQ on the netGo homepage: http://netgo.hjolug.org/faw.php

It describes how you can fix it yourself too.

kennethr
12 years ago

Thanks

eode
12 years ago

Would it be possible to modify this to work together with wpa supplicant? I don't know of *any* graphical tools that do right now. It would be nice just to click on a "use wpa supplicant for this network" box, even if it didn't configure wpa supplicant, but just started and stopped the service.. ..although, configuration would be nice, too. ;-) The newest wpa supplicant (0.4.5) has a much simpler configuration file than prior versions, for ease of getting it working you might want to use that, if you decide to use it..

panzar
12 years ago

Hm.. I've been hesitating about implementing WPA Supplicant support. The biggest reason is that it still supports a very limited amout of wlan cards. There is a solution for (the few?) people who owns a WPA Supplicant compitable card and wants to use netGo though: the "Custom script" feature. Just create a script that calls the WPA Supplicant commands and add the script to the profile.

This is definetly an interesting discussion, please tell me your opinion.

eode
12 years ago

Ah. Thanks. :-)

Val
12 years ago

I vote for wpa_supplicant! :-) Don't think that it has too few cards supprted (especially because ndis_warapper is actualy a bunch of adapters ;-) but I know not so many networks without WPA.

aleceres
12 years ago

What a great application! it would just be great if you could somehow merge this code in knemo. This would add a full control over net devices together with constant monitoring.

RockHound
13 years ago

Hi there...

Would it possible to add support for Quickswitch (http://muthanna.com/quickswitch)?

Great app otherwise. :-)

Martin

panzar
13 years ago

Hm, that's interesting.
I've never seen that app before, and to be honest I didn't think any app like that (except netGo) existed.

I don't get what you mean with "implementing support for it in netGo" since they are two separate apps doing the same thing?

Please reply if I misunderstood you :)

Val
12 years ago

Nice to hear that NetGo is up again! :)

As for quickswitch, I suggest that it is better idea to integrate with hprofile (http://hprofile.sourceforge.net/). Let me explain what I mean. As for now, NetGO uses ifconfig/route/iwconfig utilities to set up parameters and stores profile in its own files. Such setup will be lost after system reboot and every system alredy have a place where such settings are stored - /etc/rc.d or similiar. The idea is to make NetGo a frontend for console utility hprofile and let it manage profiles in accordance with distro's own settings system.

panzar
12 years ago

Hi,

thanks for the suggestion, but this has never been my intention with netGo. netGo is distro-independent in that way that it uses ifconfig, route etc. to set the network commands. It doesn't provide support for saving the network settings between restarts, you need to execute a profile at every startup. This approach is simple and works good since executing a profile is very easy and is done very fast.

Val
12 years ago

Okay, I see. Thanks for an explanation.

ming0
13 years ago

Is this KDE 3.3 compatible?

panzar
13 years ago

I don't see why Qt-apps shouldn't work on KDE :)
I'm not using KDE 3.3 myself, but I'm sure netGo would work.

drbadevil
13 years ago

Good application!

I like the idea behind the app.
However, I switch between proxied and un-proxied networks and it would be great if a support for automatic proxy configuration was included in the app.

An other issue is that one of the networks I am using requires a VPN connection. So it would be nice if there was possibility to include a VPNstart and VPNstop script in the profiles.

Best
++Robert

1
2

13 years ago

Update: Added Debian packages and RPMS. netGo is also available in Gentoo's portage (emerge netgo).

Info Update
===========

Just wanted to let you know that I've decided to start working on a new version of netGo. The reason is all the positive feedback I've recieved and I have still got a couple of features and improvements I would like to implement in netGo. If you have any suggestions or ideas I'd be happy to hear them, now is the time.
See the updated homepage for further info: http://netgo.hjolug.org

30 136

File (click to download)	Version	Description	Filetype	Packagetype	License	Downloads	Date	Filesize	OCS-Install	DL