netcfg v2.0.3

iphitus · 2008-01-11 02:11:58

zenlord wrote:

iphitus wrote:
Either way, if scan isnt showing anything as root, that's a driver bug, not netcfg and should be reported to the driver's developers.
Reported: http://bughost.org/bugzilla/show_bug.cgi?id=1499#c10
As I'm very new to reporting bugs (and even Linux in general) I hope I did it in the correct way.
Zl.

As root do ifconfig wlan0 up, THEN do iwlist wlan0 scan. The up is needed to enable to device.

Pierre · 2008-01-11 12:22:54

iphitus wrote:

ok thanks for the testing guys.
Pierre
* What is this "last" link for?
Someone wanted a record of the last network they connected to, so i created that symlink. Seems i didnt think it through enough... I'll change it in the next release.
Could you try removing the 'last' symlink, and then remove lines 210 and 211 in /usr/lib/network/network.subr? Then make sure there's no traces to last in /var/run/network.

OK, this seems to work correctly now.

zyghom · 2008-01-11 12:45:00

finally I got it working but few suggestions:
1-profiles are ok - working - but what if I want to roam with my laptop - I don't see (yet?) possibility for browsing WiFi networks
2-how to sort profiles in menu ? I tried by changing i.e. wlan to 1-wlan and lan to 2-lan just to get first wlan on the list but netcfg2 ignors me ;-), ok, defaultmenu works great but in case of more profiles it would be nice to make them sorted
3-auto-wireless does not want to cooperate:

23:39:38 root@baboon:/home/papio# netcfg-auto-wireless wlan0
/usr/bin/netcfg-auto-wireless: line 12: : No such file or directory
No network found

23:39:53 root@baboon:/home/papio# netcfg2 -v
netcfg v2.0.3
23:40:13 root@baboon:/home/papio#

4-when I want to switch between profile wlan to lan and it fails then still wlan is working - so it does not seem that POST_DOWN directive is working in such case (in normal case it does)

5-when any switching fails and link "last" is lost then the only way to make it working (menu) again is to recreate link
6-when netcfg2 makes link it is somehow having two slashes:

23:48:05 root@baboon:/etc/network.d# ls -la last
lrwxrwxrwx 1 root root 20 2008-01-10 23:46 last -> /etc/network.d//wlan
23:48:12 root@baboon:/etc/network.d#

7-when restarting menu and moving highlighting then timer does not stop - it still chooses the "last" when timout occurs

Blind · 2008-01-12 03:37:28

Hey there,

the one with the "last" would be me. Actually, this works well here...

Just wanted to say thanks for your work!

Cheers,
Blind

iphitus · 2008-01-12 08:14:40

zyghom wrote:

finally I got it working but few suggestions:
1-profiles are ok - working - but what if I want to roam with my laptop - I don't see (yet?) possibility for browsing WiFi networks

The required "stuff" is there, it wouldnt be to difficult to make, but it's not on my todo list

2-how to sort profiles in menu ? I tried by changing i.e. wlan to 1-wlan and lan to 2-lan just to get first wlan on the list but netcfg2 ignors me ;-), ok, defaultmenu works great but in case of more profiles it would be nice to make them sorted

iirc I just use find, I'll set it to use alphabetical explicitly.

3-auto-wireless does not want to cooperate:
23:39:38 root@baboon:/home/papio# netcfg-auto-wireless wlan0
/usr/bin/netcfg-auto-wireless: line 12: : No such file or directory
No network found

Yeah, known problem. Pretty sure it happens when netcfg-auto-wireless doesnt find any networks anyway -- so it's a mostly harmless error.

4-when I want to switch between profile wlan to lan and it fails then still wlan is working - so it does not seem that POST_DOWN directive is working in such case (in normal case it does)

You need to take your wlan profile down FIRST, and then enable lan. They're different devices and netcfg does _not_ do this for you (and will not).

5-when any switching fails and link "last" is lost then the only way to make it working (menu) again is to recreate link
6-when netcfg2 makes link it is somehow having two slashes:

I'll be removing last and doing it differently. Too many problems caused by making a symlink.

7-when restarting menu and moving highlighting then timer does not stop - it still chooses the "last" when timout occurs

Odd. That might be a bug in dialog, i'll have to look at that.

zyghom · 2008-01-12 08:32:11

iphitus wrote:

The required "stuff" is there, it wouldnt be to difficult to make, but it's not on my todo list

but in that case netcfg2 will not be usefull in general cases - only for predefined profiles (home-wlan, office-lan-static, office-lan-dhcp etc)
if it can browse - choose - from available netwoks than it would be full replacement for networkmanager what would be perfect anyway ;-)
or even wicd

iphitus · 2008-01-12 11:07:13

zyghom wrote:

iphitus wrote:
The required "stuff" is there, it wouldnt be to difficult to make, but it's not on my todo list
but in that case netcfg2 will not be usefull in general cases - only for predefined profiles (home-wlan, office-lan-static, office-lan-dhcp etc)
if it can browse - choose - from available netwoks than it would be full replacement for networkmanager what would be perfect anyway ;-)
or even wicd

most wireless users deal with predefined networks, with maybe an occasional new one.

Regardless, like I sad, it'd be dead easy to build a network browser, all the code in netcfg is re-usable. Create a new script, source usr/lib/network/wireless.subr, use "list_networks" to get a list of networks, pass those to "dialog", get a wireless key, and connect -- easy!

But it's not on my todo list, patches welcome.

James

Last edited by iphitus (2008-01-12 11:14:44)

ralvez · 2008-01-12 18:52:47

For the past few days whenever I run pacman -S testing/netcfg it tells me that my version is 2.0.1 and that I'm up to date but the version posted here is labeled as 2.0.3
am I doing something wrong?

R.

Fackamato · 2008-01-12 23:30:04

I have eth0 and wlan0, connected to the same router (eth0 cable and wlan0 wireless, you guessed it! ), and I'd like to have a failover mechanism on boot. I have two working netcfg2 profiles, one for ethernet and one for wireless. Both connect correctly. How would I do, if I want Archlinux to first try the wlan connection, then failover to the lan connection, on boot? I.e. (kernel boot.. scripts.. up with network, checking for wireless connectivity.. no? use ethernet > done).

If this would be possible with bonding, it would be even better! Is there currently a way?

iphitus · 2008-01-13 09:02:45

Fackamato: Could do it with bonding -- I did in a way earlier revision of the network profiles. In this case, it'd be easier to just let netcfg2 do the work.

By default, netcfg2 uses mii-tool on ethernet connections to check if a cable is present. And if you set SCAN="on" in the wireless profile, it won't connect unless the wireless network is there. If you have a network with a hidden SSID, SCAN wont work... you'll have to set it to off, it'll work, just a tad slower.

So really, you could just set NETWORKS=(somewireless someethernet)

And netcfg should handle the rest fine.

iphitus · 2008-01-13 10:22:41

ralvez wrote:

For the past few days whenever I run pacman -S testing/netcfg it tells me that my version is 2.0.1 and that I'm up to date but the version posted here is labeled as 2.0.3
am I doing something wrong?
R.

on Arch64? I didnt update it because of the problems already shown on Arch32.

Just released v2.0.5 (I didnt like 2.0.4, but its in git if you're curious), and on both Arch64 and Arch32

- Made the output of the auto script all nice and tidy,
- fixed Error 12 File Not Found
- set netcfg-menu to sort alphabetically,
- removed the buggy "last profile" option, I will re-add it in the future.

Enjoy!

James

Last edited by iphitus (2008-01-13 10:35:17)

ralvez · 2008-01-13 17:24:05

James,

Nope on Arch 32. That's why I'm asking. I uncommented testing and the testing mirrors ,like I did before, but this time when I issued pacman -S netcfg I get a message that I'm up to date: "do I want to upgrade anyway Y/n". That's odd, I think, since it should see version 2.03 in the servers.

Nevertheless, thanks for the great work ... eventually I'll get (I hope )

R.

iphitus · 2008-01-13 23:00:29

ralvez wrote:

James,
Nope on Arch 32. That's why I'm asking. I uncommented testing and the testing mirrors ,like I did before, but this time when I issued pacman -S netcfg I get a message that I'm up to date: "do I want to upgrade anyway Y/n". That's odd, I think, since it should see version 2.03 in the servers.
Nevertheless, thanks for the great work ... eventually I'll get (I hope )
R.

Slow mirrors then, just grab it from another.

barebones · 2008-01-14 18:51:19

I haven't tried auto-connect yet, but everything else seems to be working well with arch64 here for me. Thanks Iphitus.

cu3edweb · 2008-01-14 19:35:55

I updated to 2.0.5 and all is working great except I have to do ifconfig wlan0 up before auto-connect will work. I did get auto-connect to work when I put wlan0 in the INTERFACES section of the rc.conf and also set wlan0="dhcp" but then the boot up process took awhile, It looked like it was trying to set wlan0 up before the auto-connect even started if that makes sense.

cu3edweb · 2008-01-15 22:48:44

cu3edweb wrote:

I updated to 2.0.5 and all is working great except I have to do ifconfig wlan0 up before auto-connect will work. I did get auto-connect to work when I put wlan0 in the INTERFACES section of the rc.conf and also set wlan0="dhcp" but then the boot up process took awhile, It looked like it was trying to set wlan0 up before the auto-connect even started if that makes sense.

Still not sure how to set this up so the auto-connect will work

bangkok_manouel · 2008-01-17 17:32:25

Not sure if that's a bug or feature but here's the report anyway:

In /etc/rc.conf:

NETWORKS=(ethernet wpa)

using wired connection, i was expecting wireless to fail but it doesn't. Here's what ifconfig says:

eth0      Link encap:Ethernet  HWaddr 00:1D:60:62:06:C1  
          inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:41752 (40.7 Kb)  TX bytes:11328 (11.0 Kb)
          Interrupt:18 Base address:0xa000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:1B:77:D5:28:A8  
          inet addr:192.168.2.102  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:90 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:29075 (28.3 Kb)  TX bytes:1449 (1.4 Kb)

wmaster0  Link encap:UNSPEC  HWaddr 00-1B-77-D5-28-A8-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

I end up with two IP addresses.

Evoreth · 2008-01-19 18:35:59

It works flawlessly with my Netgear MA521 PCMCIA card, using ndiswrapper and wpa. The connection seems to be much more stable than with networkmanager. Thanks iphitus!

Fackamato · 2008-01-20 10:55:32

bangkok_manouel wrote:

Not sure if that's a bug or feature but here's the report anyway:

In /etc/rc.conf:

NETWORKS=(ethernet wpa)

using wired connection, i was expecting wireless to fail but it doesn't. Here's what ifconfig says:

eth0      Link encap:Ethernet  HWaddr 00:1D:60:62:06:C1  
          inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:41752 (40.7 Kb)  TX bytes:11328 (11.0 Kb)
          Interrupt:18 Base address:0xa000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:1B:77:D5:28:A8  
          inet addr:192.168.2.102  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:90 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:29075 (28.3 Kb)  TX bytes:1449 (1.4 Kb)

wmaster0  Link encap:UNSPEC  HWaddr 00-1B-77-D5-28-A8-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

I end up with two IP addresses.

I think it's supposed to do that, since that's normal network behaviour. BUT, it would be nice, if netcfg2 could skip the second connection if the first one succeeds (IMO)

Mo · 2008-01-22 12:38:09

I got a few issues with netcfg v2.0.5 and my ppp-connection.
Here is the ppp.subr which is working for me: http://pastebin.archlinux.org/24642

Wouldn't it make sense if the PEER-setting in the profile would be the name of the profile and not the path to it (e.g. "pppoe" instead of "/etc/ppp/peers/pppoe")? Maybe we could get rid of the basename-calls then. I can take a look for a patch at this if you want.

EDIT:

Fackamato wrote:

I think it's supposed to do that, since that's normal network behaviour. BUT, it would be nice, if netcfg2 could skip the second connection if the first one succeeds (IMO)

Yes, that would be really nice. Something like

auto-wifi
if (wifi not connected) 
    connect to ppp
if (ppp not connected)
   connect to default ethernet

Last edited by Mo (2008-01-22 12:49:31)

Moo-Crumpus · 2008-01-22 14:03:05

I have no problems running netcfg2 manually with my ipw2200.
But it does not start at boot - allthough the daemon net-profile is added in rc.conf.

I did:

ln -s /etc/network.d/mywlan /etc/net-profiles/mywlan

and changed the file rc.conf to look like

...
NET_PROFILES=(mywlan)
...
DAEMONS=(syslog-ng ifplugd network netfs net-profiles  ...

awagner · 2008-01-22 14:35:39

These are all my network-relevant rc.conf settings and I seem to be able to use my ethernet LAN just fine:

HOSTNAME="apollo"
NETWORKS=(homelan)
DAEMONS=(syslog-ng @net-profiles hal hibernate-cleanup @cpufreq @spamd @privoxy @cups @alsa @crond @archstatsrc )

...or am I going to run into problems, say with wireless, because I have left out the network daemon?
(In fact, I have had some wireless problems yesterday where the AP association seemed not to hold for long and I couldnt get anything via dhc(lient|pcd). With ndiswrapper/wpa on Arch64 that is. But I suppose making sure the above is okay before trying to debug the wlan again is ok. It'll be another week before I'm at the wlan again anyway.)

TIA,
Andreas

Moo-Crumpus · 2008-01-22 16:10:11

net-profiles does little. It only disconnects sessions I started by command line.

iphitus · 2008-01-22 21:05:50

Sorry for the slow response, have been away for a week.

cu3edweb: Add PRE_UP="ifconfig $INTERFACE up" to your config. Odd though, as netcfg already does ifconfig interface up.

bangkok_manouel: It's not a bug, but I can see your complaint. Regardless, you do end up with a working internet connection, even though both are connected. I'll add an option like Fackamato suggests.

Evoreth: Thanks!

Mo: Thanks a bunch for that!
As for the suggestion, you can acheive the same affect by just doing NETWORKS=(auto-wireless wlan0 ppp ethernet). If they're going to fail, they're going to fail.

Moo-Crumpus: It's NETWORKS=() not NET_PROFILES=() in /etc/rc.conf. The new netcfg has a different profile syntax, and it's not compatible with the old.

awagner: It's safe to leave out "network".

Last edited by iphitus (2008-02-13 08:50:57)

bangkok_manouel · 2008-01-23 04:15:17

Iphitus wrote:

bangkok_manouel: It's not a bug, but I can see your complaint. Regardless, you do end up with a working internet connection, even though both are connected. I'll add an option like Fackamato suggests.

Great ! Thanks again for all your hard work.

Arch Linux

#26 2008-01-11 02:11:58

Re: netcfg v2.0.3

#27 2008-01-11 12:22:54

Re: netcfg v2.0.3

#28 2008-01-11 12:45:00

Re: netcfg v2.0.3

#29 2008-01-12 03:37:28

Re: netcfg v2.0.3

#30 2008-01-12 08:14:40

Re: netcfg v2.0.3

#31 2008-01-12 08:32:11

Re: netcfg v2.0.3

#32 2008-01-12 11:07:13

Re: netcfg v2.0.3

#33 2008-01-12 18:52:47

Re: netcfg v2.0.3

#34 2008-01-12 23:30:04

Re: netcfg v2.0.3

#35 2008-01-13 09:02:45

Re: netcfg v2.0.3

#36 2008-01-13 10:22:41

Re: netcfg v2.0.3

#37 2008-01-13 17:24:05

Re: netcfg v2.0.3

#38 2008-01-13 23:00:29

Re: netcfg v2.0.3

#39 2008-01-14 18:51:19

Re: netcfg v2.0.3

#40 2008-01-14 19:35:55

Re: netcfg v2.0.3

#41 2008-01-15 22:48:44

Re: netcfg v2.0.3

#42 2008-01-17 17:32:25

Re: netcfg v2.0.3

#43 2008-01-19 18:35:59

Re: netcfg v2.0.3

#44 2008-01-20 10:55:32

Re: netcfg v2.0.3

#45 2008-01-22 12:38:09

Re: netcfg v2.0.3

#46 2008-01-22 14:03:05

Re: netcfg v2.0.3

#47 2008-01-22 14:35:39

Re: netcfg v2.0.3

#48 2008-01-22 16:10:11

Re: netcfg v2.0.3

#49 2008-01-22 21:05:50

Re: netcfg v2.0.3

#50 2008-01-23 04:15:17

Re: netcfg v2.0.3

Board footer