Some updates to the problem: i've installed VL SOHO 5.8 RC3, i've done again the scripts, and now when i try to connect i get this error "/dev/ttyUSB0 unknown option". I can't remember the exact message, but it sounds like that. It reffers to a part in a script from /etc/ppp/peers/, the umts script. The /dev/ttyUSB0 is the first option that appears in that script, indicating which device to use. I've changed it to look like a comment, the pppd call umts nodetach command works, but there's no connection! And I really hate the way the terminals are acting on this new version of VL. They show the output of the pppd command in only one line.Both LEDs are blinking, after the connection only one should blink, and that would be the sign that I am connected.Now i am really sorry that I've changed my OS.The result of this: quitting Vector Linux in favor of Windows XP.

im not with wireless,but i still remember the annoying bug in vector,where vec switches eth interfaces on each restart and i am internet-less in between each reboot....The only way this could be fixed was by John's "stopit doing it the udev way" howto...I really do hope that they fixed that in some of the RCs..

This is not a bug, it is by design in udev. It is impossible to predict which interface will come up first and udev detects them in that order. It also seems impossible to me to pre-define udev rules to avoid this as it would be different in every PC model and depending on extra network cards you might use. I am open to suggestions though, as it might be possible to add the functionality to the hardware detection scripts.

Logged

O'Neill (RE the Asgard): "Usually they ask nicely before they ignore us and do what they damn well please."http://joe1962.bigbox.infoRunning: VL 7 Std 64 + self-cooked XFCE-4.10