Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 22 Aug 2017, 22:46
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
pgprs-2.0.2
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 3 [42 Posts]   Goto page: Previous 1, 2, 3 Next
Author Message
watchdog

Joined: 28 Sep 2012
Posts: 1404
Location: Italy

PostPosted: Sat 20 Feb 2016, 01:20    Post subject:  

rerwin wrote:
watchdog,
But if you still have that problem with my version that I intend to be "pgprs-2.0" once we get past beta testing, please report that here.
R


Yes, I intended that the problem about resolv.conf is with your version which I'm testing. The last one in first post in this thread. I wrote pgprs2 instead of pgprs-1.5.2-20160214-beta.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1813
Location: Maine, USA

PostPosted: Sun 21 Feb 2016, 23:48    Post subject:  

LazY Puppy wrote:
I installed just by clicking the .pet files - nothing else!
Thanks for installing in the way I intended. The key here is the fact of the hang. The tool used to test for modem devices can hang in some cases that I have not encountered, myself. I have added an improved version of the workaround for that, in the 20160221 version in the first message of this thread.

The fix also corrects other logic, so that more device names will be tested. The workaround will wait for 5 seconds if the tester hangs, then stop the hanging and continue testing for other devices. Normally, each device test will be nearly instantaneous.

In addition, I added to the "connect" package updated pdiag components to better capture pgprs files for analysis. The rest of the package is the same as the previous version (20160206).

Thank you again, Lazy Puppy, for "holding my feet to the fire" to get me to clean up the device determination logic. The new pgprs package will add some trace information to the /tmp/xerrs.log file, showing the process of device testing. Please send me that file, so I can verify how the fix works.

Now I can think about watchdog's resolv.conf problem.

LazY Puppy wrote:
By the way: I forgot to mention that frisbee is recognizing the USB Modem after a refresh in tahr64 605 with the fdrv sfs loaded, though -as in all my previous testings- exit code 8. No connection possible.
Frisbee's gprs option has a bug that makes that option unusable. I discovered that while investigating your initial report of a problem with it. That will fixed in the beta for frisbee 1.4 (initially, 1.3.5-beta).
R
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1941
Location: Germany

PostPosted: Tue 23 Feb 2016, 02:00    Post subject:  

rerwin wrote:
The tool used to test for modem devices can hang in some cases that I have not encountered, myself.

I think -no, I'm convinced- you did not really understand what's the problem over here.

It is NOT the tool used to test for modem devices that hangs. Since there is no GUI appearing from wherein I can select or enter my device from a shown list of detected devices, so there is no tool running to test for modem devices found.

The problem is: after installing your packages I click the connect icon on desktop. In that GUI I switch to the second tab and choose gprs for to run next time. Then I switch back to tab one and am clicking the icon for gprs wireless modems.

That's the point where a GUI pops up to enter my APN and to select/enter the modem device. This GUI appears when I'm installing my personal pgprs package.

But it doesn't appear when I'd installed the your packages. So, no APN known for the connect script's code, so no connection possible.

Now I'm going to tell you what I'd done so far with the latest of the your pgprs package.

Since I can read bash code I decided to extract the packages to have a look into the new pgprs connect script to search for a reason why I can't setup/enter my APN and modem device.

To my own surprise I found the pgprs setup script still existing - though there is no such a menu entry for pgprs setup. I had a look again into the .desktop file and found again pgprs --connect for its Exec= entry.

So I felt in love with the idea just to type pgprs --setup into a terminal to find out, what will happen afterwards.

To my own surprise again, the GUI to setup/enter APN and modem device appears on the screen. My modem device is detected and preselected. I'd chosen *99***1# as for the phone number (it's just the default in older versions and had worked for me all the time) and exited the GUI by Ok.

Opened up a second terminal and typed pgprs --connect into that. At first try it didn't connect, but this happens sequentally also in older versions when I'm too quickly trying to connect after setting up APN and modem device.

On a second try it connects to the web and I'm currently posting from that connected connection. Laughing

Using tahr 6.0.2 in original. Just changed the keyboard layout to DE.

So, I need / it needs to have the pgprs setup script (the GUI) appearing on the screen after clicking the gprs wireless icon in internet connection wizard. And this -so far- has never ever happened in any of the your new rewrite scripts of pgprs. Got me now?

At last just one simple question: is frisbee really able to do anything else then returning exit code 8, not connected? I will put frisbee on top of my personal list of exit code 8 applications. Laughing Laughing Laughing

_________________
RSH

Die etablierten Parteien in Deutschland setzen mathematische Regeln außer Kraft. Zuviele Nullen vor dem Komma - das ist gefährlich.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1813
Location: Maine, USA

PostPosted: Tue 23 Feb 2016, 23:46    Post subject:  

LazY Puppy wrote:
It is NOT the tool used to test for modem devices that hangs. Since there is no GUI appearing from wherein I can select or enter my device from a shown list of detected devices, so there is no tool running to test for modem devices found.
Actually, the modem testing is done in preparation for display of the GUI, to populate the device list that you select from. That is where the hang can occur, which would cause the GUI to not display.

Quote:
The problem is: after installing your packages I click the connect icon on desktop. In that GUI I switch to the second tab and choose gprs for to run next time. Then I switch back to tab one and am clicking the icon for gprs wireless modems.
That's the point where a GUI pops up to enter my APN and to select/enter the modem device. This GUI appears when I'm installing my personal pgprs package.

But it doesn't appear when I'd installed the your packages.
Thanks for describing your steps. I replicated that sequence on my test PC and saw the setup window (GUI), entered an APN, clicked OK, then clicked the 'connect' icon and, after a few seconds, saw the "connection failed" window, which is as far as I can get (with no real mobile/wireless ISP). (I use a USB analog modem to simulate a wireless modem, for the purpose of detection.)

Quote:
Now I'm going to tell you what I'd done so far with the latest of the your pgprs package.
By running the setup and connect scripts separately, you confirmed that the main parts do work. That implies that the interfacing script. 'pgprs' is where something is not right. Please turn on tracing in the file, /usr/sbin/pgprs, by removing the "#" at the beginning of line 4 (#set -x ...). Then start pgprs as you described. Use a fresh environment or delete /etc/gprs.conf before trying pgprs. Then please send me the /tmp/xerrs.log file, to give me the evidence I need to solve the problem -- and to save you from having to troubleshoot further.

Quote:
At last just one simple question: is frisbee really able to do anything else then returning exit code 8, not connected? I will put frisbee on top of my personal list of exit code 8 applications. Laughing Laughing Laughing
That is all that frisbee's gprs function will do until I upload an updated version (1.3.5-beta). Its gprs logic is similar to that of the new pgprs. So, I need to fix it with whatever we learn about the pgprs problem(s).
R
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1813
Location: Maine, USA

PostPosted: Mon 11 Apr 2016, 16:19    Post subject: New beta - 20160410  

I have uploaded another beta of pgprs 1.5.2 for testing. I attempted to clean up the behavioral problems Lazy_Puppy encountered, and others. Now, when you exit/disconnect from a connection window, the "Configure" (setup) window will appear. To avoid that, you can disconnect with the "X" window-close button. However,the "close but stay connected" button does not start the setup window.

Please give me feedback on how the connection process goes, because I cannot test that myself.
Richard
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1941
Location: Germany

PostPosted: Mon 11 Apr 2016, 17:07    Post subject:  

Downloaded and installed.

Still no GUI to enter my APN and stuff when clicking the GPRS button in internet connection wizard !!!

Modem not recognized in frisbee (the original one in tahr 6.0.2 - don't have a newer one).

PupDial recognized the modem but couldn't connect to the web.

PDiag file attached.

Though, this time when installing my private pgprs package on top of your pgprs package, I could connect to the web (this wasn't possible in earlier versions, needed to reboot then).

_________________
RSH

Die etablierten Parteien in Deutschland setzen mathematische Regeln außer Kraft. Zuviele Nullen vor dem Komma - das ist gefährlich.

Last edited by LazY Puppy on Mon 11 Apr 2016, 17:32; edited 1 time in total
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1941
Location: Germany

PostPosted: Mon 11 Apr 2016, 17:32    Post subject:  

Thanks to zigbert's post I had attention to these attached packages:

- connect_updates-20160321.pet
- frisbee-1.3.5-20160410-beta.pet

So I made a fresh reboot and installed the above packages and pgprs-1.5.2-20160410-beta.pet as the last one.

Got a gui to enter APN and stuff (made a mistake then) so, after a 2nd try I'm now online by GPRS connection. Didn't try to connect with frisbee - don't want to, since the usual GPRS seems to work now for my modem.

I have removed the above attached pdiag file.

Cool !!!

_________________
RSH

Die etablierten Parteien in Deutschland setzen mathematische Regeln außer Kraft. Zuviele Nullen vor dem Komma - das ist gefährlich.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1813
Location: Maine, USA

PostPosted: Mon 11 Apr 2016, 22:49    Post subject:  

LazY Puppy,
Thank you for trying my pgprs one more time! I am ecstatic that you are able the get it working.

Thanks for your persistence.
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1941
Location: Germany

PostPosted: Tue 12 Apr 2016, 19:19    Post subject:  

rerwin wrote:
LazY Puppy,
Thank you for trying my pgprs one more time! I am ecstatic that you are able the get it working.

Thanks for your persistence.

I'd recently finished my work on T.O.P.L.E.S.S. 1.0.1, so I just got some time to give it a try again.

Good that it is working now. Hopefully it will find its way back into the next Puppy Systems to come! Idea

_________________
RSH

Die etablierten Parteien in Deutschland setzen mathematische Regeln außer Kraft. Zuviele Nullen vor dem Komma - das ist gefährlich.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1813
Location: Maine, USA

PostPosted: Tue 12 Apr 2016, 20:57    Post subject:  

LazY Puppy,
My plan is to learn how to prepare the packages for inclusion in the woof-CE system. Thanks to your helpful testing of pgprs, I am almost ready to rename it as "2.0", as a candidate for woof-CE. I want to be able to do that, too, with Frisbee, but need someone to verify that the GPRS part of it actually works.

Since it uses logic similar to that in pgprs-2.0, it should work. You are the only person in this thread, so far, that has the capability to utilize Frisbee's GPRS. Please consider trying it. You might find it interesting, particularly if you run parts of it and Pgprs. The two should protect themselves from interfering with each other, by preventing certain combinations of activities.

You can start a connection with either, then close the "connection" window and then get back to the connection by using the other tool. For example, start a connection with Frisbee but then monitor it from "Pgprs Connect", in the menu. Although Pgprs-setup and Frisbee cannot be active at the same time, Frisbee can be active while a Pgprs connection is displayed (but not Pgprs-setup while a Frisbee GPRS connection is displayed).

Anyway, the main thing is to verify that you can connect using Frisbee as well as you can with Pgprs. That will get us closer to final release of both, reducing the chances of needing a bugfix release.
Richard
Back to top
View user's profile Send private message 
Aung

Joined: 19 Jan 2007
Posts: 144
Location: Hervey Bay

PostPosted: Fri 15 Apr 2016, 09:44    Post subject: Trying pgprs in fatdog  

Trying pgprs in fatdog
From the menu button, no interface shows up, straight to this message.

Attempting connection through /dev/ttyUSB2 to APN cellcard...

Couldn't open the /dev/ppp device: No such file or directory
Exit status is 4
DISCONNECTED

From command line

# pgprs
/usr/local/pgprs/pgprs-connect: line 24: /usr/sbin/networkdisconnect: No such file or directory

copied 'networkdisconnect' from micko slacko, almost but no connection, stonkered

Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/ttyUSB2
kernel does not support PPP filtering
local IP address 10.161.20.184
remote IP address 10.0.0.1
primary DNS address 203.144.66.3
secondary DNS address 203.144.65.2


This is what micko slacko looks like, is the problem in the (CHAP) bit.

--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Apr 15 20:32:56 2016
--> Pid of pppd: 9587
--> Using interface ppp0
--> Authentication (CHAP) started
--> Authentication (CHAP) successful
--> local IP address 10.161.87.46
--> remote IP address 10.64.64.64
--> primary DNS address 203.144.66.3
--> secondary DNS address 203.144.65.2
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1941
Location: Germany

PostPosted: Fri 15 Apr 2016, 20:47    Post subject:  

Quote:
Anyway, the main thing is to verify that you can connect using Frisbee as well as you can with Pgprs. That will get us closer to final release of both, reducing the chances of needing a bugfix release.

I'm sorry to say:

- trying to connect to the web using frisbee was NOT SUCCESSFUL !!!

I tried multiple different things to be setup in frisbee, but none of them worked.

Got four different values of exit status: 0, 1, 4, and 8.

Unfortunately I'd overseen to store the pdiag file to external drive, so it was lost at reboot. I will give this just and only one more try, to send to you the pdiag file - apart from this: I'm really getting tired to try frisbee to connect to the web.

The WoofCE team should be ashamed as much as possible, to remove a working pgprs connection tool without to have a fully working replacement. WoofCE had made so nice and many improvements and progress in other parts, but this pgprs/frisbee PROBLEM really has left the path of Linux.

As I do understand Linux it's about WORKING - no matter what the GUI looks alike or if there is even a GUI. The removal of pgprs without a fully working replacement is the COMPLETE REVERSAL of this philosophy.

Really this sucks!

Rerwin, I appreciate you efforts on this, but I'm getting too tired on this to continue on this pgprs/frisbee PROBLEM in any matter.

The WoofCE Guys should really make a turnaround on this PROBLEM.

Give the original pgprs package back to the users of gprs modems - they are NOT LESS as some may have noticed lately in the forum about issues trying to connect by gprs modems!

Also: I think it's kinda shizo stuff to declare gprs modems as OLD by the use of an operating system designed to use/run OLD hardware! Laughing Laughing Laughing

At least Puppy Linux should define a border or time line backwards of supporting types of computers. By the current state to run on 256/512 MB machines, Puppy Linux is SUPPORTING THE WASTE of electric power and therefor SUPPORTING THE WASTE of getting rare resources to produce such electric power!

This way the OS could get a bit bigger in size without to remove files in KB size to keep the Puppy small !!! Laughing

_________________
RSH

Die etablierten Parteien in Deutschland setzen mathematische Regeln außer Kraft. Zuviele Nullen vor dem Komma - das ist gefährlich.
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1205

PostPosted: Fri 15 Apr 2016, 21:11    Post subject:  

LazY Puppy wrote:
The WoofCE team should be ashamed as much as possible, to remove a working pgprs connection tool without to have a fully working replacement. WoofCE had made so nice and many improvements and progress in other parts, but this pgprs/frisbee PROBLEM really has left the path of Linux.

As I do understand Linux it's about WORKING - no matter what the GUI looks alike or if there is even a GUI. The removal of pgprs without a fully working replacement is the COMPLETE REVERSAL of this philosophy.

There's something called "pgprs2" in Slacko 6.3.0.6. Hooray for Woof-CE? Laughing
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1941
Location: Germany

PostPosted: Fri 15 Apr 2016, 21:18    Post subject:  

Quote:
There's something called "pgprs2" in Slacko 6.3.0.6. Hooray for Woof-CE?

Really ???

Ok, hooray for Woof-CE - if you are right... (and if it works) Wink

_________________
RSH

Die etablierten Parteien in Deutschland setzen mathematische Regeln außer Kraft. Zuviele Nullen vor dem Komma - das ist gefährlich.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1813
Location: Maine, USA

PostPosted: Tue 26 Apr 2016, 15:29    Post subject:  

I have now uploaded a release candidate version of pgprs that corrects problems left in the 20160410 version, along with a final (minor cleanup) version of connect_updates.

Thanks to Aung's report of his experience with fatdog, I added and corrected logic so that it should work OOB, except for the "kernel does not support PPP filtering" issue. I understand that this indicates that PPP filtering was not configured into the kernel build, so probably requires attention by the fatdog developer. The "RC" gets as far as I can go, in that the connection window shows an ERROR with the "IP" line in the chat script (because I can test with only an analog modem, which probably does not recognize the cgdcont command).
EDIT: Aung, I re-uploaded the RC after download number 1, to add automatic creation of the /dev/ppp device (in case you downloaded it). Applies only to fatdog, AFAIK.

LazY Puppy,
Thanks for trying frisbee's GPRS. Too bad that it did not work. I have made further fixes to it, but cannot know whether I fixed the problems you encountered. I would need a pdiag, to work the problem. I sympathize with your being tired of testing this stuff. I am getting tired of it, too. But I want to "get it right".

Regarding the Woof-CE decision to abandon the original pgprs, it was incompatible with their architecture that removed the "all-firmware" system of dynamic installation (at least for tahr). With pgprs-2.0, I am attempting to restore PGPRS to the mainstream puppies, for Woof-CE to adopt. That is why your help in testing it was vital. Thank you, again, for doing that.
Richard
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 3 [42 Posts]   Goto page: Previous 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0712s ][ Queries: 14 (0.0064s) ][ GZIP on ]