Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: qb4 on December 25, 2008, 06:16:03 PM
-
Hello all,
My first post, I hope I'm doing it right.
Would it be possible to make a wvdial.tce for those of us who are stuck with dialup?
I did a search for wvdial, but maybe I am doing it wrong.
If I can get on the net with TC, then it is definitely a keeper, bye-bye Win98.
(no other Linux will run on my machine but TC).
Thanks.
-
Hi qb4!
There seems to be some interest in dialup. I remember when I was happily using a 32k modem. Though I haven't used dialup in about 4 years, I will pull my hardware out of the attick and see what I can do. I can sign up for Netzero or something like that and build and test some ppp apps. Hang in there for a little bit, for it may take a few days or a week to get my feet wet again with ppp, but I will see what I can do to support our dialup customers.
JW
Oh, pppd is available in our tce repository, but I will see if I can't add some GUI utilities to our existing pppd setup.
-
Hi qb4!
It's me again. I built and tested wvdial.tcel and it works fine here to connect. But here's the catch: my "free" dialup acces is a long distance number that costs probably about $15 or more an hour, so I don't have the best access to test it with. So I am asking for your help. Let us know if there are things that can be improved upon in the wvdial.tcel package I am about to upload so we can fix it. I will work on more user friendly dial up stuff for newcomers and I appreciate your help in providing dialup acces in TC. I am not seperating the development stuff as I said time is tight, but maybe that can come later. Thank your for your support of TC.
By the way, it is now the /etc/wvdial.conf file that you enter your settings though it was compiled for /usr/local. Maybe later can be built for /usr/local/etc/wvdial.conf
Jason W
-
Hey Jason,
You are the fastest thing since the RoadRunner, and at Xmas too.. amazing!
Thankyou for that, I have grabbed it and will test ASAP, and report back.
Edit, short time later: It needs libssl.so.0.9.8. Where can I find that, please?
-
It needs libssl.so.0.9.8. Where can I find that, please?
..it's in the extensions section
-
Juanito,
Humour me please. Remember I'm new here. :-X
Is there another extensions section than the one we are in at the moment?
If so would you please point me to it.
I have done a forum search for libssl without result.
If you mean in the repository, http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tce/ it is not there.
Also there is no wvdial.conf in /etc, it is in /usr/local/bin.
It is an ELF file and I can't edit it with Leafpad or the editor in emelfm2.
Help!
-
openssl-0.9.8h.tcel is the extension that you need to install. I forgot to mention that when I packaged it.
there is a binary called wvdialconfig ( I think that is the name, I am on Windows now ) that will create the /etc/wvdial.conf when it is run.
I will put all this into the info file and make a .dep file to automatically install openssl.
Also, upon further examination of docs wvdial seems to also depend on pppd. I will work out the details this evening.
-
wvdial is required not only for Dial-up but also by the people who use mobile phones and PCI/USB Data cards supplied by Mobile operators.
wvdial uses pppd to connect.
-
OK,
Installed openssl.
Configured wvdial.conf.
Wvdial couldn't find PPPD... had to add a PPPD Path to wvdial.conf.
Dial.. connect.. no /etc/ppp/pap-secrets.. I created one.
Dial.. connect.. PPPD died, exit code 242.
I'm learning fast, but now stuck at this point.
-
I will try to better interweave wvdial with ppp, and see what needs to be done to make it easier to dial up.
-
Well, I fired it up to try it again, and discovered that wvdial.conf and the other changes I made
didn't survive the power down.
I re-created everything, and saved backups external to TC.
Running it again, got exit code 2, (pppd options error, according to the man page at http://linux.die.net/man/8/pppd).
How to make changes save?
-
I am getting the same error. I tried dialing in with DSL linux using the ppp tool and the connection did not die though I could not send data. There seems to be something wrong in there somewhere. I will troubleshoot and report back when I find some answers.
Backing up the /etc/wvdail.conf would save that file across reboots. When I get this working I will put more into the info fille on setup and what files to back up.
edit:
Netzero's dial up tool (downloadable .deb version) does not connect either. Dies just like wvdial/ppp. So there is something wrong with the account or settings. I will try other providers and see if I have better luck.
-
I have had success with pppsetup, which I used in Slackware when I was on dialup and it makes the whole thing so easy. I don't know what is the issue with wvdial but I have spent a couple of evenvings on it myself trying to get it to work and I don't want to waste anyone else's time either, so I think it is best to pull that extension and chalk it up to experience. Maybe later someone else that uses dialup regular can make a wvdial extension. There are just a couple of things such as device names in the pppsetup script that need adjusting and when I test it out for a while I may upload an extension for it. It only requires bash and ppp.
My intentions were good but I stuck my foot in my mouth with wvdial. Pppsetup takes care of the things that wvdial was lacking anyway.
-
Seeing as the error was related to PPPD options, I tried an options file (12 lines) from another distro.
It didn't make for any different result.
Was worth a try, anyway.
You have my admiration for wasting two nights on this, I wouldn't have.
I hope you are able to get pppsetup straightened out.
May the force be with you.
-
A little frustrating as I counted my chickens before they hatched, but not a waste on my end. PPPsetup works very well and as soon as a config directory issue is decided upon with pppd then I will retool the script, test, and upload the extension. Supporting PPI mode is what is being worked out with pppsetup to save from having to back up files across reboots. Hopefully that way ppp setups will persist across reboots without specifying files to back up if one is using mounted /usr/local. That is the goal.
-
This won't be of any help to you, and probably of very little interest.
Following your mention of PPPSETUP, I searched and found a couple of files.. both quite different.
One has a TUI, and the other creates a script.
I setup the script one and ran it, and after having to re-locate all the PPPD files to /usr/sbin (which is apparently where they are supposed to be), ran the script and online immediately.
Only problem was I couldn't connect with Opera or Minefield, but Links was fine.
The file was pppsetup-2.28.tar.gz (7,896bytes), but I don't remember where I got it from.
Probably not the best one to make a .tce of for the average punter.
Anyway, TC is now dialup-connectable. HOORAH!
-
That is the same pppsetup I used. Now the issue is supporting PPI so configs would not have to be backed up on each reboot. The pppsetup script would require quite a rewrite, so I may write a new one from scratch to accomodate PPI mode as that may be easier than the rewriting and testing of a hacked pppsetup. For now use pppsetup and I will post a setup tool when PPI mode of pppd.tcel is worked out.
-
...after having to re-locate all the PPPD files to /usr/sbin (which is apparently where they are supposed to be), ran the script and online immediately.
step by step instructions, if possible, would be neat for dialup users. as for relocating the files, i'm just guessing that you should have untargz'ed it from the / folder, which should put the files in the right place.
-
There is now a pppsetup.tce extension.
-
Hi:
Is there any posibility to upload wvdial.tce? this utility works flawesly in other distro.
Regards,
Alex
-
Hi Jason:
I have had sucess with wvdial version 1.41!!
I had to copy manually the configuration files from puppyOS:
1)I copied to "/etc" the files reslov.conf and wvdial.conf
2)I copied to /usr/bin the file wvdial (it´s only 77 kb)
2)I created a file /etc/ppp/peers/wvdial with "noauth" and "name wvdial" in two separate lines.
3) and add a line in wvdial.conf with PPPD Path = /usr/local/sbin/pppd
Now I want the configuration to persist after reboot. Do I have to create a TCE extension? or is there any way to back up the copied files?
Thanks!!
Alex
-
That's great. Backing up the files in /etc and the binary in /usr/local by adding them to /opt/.filetool.lst would make it persist. It would be good if you could submit an extension of this.
-
I have had sucess with wvdial version 1.41!!
I had to copy manually the configuration files from puppyOS:
The above worked for me too. I took the files from Puppy Linux version 2.17.1
[EDIT: I didn't need to do everything I list below. Please therefore also see my immediately following post for final details]
Just for the hell of it, I also copied puppyserialdetect (into /usr/sbin), which also worked fine under Tiny Core Linux.
What was particularly good, from my point of view, was that it all now also worked with my PCMCIA modem on /dev/ttyS1
Prior to the above, I could only get pppsetup with ppp-go working on an external modem connected to /dev/ttyS0
I did do a few extra things during the configuration (some of which might not be relevant... I have to re-check):
1. I downloaded tce extension setserial
2. I ran: setserial -v -b /dev/ttyS1 auto_irq skip_test autoconfig
(I don't really know if I 'needed' to do items 1 and 2 though; I'll have to check that and report back later).
3. I entered: ln -sf /dev/modem /dev/ttyS1
4. I edited /etc/ppp/pppscript in order to change the modem initialisation info to:
"" "ATZ"
"" "ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0"
(on two separate lines)
These modem init values were the same as those I found in puppy wvdial.conf, without which my pcmcia modem on /dev/ttyS1 wouldn't connect. Using them I'm now able to dial-in using either wvdial or ppp-go from my pcmcia modem on /dev/ttyS1.
5. Owing to my Internet Service Provider doing something to their ppp connection negotiation set up, I needed to also add the -am option on a line by itself just after the line asyncmap 0 in the file /etc/ppp/options
That is:
. . .
asyncmap 0
-am
. . .
I believe the above tells pppd not to negotiate asyncmap but to use the default value asyncmap 0. Without that, I cannot connect using ppp to my ISP with pretty much any Linux distribution (though Windows machines dial in fine). I doubt most people need or want the -am option though; it's just my ISP and a few others.
6. I 'may' have done something else too, but I can't recall. However, I'll be trying the procedure out from scratch tomorrow sometime, so will edit this post accordingly as needed.
I'm absolutely loving the tiny tiny core linux. It is the most flexible Linux distribution ever. Fantastic job!
-
I have now gone through the above process again from scratch to find out what parts I didn't actually require.
1. To get ppp-go (via pppsetup) working, on either my external modem (on /dev/ttyS0) or now my pcmcia modem (on /dev/ttyS1) I don't need wvdial at all (however, ... instructions for using wvdial from Puppy OS work fine for me, though, on my computer, with my ISP, I still need to also do the configurations which I outline below).
2. My external hardware modem on /dev/ttyS0 works fine with the default modem initialisation settings provided by pppsetup. However my pcmcia modem wouldn't work with the default AT modem string values. Instead, I had to supply the following AT modem string (which also, incidentally, works fine with my external modem on /dev/ttyS0):
ATZ OK "ATQO V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0" OK
I entered the above all on one line when asked (given the opportunity to) on running the pppsetup program. Note that pppsetup then automatically writes out the pppscript (and creates ppp-go), which results in the following line appearing in pppscript just prior to the atdt... dialing stanza:
"" ATZ OK "ATQO V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0" OK
This is actually the default modem initialisation string which Puppy Linux version 2.17.1 uses for wvdial as it happens (though of course you don't need to use wvdial itself at all for ppp-go to work unless you want that dialer too).
(NOTE: Since the above modem initialisation string has always worked well with a variety of modems, I suggest that pppsetup is modified such that this is offered as the default modem initialisation string, since that would avoid a lot of newcomers a lot of potential difficulty).
3. This part probably doesn't effect most people. It depends on how your Internet Service Provider has ppp set up. In my case, I was getting the following ppp connect error:
. . .
Sent [PAP AuthReq . . .]
No response to PAP authentication-requests
. . .
sent [LCP TermReq id=0x5 "Failed to authenticate ourselves to the peer"]
Connection terminated
The solution, as I pointed out in my above post was to add the pppd option -am to the /etc/ppp/options pppd configuration file. I put that option immediately after the asyncmap 0 option line, on a separate line, as follows in this extract (don't forget the minus sign in front of the am). As I said, most people probably won't need or want this -am option though:
. . .
asyncmap 0
-am
. . .
Note that I didn't need to install or use "setserial" afterall (or any programs at all from Puppy Linux if I was simply wanting to use pppsetup and ppp-go [just needed the suggested modem initialisation string], though the wvdial program out of Puppy version 2.17.1 certainly works too [with, for the case of my ISPs ppp negotiation, the above -am line added to /etc/ppp/options] as described).
Hope this info helps someone.
-
For information on how to set up a dial up internet connection, see
/dial.html][removed due to policy violation]/dial.html (http://[removed due to policy violation)
For information on how to install Tiny Core without being connected to the internet, see
/install.html][removed due to policy violation]/install.html (http://[removed due to policy violation)
I hope this helps people with dial up internet connections.
-
/dial.html][removed due to policy violation]/dial.html (http://[removed due to policy violation)
... /instal.html][removed due to policy violation]/instal.html (http://[removed due to policy violation)
not bad, you should be editing the wiki.
-
it would be possible to recreate the extension for the new tinycore?
I've tried but I ran into an error when the program starts:
tc@box:/$ wvdial
wvdial: error while loading shared libraries: libuniconf.so.4.6: cannot open shared object file: No such file or directory
tc@box:from what I found would be a wrong path of wvdial against wvstream,
a dependency that must be compiled first
-
A wvdial extension would be a good addition.
It would be good if you keep trying, and see if you get it working. Even get help from others when you need it.
The people who create extensions do not have a dial up connection, and have no way of testing whether it works. So they have not created the extension.
-
For a potential alternative see:
http://forum.tinycorelinux.net/index.php?topic=8431.msg45206#msg45206
xeznet which is available as precompiled binary seemed to work here after some fiddling...
Of course, what Guy said applies, no opportunity to test with a modem connection.
-
Ok, I succeded to use wvdial and now I want to create the package, but still a few problems and I would ask those who are more experienced than me.
1 After compiling wvdial always and ran, it says he does not find the library libuniconf.so.4.6. This library comes from wvstream I have compiled first. This problem seems to disappear to the installation of any package.tcz! could be a permissions problem?
2 wvdial inevitably calls for the executable pppd in /usr/sbin (actually installed in /usr/local/sbin from package pppd).
The string PPPD = /usr/local/sbin/pppd in /etc/wvdial.conf generates this error during wvdial starting:
...
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Timed out while dialing. Trying again.
--> Sending: ATD*99#
--> Waiting for carrier.
...A symlink still easily solves this problem, but have an executable and a symlink in two different directory of executable both controlled by the system could not create problem?
-
Umm, did you try to
specify a "PPPD Path" option in wvdial.conf.?
-
PPPD = /usr/local/sbin/pppd
Here is a small explanation http://linux.die.net/man/5/wvdial.conf
-
Try literally "PPPD Path = /usr/....". For your first issue, ldconfig hasn't been run, and it is run on tcz install.
-
damn inattention!
Thanks curaga, the problem 2 has vanished, remains the 1, but maybe this problem is solved by creating the package.
I try and will let you know
-
ok, the package is sent, hopefully good ;D