1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
The "to do" items below are listed on a "current priority" basis, i.e.
the one I'm most inclined to work on is the one listed first, while the
rest further down will be addressed in the near future. If it is your
feeling that some item should be "bumped" up to a higher priority,
please do drop me a line :) Also if you've come across some problem
mentioned below, please do provide any type of feedback you deem would
speed up finding a solution.
- Enable verbose chat execution when in debug mode, but only for pppd
versions 2.3.x and later. Enable selecting "-nohints" and "-debug"
from within the GUI ("-debug" turns on chat verbose mode also).
- Add internationalization patches by Ricardo Stefani.
- Support for domain name: to be added to /etc/resolv.conf together
with the DNS server IP addresses.
- Add extra option for "Other" port speed to accommodate "strange"
ports and/or modems.
- Implement control for reseting logs.
- Edit post-connect/post-disconnect commands from within xisp,
for execution as user and/or possibly as root (via strings
passed to .xisp-up/-down).
- Investigate memory bloat :)
- Think about implementing tx/rx blinkies and/or packet-traffic or even
better byte-traffic indicators a la xload (now that kernel 2.2.x is out).
- Investigate possibility of implementing a special "script-interrupt"
specifier (e.g. %?) in user script lines. Upon detection of such an
"interrupt", xispdial would "cut" the generated script at that point,
pass it to chat, and when chat returns, pop-up a window for user
input, read a string, then assemble the rest of the script using this
string, and either finishing, or continuing with the next script
"interrupt". Such a scheme would greatly enhance SecurID (and the
like) logins.
Alternatively merge Jim Shallman's simple code for a SecureID prompt.
- Investigate manual dialing option with interrupt, hang-up etc.
buttons.
- Support charging plans by ISPs that e.g. charge a fixed tariff for a
maximum amount of connection time (e.g.) per month, and apply normal
charges from that point on.
- Implement feature for stopping dial attempts beyond a limit set by
the ISP's "access plan". xisp should keep track of successful dials
(or logins) and a) refrain from dialing when the limit is exceeded
(possibly allowing an override), and b) notify the user through a
number of ways (mail, console message, pop-up window etc.). The
limit shall be defined as a number of maximum dials per fixed time
periods (minutes, hours, days, months).
- Implement something similar to the above, but for connection time.
Here, xisp should disconnect if a fixed amount of connection time has
been reached for the period under consideration.
- Implement feature for not accepting connections below a certain
speed "threshold". This can be used to pick a "good" phone line,
or a higher speed modem if not all are of same speed. This is also
implemented via init commands in some modems (e.g. US Robotics).
- Move the PTT/Zone selection from the "global" section into each
ISP entry and investigate possibility of adding ISP cost on top
of PTT costs in logging.
This must be implemented together with the following:
- Do logging on a per-ISP basis as one can have ISP's using different
charging zones and possibly different PTT's.
- Support two phases for .xisp-down: one immediately *before*
disconnecting and one immediately after (i.e. call twice). If any
one reading this wants to do something before disconnecting using
the current version, the SIGUSR1 and SIGUSR2 remote-control
capability should give you some ideas (read the xisp(1) manual page).
- Do the same for .xisp-up.
- Option for online display to flip between time and charge every 5
seconds (when it updates - same for icon title). Or, maybe flipping
between cost and a countdown to the next charge unit. Possibly add
special sound(s) 10s (or so) before next unit and/or when changing
charging rule.
- Support "collapsed" state, with maybe only a single button. Useful
for fvwm2's button bar, or for small resolution displays (e.g. on
a laptop).
- Have "logical" modems instead of saving modem info with ISP info;
every ISP entry could then use any one logical modem.
- Support "idle disconnect" by monitoring the packets flowing through
the PPP interface, and/or use the "idle-disconnect" capabilities
in pppd-2.3.x
- Investigate possibility of xisp working together with diald.
- Automatic chat-script generation from one terminal-login.
- A status bar showing the dialing progress.
|
