| Package DSL | ||
| OPT_PPPOE | OPT_PPTP | OPT_POESTATUS |
In Austria (and other european countries) PPTP protocol is used instead of PPPoE. Again a separate Ethernat adaptor is connected to the PPPTP modem.
From version 2.0 access via PPTP is realized as a circuit - with friendly support by Rudolf Hämmerle <rudolf.haemmerle@aon.at>.
Since it is a fact that a PPTP connection is very similar to a PPPoE connection, some of the remarks for PPPoE are also valid for PPTP..
For PPTP you will use two adaptors. You should use the first adaptor for the LAN connection and the second one for connection to the DSL modem.
Only the first adaptor will need IP addresses.
That means:
IP_NET_N='1' # Only *one* adaptor with IP address!
IP_NET_1xxx='...' # ...then all the standard parameters...
For PPTP_ETH you will enter 'eth1' for the second Ethernet adaptor and *NO* IP_NET_2_xxx variables !
From version 2.0 PPTP has to be defined as circuit and will then be controlable via imond/imonc. Therefore you MUST set:
Enter a name for the circuit here - max. 15 characters. This name will be displayed in imon client. Blanks are not allowed!
Example: PPTP_NAME='DSL'
Here you will define, if name servers which are transmitted from your provider for this session, will be stored (temporarily) in the configuration file of the local name server ens.
This option only makes any sense when you are using circuits for internet providers.
In the meantime almost every provider supports this kind of transfer.
After transmission of name server IP addresses, all name servers which had been entered in
DNS_FORWARDERS
will be removed (temporarily) from file ens.conf and all IP addresses tranmitted from your provider will be entered into file ens.conf as forwarders. After this the local nameserver will be forced to again read its configuration. All resolved names will NOT be removed from name server cache.
This option offers the opportunity to work with the nearest mane servers, if the provider transmits the correct IP addresses - this will fasten name resolution.
If one of the DNS servers failed, the transmitted DNS server addresses will usually be corrected quite fast by the provider.
But, nevertheless you will have to give - before first connection - a valid name server via DNS_FORWARDERS. Otherwise there will be no correct resolution for the first attempt of access. Additionally the original configuration of the local name server will be restored when the connection is closed!
Default setting: PPTP_USEPEERDNS='yes'
Name oh Ethernet interface
'eth0' 1st Ethernet adaptor
'eth1' 2nd Ethernet adaptor
... ...
Default setting: PPTP_ETH='eth1'
Here you must enter user name and password for the specified provider. PPTP_USER will contain the user name, PPTP_PASS the password.
If you want pppd to give any additional debug information as output, you will have to set PPTP_DEBUG to 'yes'. Then ipppd will write additional information via the syslog interface.
IMPORTANT: To get an output via syslogd, you will have to set variable OPT_SYSLOGD also to 'yes' .
Here you should enter the amount of time after which connection shall be closed if there isnīt any traffic on the DSL line.
In Austria there are two different PPTP modems possible. This must be selected via PPTP_MODEM_TYPE. Description is 'bbaa' oder 'bcaa'.
Users of provider MXSTREAM in the Netherlands must enter 'mxstream' here.
Default setting: PPTP_MODEM_TYPE='bcaa'
Charge-Interval: Enter charge interval in seconds. This value will be used for cost calculation.
Most providers will calculate connection costs in minute intervals. If that is the case, a value of '60' would be correct. If you have a provider who calculates on a second base it would be better to set PPTP_CHARGEINT to '1'.
Sorry, but PPTP (DSL) will not use the full charge interval as it is done for ISDN. For the DSL connection the following is valid: The time given in: PPTP_HUP_TIMEOUT will give the time interval for hang-up.
That is why PPTP_CHARGEINT is only valid for calculation of connection costs.
This section gives information about times when this circuit shall be activated and at which time it will be a connection at which costs. This will enable you to use different circuits with default routes at different times (least-cost-routing). Daemon imond will control the route assignments.
Construction of variables:
PPTP_TIMES='times-1-info [times-2-info] ...'
Each field times-?-info consists of four sub-fields - divided by colons (':')
1st field: W1-W2
day of the week interval, ex.: Mo-Fr or Sa-Su, etc.This data may be written in german or english syntax. If you want to enter one single day of the week, this must be done like this: Su-Su.
2nd field: hh-hh
Hours interval; ex.: 09-18 or 18-09. 18-09 is the same as: 18-24 plus 00-09. 00-24 means: the whole day.
3rd field: Charge
Here you may enter (in DM values) costs per minute; ex.: 0.032 for 3.2 Pfennig per minute. These will be calculated, depending on charge time/interval, for real existing costs, which will then be displayed in imon client.
4th field: LC-Default-Route
Content can be: 'Y' or 'N'. Meanings are:
Y: The given time interval will be used as default route for LC routing.
N: The given time interval is only used for costs calculation; it will not be used for automatic LC routing.
Example (to be read as one long line):
PPTP_TIMES='Mo-Fr:09-18:0.049:N Mo-Fr:18-09:0.044:Y Sa-Su:00-24:0.039:Y'
Important:
If all time intervals of all LC default route circuits ("Y") - if summed up - do not include the complete week, there will be NO default route in times without any definition. This would mean: no internet surfing during these (undefined) time intervals!
Another simple example:
PPPOE_TIMES='Mo-Su:00-24:0.0:Y'
For those who use a flatrate.
One last remark to LC routing:
Holidays will be treated as Sundays.