After i create the Log-Folder, because cat /var/log/messages | grep ppp show me first:
[root@ipf1lte ~]# cat /var/log/messages | grep ppp
Jan 17 15:57:55 ipf1lte pppd[2131]: no device specified and stdin is not a tty
Jan 17 17:38:07 ipf1lte pppd[1976]: no device specified and stdin is not a tty
Jan 17 18:06:15 ipf1lte pppd[10052]: pppd 2.5.0 started by root, uid 0
Jan 17 18:06:15 ipf1lte pppd[10052]: Using interface ppp0
Jan 17 18:06:15 ipf1lte pppd[10052]: local IP address 10.112.112.112
Jan 17 18:06:15 ipf1lte pppd[10052]: remote IP address 10.112.112.113
Jan 17 18:06:15 ipf1lte root: Could not find a bridged zone for ppp0
Jan 17 18:06:15 ipf1lte vnstatd[1790]: Interface "ppp0" added with 1000 Mbit bandwidth limit.
Jan 17 18:06:15 ipf1lte vnstatd[1790]: Monitoring (4): ppp0 (1000 Mbit) wlan0 (1000 Mbit) red0 (1000 Mbit) green0 (1000 Mbit)
Jan 17 18:06:17 ipf1lte ntpd[2065]: Listen normally on 4 ppp0 10.112.112.112:123
Jan 17 18:06:17 ipf1lte pppd[10052]: Starting link
Jan 17 18:06:17 ipf1lte pppd[10052]: Can't create lock file /var/run/pppd/lock/LCK..ttyUSB0: No such file or directory
Jan 17 18:06:48 ipf1lte pppd[10052]: Starting link
[root@ipf1lte ~]# mkdir /var/run/pppd/lock/
mkdir: cannot create directory ā/var/run/pppd/lock/ā: No such file or directory
[root@ipf1lte ~]# mkdir -p /var/run/pppd/lock/
and initiate the Dial-In Prozess the var/log/messages show me:
Jan 17 15:57:55 ipf1lte pppd[2131]: no device specified and stdin is not a tty
Jan 17 17:38:07 ipf1lte pppd[1976]: no device specified and stdin is not a tty
Jan 17 18:06:15 ipf1lte pppd[10052]: pppd 2.5.0 started by root, uid 0
Jan 17 18:06:15 ipf1lte pppd[10052]: Using interface ppp0
Jan 17 18:06:15 ipf1lte pppd[10052]: local IP address 10.112.112.112
Jan 17 18:06:15 ipf1lte pppd[10052]: remote IP address 10.112.112.113
Jan 17 18:06:15 ipf1lte root: Could not find a bridged zone for ppp0
Jan 17 18:06:15 ipf1lte vnstatd[1790]: Interface "ppp0" added with 1000 Mbit bandwidth limit.
Jan 17 18:06:15 ipf1lte vnstatd[1790]: Monitoring (4): ppp0 (1000 Mbit) wlan0 (1000 Mbit) red0 (1000 Mbit) green0 (1000 Mbit)
Jan 17 18:06:17 ipf1lte ntpd[2065]: Listen normally on 4 ppp0 10.112.112.112:123
Jan 17 18:06:17 ipf1lte pppd[10052]: Starting link
Jan 17 18:06:17 ipf1lte pppd[10052]: Can't create lock file /var/run/pppd/lock/LCK..ttyUSB0: No such file or directory
Jan 17 18:06:48 ipf1lte pppd[10052]: Starting link
Jan 17 18:06:48 ipf1lte pppd[10052]: Can't create lock file /var/run/pppd/lock/LCK..ttyUSB0: No such file or directory
Jan 17 18:07:20 ipf1lte pppd[10052]: Starting link
Jan 17 18:07:20 ipf1lte pppd[10052]: Can't create lock file /var/run/pppd/lock/LCK..ttyUSB0: No such file or directory
Jan 17 18:07:51 ipf1lte pppd[10052]: Starting link
Jan 17 18:07:56 ipf1lte pppd[10052]: Connect script failed
Jan 17 18:08:08 ipf1lte pppd[10052]: Terminating on signal 15
Jan 17 18:08:08 ipf1lte pppd[10052]: Exit.
Jan 17 18:08:10 ipf1lte vnstatd[1790]: Interface "ppp0" disabled.
Jan 17 18:08:12 ipf1lte ntpd[2065]: Deleting interface #4 ppp0, 10.112.112.112#123, interface stats: received=0, sent=0, dropped=0, active_time=115 secs
Jan 17 18:08:16 ipf1lte pppd[10517]: pppd 2.5.0 started by root, uid 0
Jan 17 18:08:16 ipf1lte pppd[10517]: Using interface ppp0
Jan 17 18:08:16 ipf1lte pppd[10517]: local IP address 10.112.112.112
Jan 17 18:08:16 ipf1lte pppd[10517]: remote IP address 10.112.112.113
Jan 17 18:08:16 ipf1lte root: Could not find a bridged zone for ppp0
Jan 17 18:08:18 ipf1lte ntpd[2065]: Listen normally on 5 ppp0 10.112.112.112:123
Jan 17 18:08:18 ipf1lte pppd[10517]: Starting link
Jan 17 18:08:20 ipf1lte vnstatd[1790]: Interface "ppp0" enabled.
Jan 17 18:08:23 ipf1lte pppd[10517]: Connect script failed
Jan 17 18:08:55 ipf1lte pppd[10517]: Starting link
Jan 17 18:08:59 ipf1lte pppd[10517]: Connect script failed
Jan 17 18:09:33 ipf1lte pppd[10517]: Starting link
Jan 17 18:09:37 ipf1lte pppd[10517]: Connect script failed
Jan 17 18:10:09 ipf1lte pppd[10517]: Starting link
Jan 17 18:10:13 ipf1lte pppd[10517]: Connect script failed
Jan 17 18:10:45 ipf1lte pppd[10517]: Starting link
Jan 17 18:10:49 ipf1lte pppd[10517]: Connect script failed
Jan 17 18:11:23 ipf1lte pppd[10517]: Starting link
Jan 17 18:11:27 ipf1lte pppd[10517]: Connect script failed
Jan 17 18:12:00 ipf1lte pppd[10517]: Starting link
Jan 17 18:12:05 ipf1lte pppd[10517]: Connect script failed
Is your LTE device recognized by the kernel? Do you see it listed with lsusb? Do you have the device in /dev/? You can check with ls /dev/ | grep ttyUSB.
Good morning cfusco,
yes, i can see detailed information with lsusb. And i have more than 1 devices in with ls /dev/ | grep ttyUSB.
Should i post it ?
Is it necessary to use modeswitch ?
Or, maybe, i must be change the firmware ?
What permissions do you have on /var/run/pppd and /var/run/pppd/lock ?
The ppp developers have created a fix for the problem of missing and not created directories that was caused in ppp-2.5.0 and they look to include it in the ppp-2.5.1 release. Unfortunately that release still has not been made by them after three months so I will probably do a patch submission for the commit level that includes the fixes for this problem.
That will at least ensure that the problem of missing directories that are not created gets structurally solved for the future.
Dear Mr. Belka, sorry, the misunderstanding on my part (maybe about logtime-differences ) because after i create the folder the cat /var/log/messages | grep ppp donāt show me again:
Canāt create lock file /var/run/pppd/lock/LCKā¦ttyUSB0: No such file or directory
BUT, by-the-way, as i look into the folder (/var/run/pppd/lock/ā¦): Itās empty
Curious !!
And actually, after iāve flashed the Firmware of the LTE-Device the Modem Information give me in the part Network Information:
Network Registration (not longer: NOT REGISTRED, NOT SEARCHING), rather
REGISTRED TO HOME NETWORK
The problem is, there is no /var/run/pppd/lock path in system.
Just manually create it.
Make sure you are root while mkdir.
You have to recreate it on every boot as described below.
The problem of some of the lock file directories not be creating was a bug in ppp-2.5.0 It was mentioned in some other posts on the forum about PPP.
A set of patches were created and approved by the PPP developers and merged and their plan was to issue these as version ppp-2.5.1 but unfortunately 4 months later version 2.5.1 has still not been released.
I have looked at getting a source tarball from the github siite based on the latest commit status but that is also not easily done.
I will have another go at that to figure out a way to create a source tarball from the PPP github site from the current commit status.
There was a discussion on that in the github issue related to this problem but some of the distros came back and said the default directories had been created as part of the default install in the past and it was not good to suddenly have that stopped without any warning.
After some discussion a person created a patch set that created the required default directory and that patch set was accepted and it was merged into the PPP github repo back in Nov 2023. Distroās can then still define a different directory if they want but a default one is created.
So the fix has been included into the master branch of the PPP github just that the next release to include that has not been produced yet.
I had a look again today and found that I could get a zip file of the current master, which I downloaded. I then extracted it, renamed it from master to the latest commit that was included in it, and I will now do a build and patch submission of it for IPFire. It may or may not get into CU 185 but definitely into CU 186.
Great! The main problem now is that even if you create given folder - it needs a recreation on every boot or pppd wonāt start. That makes modem/mobile unusable for RED.
You might be able to deal with that by adding the mkdir command into your rc.local file. That runs after all initscripts are run but before the networking is started, which is where pppoe will be started. https://www.ipfire.org/docs/pkgs/rc-local
The only thing you will need to remember is to remove the command when the updated ppp version is put into a Core Update.
As far as I know you donāt need PPP-Configuration for internal LTE devices.
As long as the correct driver is in the kernel or IPFire (or was implemented from you by self-compiling an own instance) and IPFire recognizes your device in the interface-setup, you need āQMIā or āMBIMā (depends on the chipset on the WWAN-module) to connect and get RED configured the right way.
āMBIMā is not implemented in IPFire by default, but I wrote a complete isntruction on how to do this here, including a script that configures the RED-interface afterwards:
Correct me if Iām wrong, maybe I just misunderstood your issue.
After the weeks, thankās a lot for your help.
But i have now an other way to bring back the ipfire in my network-environment.
And about the last answers from Lexus Polaris (Alex): Iāll try it with my
hardware.