Package DSL | ||
OPT_PPPOE | OPT_PPTP | OPT_POESTATUS |
The communication via a DSL connection will need the PPPoE package, because the Telekom wonīt give you a real router but just a DSL modem ! Between the FLI4L router and the modem the protocol PPP is used - in this case especially over the Ethernet.
One or two Ethernet adaptors can be used in the FLI4L router:
Best choice will be of course the one with TWO Ethernet adaptors. Then you will have a correct division between the two protocols used - IP and PPP.
But: the "one-adaptor-method" will also work. In this case the DSL modem will simply be connected to your network hub. There might be a slight loss in transfer speed.
If you 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_ETH_N='1' # Only *one* adaptor with IP address! IP_ETH_1_xxx='...' # ...then all the standard parameters...
For PPPOE_ETH you will have to use 'eth1' for the second Ethernet adaptor and you enter *no* IP_ETH_2_xxx variables.
From version 1.5 PPPoE must be defined as circuit. This will enable you to control it via imond/imonc. Therefore you MUST set the following:
START_IMOND='yes'
... see chapter 2.
Default setting: OPT_PPPOE='no'
At this place/variable you should enter a name for the circuit - max. 15 characters. This name will be displayed in the imon client.
Example: PPPOE_NAME='DSL'
This entry will control transfer and (temporary) storage of providerīs name server entries (for duration of this online session) to 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 having transferred the name server IP addresses, all name servers which were entered into DNS_FORWARDERS, will be deleted from file ens.conf AND IP addresses from your provider will be filled into the file ens.conf. After this the local name server will be forced to re-read its configuration. All names which had been resolved up to this time will not be lost/removed from name serverīs 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: PPPOE_USEPEERDNS='no'
Name of Ethernet interface 'eth0' 1st Ethernet adaptor 'eth1' 2nd Ethernet adaptor ... ...
Default setting: PPPOE_ETH='eth1'
Here you must enter user name and password for the specified provider. PPPOE_USER will contain the user name, PPPOE_PASS the password.
WICHTIG:
For a T-Online account you must be aware of the following:
User ID AAAAAAAAAAAATTTTTT#MMMM is a construction of the 12-character "Anschlußkennung", the T-Online number and the "Mitbenutzernummer" (user number). You must set a '#' directly after the T-Online number, if the T-Online number contains less than 12 characters/digits.
If you are (in only very rare cases) not successful with this (may depend on the used "Telekom node"), you must include another '#' between "Anschlußkennung" and T-Online number.
In all other cases (T-Online number with 12 characters/digits) you do not have to enter any '#' characters.
User ID for T-Online must be completed with: '@t-online.de' !
Example:
PPPOE_USER='111111111111222222#0001@t-online.de'
If you want pppd to give any additional debug information as output, you will have to set PPPOE_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.
Synchronous/asynchronous PPP. Possible values: 'yes' or 'no'.
As given in the description of the PPPoE package, it is recommended to use the setting 'no' (asynchronous). This is said to lead to a higher CPU load. So the recommended steps are now: first try/setting: 'no'. If everything is running in a stable condition and you encounter difficulties, you may then use setting 'yes'.
Default setting: PPPOE_SYNCHRONOUS='no'
When you are using two adaptors, you should use the first adaptor for LAN connection and the second adaptor for the connection to your DSL modem.
Only the first adaptor will need IP addresses.
That means:
IP_ETH_N='1' # Only *one* adaptor with IP address! IP_ETH_1_xxx='...' # all usual parameters...
For the second Ethernet adaptor you will have to set PPPOE_ETH to 'eth1' and *no* IP_ETH_2_xxx variables.
From version 1.5 PPPoE has to be defined as circuit and will be controllable via imond/imonc. Therefore you will have to do the following setting:
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 PPPOE_CHARGEINT to '1'.
Sorry, but PPPoE (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: PPPOE_HUP_TIMEOUT will give the time interval for hang-up.
That is why PPPOE_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:
PPPOE_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):
PPPOE_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.