The mode is actually a combination of LED color 4 = blue(idle), 5 = cyan(connected), and submode 7 = HSDPA
I need to find some proper documentation, really.
*some* username and password, so defaults are set if user enters nothing.
Removed interface_ppp_configure call from interfaces_ppp_edit.php. It was
useless there with the new structure, and it caused all PPP links to attempt
to connect when user presses "Save" even before they are assigned to LAN/WAN, etc.
Also, fix up pfsense-utils.inc and status_interfaces.php
to display more info on status_interfaces.php.
Changed util.inc to allow cua* interfaces to be recognized as real interfaces as
pfSense got "interface mismatch" at boot and forced user to reassign. Maybe someone
else has a better way to do this.
Number, and the SIM PIN and wait time for the SIM to settle after the PIN is
entered.
Still no work on multilink PPP with serial port links.
Right now the code creates the mpd.secret file. I tested it using the set auth
password <password> syntax in the mpd.conf file and got errors so I kept the
mpd.secret file generation. PPP for modems does need the mpd.script file. It's
the chat script file for the link establishment. Right now it has to be in
/usr/local/sbin/mpd.script, and it's linked to /var/etc/ at boot time when ppp
is first configured. I also took away the "Dialcmd" field in the PPP setup page
(and a couple others) because the script is rather comprehensive and is designed
to handle many modems. My two 3G modems worked without modification to the
script. I did have to modify the scrip to handle the setting of APN and SIM
PINs.
I made the Init String field work, and the default init commands in the ATT&T,
Verizion, and Sprint defaults now come up in the Init String field. You also no
longer should put an "AT" at the beginning of modem commands entered in the web
page because the script does that for you. I implemented interface renaming and
that simplified the new code a lot, so that's nice. Now ppp interfaces start
with ppp0 and go up as you add more.
This patch refers to the ppp-linkup and linkdown scripts in the /usr/local/sbin/
directory so custom PPP linkup and linkdown scripts are not needed anymore.
The persistent uptime tracking is still an open issue, but it works within each
connected session. I'm already experiencing much smother conditions with mpd5
for PPP on 3G than I was with userland ppp. It's very nice.
on the "Status-> Interfaces" page, and also logging on /conf (to
survive reboot) of uptimes of each session after it is closed. In
addition, the status_interfaces.php page displays the cumulative
uptime total so users can manage their links that are on pay by the
minute arrangements.
Shortcomings: partial minutes are just added as cumulative seconds
where most providers probably charge you for a minute after you're 1
second into that minute. I may fix this later.
Submitted-by: Gabriel B
First, I update the get_real_interface function so that it returns just the serial port for the ppp device (instead of ppp_<serial_port>) when the ppp link is not up. This makes the function more useful because now you can call the "interface_ppp_configure" function and pass in the the result of "get_real_interface($wan)" for example.
I also changed the method that the "get_real_interface" function uses to get the tunnel interface name when the ppp link is up. I found that when my 3G modem was in a low signal area, the ppp link would come up partially, and not receive an IP address. If this occurred the web GUI would report that my WAN interface was "pflog0" because the method of chopping up the "ps aux" and "ifconfig" system calls didn't account for the tunnel being partially up (ppp running, but no connectivity.) The userland ppp program puts two files into /var/run when it is running. One is /var/run/<serial_device>.if which contains the interface name that the serial device is attached to, and the other is /var/run/tunX.pid which is the process id for the ppp instance using "tunX."
These two files are more simple and reliable methods of controlling and figuring out what's going on with the ppp link.
Second, I added a function to interfaces.inc called "interface_ppp_bring_down" which figures out the pid using the /var/run/tunX.pid file and sends a kill -QUIT signal to the ppp process.
Third, I modified interfaces_ppp_configure and interface_ppp_configure functions so that
1. The ppp interface is not brought up automatically when you save the configuration because this presents problems for defining ppp.conf entries for diagnostic purposes.
2. You can call interface_ppp_configure from other functions (like interface_configure($interface)) and not have to write the ppp.conf file to the disk when you just want to bring the link up.
Fourth, I added "interface_ppp_configure($realif)" to the function definition of "interface_configure" and "interface_ppp_bring_down" to the function definition of "interface_bring_down". These allow good integration into the existing code for bringing interfaces down and up from the status_interfaces.php page.
Finally, I modified the status_interfaces.php file so that you get a button to "connect" and "disconnect" the ppp wan link.
1) Redefine page privileges to not use static urls
2) Accurate generation of privilege definitions from source
3) Merging the user and group privileges into a single set
4) Allow any privilege to be added to users or groups w/ inheritance
5) Cleaning up the related WebUI pages
