note this is wrong because it inserts an extra backslash. I can't get gtkdialog to display <edit>quotation marks without also showing a backslash</edit>.

There are more problems where the the output from the dialog is read.

Code:

eval "$RETSTRING"

Is risky because it tries to evaluate all of the output. Some of this is not executable and there is always the risk that one of the expressions could be something downright dangerous. Which field do I have to type rm -f /* into to wipeout my installation?
Something like this is safer

but I haven't included specially handling for variables with quotes in this example.

This is so close to working, well done.

I messed around and got pupdial to work with my mobile but then it wrote quotes into wvdial.conf and which broke pupdial the next time it tried to load the gui. It can probably be made to work if you accept the backslash characters in the display._________________Will
contribute: community website, screenshots, puplets, wiki, rss

warning:I put a couple of line breaks in there to stop the page being so wide_________________Will
contribute: community website, screenshots, puplets, wiki, rssLast edited by HairyWill on Tue 29 Apr 2008, 15:38; edited 3 times in total

Do all mobile phones use cdc_acm, and do these all present as the same device node?
The simplest would be a button "press this if you have connected a mobile".
I presume it could also be done automatically at boot by putting in all the usb ids. Though this is not so helpful if you plug the phone in after booting. What would be really helpful would be a list of countries, providers, contract type, connection strings and numbers as finding the connection string and correct number is a significant hurdle. A page for recording these on the wiki might be good._________________Will
contribute: community website, screenshots, puplets, wiki, rss

I gave a whirl and hit several snags.
I pretended that I didn't know which device it would get connected to. I went through all of the usb device options then used an init2 string that I already knew works to try and dial out. It failed. I can't remember the exact message from wvdial. I checked which modules were loaded and I had ipaq and idtl_???? as well as cdc_acm, I unloaded those and pupdial worked and got me connected .

I haven't looked at the code at all so if any of my comments don't make sense I apologise.

It might be good to have a list of usb.ids to decide which driver to load. I suppose it would make sense to get Barry to add them to the main list.

As far as working out what node the device is on surely there must be a way of probing the node to see if something is on the other end of it.

After pupdial finds a device it automatically writes a connection string into init2. I don't expect that this can be filled automatically but it might be helpful if we can give the user some clues on where to search for this and the number to dial.

I also was intrigued to see the vpn options. I'm not convinced this is exactly the right place for them but its great you are having a bash at this. The loss of pptpconfig bothered me though I did finally work out how to get my vpn working by hand a few weeks ago.

I tried the ms pptp option and first had to lookup the ip of my server as I only know its name. I didn't really know what I was supposed to put in the default route or netmask, though I could probably work it out if I thought hard. I wasn't quite sure if the ppp0 referred to my current interface or the one the tunnel was going to create. Isn't this always one more than the existing ppp interface(s), I left all the other settings as default. I hit the connect button and was rewarded with an extra blinky but no other output. The network connection didn't work and it looked like the routing table was wrong, I presume I made the wrong choices in the config. When I disconnected the tunnel it didn't put back my original dns servers into resolv.conf though the routing table was fine.

kazm
Try installing johns new version at the link above, that should work.

Barry has patched his copy to allow quotation marks in both init strings so the next iso he releases at the weekend should work for you as long as you load the module and make the dev link yourself._________________Will
contribute: community website, screenshots, puplets, wiki, rss

I just want to point out that Puppy 4.1 now has "pgprs," a generic wizard to detect and configure GPRS serial modem devices. It creates scripts that work directly with pppd.

I'm wondering if you ever got pupdial working with GPRS. The main catch I see to use of pupdial is the require to enter (once) the GSM PIN code to unlock the card. It is this requirement that has never allowed me to use common dialup programs.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum