Next: 4.7 DYNDNS - Dynamic Up: 4. Packages Previous: 4.5 DNS_DHCP - Hostnames,
fli4l supports DSL in three different variants:
You can choose only one of these options, simultaneous operation
isn't possible yet.
The configuration for all variants is similar, so the
general parameters are described at first and then the
special options for the individual variants will be discussed.
DSL-access is handled by imond as a circuit. Therefore
it is necessary to activate imond by setting
(see START_IMOND)
to 'yes'.
The packages all use the same configuration variables, they
differ only by the package name prefixes. As an example:
in all packages the user name is required. The variable is named
PPPOE_USER, PPTP_USER or FRITZDSL_USER
depending on the package. The variables are described indicating
the missing prefix by an asterisk. In concrete examples PPPOE is
assumed but these are valid with any other prefix too.
Set a name for the circuit - max. 15 digits long. This will be shown in the imon client imonc. Spaces (blanks) are not allowed.
Example: PPPOE_NAME='DSL'
This specifies whether the address of the name servers given by the internet service provider at dial-in will be added to the configuration file of the local name server for the duration of the online connection or not.
It only makes sense to use this option for internet access circuits. Almost all providers support these type of transfer by now.
After the name server IP addresses have been transferred, name
servers in DNS_FORWARDERS will be used as
forwarders. Afterwards the local nameserver is forced to
reread its configuration. Previously resolved names will
not be lost from the name server cache.
This option has the advantage of always using the nearest name servers (given the provider transmits the correct IP addresses) thus accelerating the name resolution process.
In case of failure of a provider's DNS server in most cases the incorrect DNS server addresses are rapidly corrected by the provider.
Nevertheless it is necessary to specify a valid name server in
DNS_FORWARDERS. Otherwise the first name request can not
be resolved correctly. In addition the original configuration of
the local nameservers will be restored when terminating the connection.
Default-setting: *_USEPEERDNS='yes'
If you want pppd to be more verbose set *_DEBUG to
'yes'. In this case pppd will write additional informations
to syslog.
Attention: In order to get this to work syslogd has to activated by
setting OPT_SYSLOGD to 'yes' in base.txt.
Provide user ID an passwort for the provider used.
*_USER is used for the user id
*_PASS is the password.
Attention: For T-Online-access consider this:
Username AAAAAAAAAAAATTTTTT#MMMM is put together from a 12 digit 'Anschlußkennung', T-Online-number and 'Mitbenutzernummer'. Behind the T-Online-number follows a '#' (only if its length is shorter than 12 digits).
If this does not work in rare cases put another '#' between 'Anschlußkennung' and T-Online-number.
User ID for T-Online has to have an additional '@t-online.de' at the end!
Example:
PPPOE_USER='111111111111222222#0001@t-online.de'
Infos on user ID's for other providers are found in the FAQ:
Specify the time in seconds after which the connection will be terminated when no more traffic is detected over the DSL line. A timeout of '0' or 'never' stands for no timeout. Using 'never' the router immedeately reconnects after a disconnection. Changing dialmodes is not possible then - it has to stay 'auto'. 'Never' is currently only available for PPPOE and FritzDSL.
Charge-interval: Time interval in seconds which will be used for calculating online costs.
Most provider calculate their charges per minute. In this case put in '60'.
For providers that charge per second set *_CHARGEINT='1'.
Unfortunately for DSL the timing is not fully utilized, as it is the
case for ISDN. In our case a hangup will be triggered after the time
specified in *_HUP_TIMEOUT.
Hence *_Chargeint is only significant for the calculation of
charges.
This times determine when to enable the circuit and how much it will cost. This makes it possible to have different default routes at different times for a circuit (Least Cost Routing). The imond daemon controls route assignment then.
Composition of variables:
PPPOE_TIMES='times-1-info [times-2-info] ...'
Each field times-?-info consists of 4 parts divided by colons (':').
Weekday-period, i.e. Mo-Fr or Sa-Su aso. English and german notations are both valid. For a single weekday write W1-W1 (i.e. Su-Su).
Hours, i.e. 09-18 or 18-09 too. 18-09 is equivalent to 18-24 plus 00-09. 00-24 means the complete day.
Currency-values as costs per minute, i.e. 0.032 for 3.2 Cent per minute. They are used to calculate the actual costs incurred, taking into account the cycle time. They will be displayed in the imon client.
Content can be Y or N, which means:
| Y: | The specified time range will be used as default route for LC-routing. |
| N: | The specified time range is only used for calculating costs but it won't be used for automatic LC-routing. |
Example (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: Times used in *_TIMES have to cover the whole week.
If that is not the case a valid configuration can't be build.
Important: If the time ranges off all LC-default-route-circuits
(``Y'') togethter don't contain the complete week there
will be no default route in these gaps. There will be no
internet access possible at these times!
One more simple example:
PPPOE_TIMES='Mo-Su:00-24:0.0:Y'
for those using a flatrate.
One last comment to LC-routing: holidays are treated as Sundays.
fli4l hangs up automatically if there is no traffic over the pppoe interface in the time specified in hangup timeout. Unfortunately also traffic from the outside counts here, for example connection attempts by a P2P client such as eDonkey. Since you will be contacted almost permanently from outside nowadays, it can happen that fli4l never terminates the DSL connection.
Option *_FILTER comes to help here. Setting it to yes will only
consider traffic that is generated from your own machine and
external traffic will be completely ignored. Since incoming traffic
usually means that the router or computers behind it respond by i.e
rejecting requests additionally some outgoing packets are ignored.
Read here how this exactly works:
Filter to use if *_FILTER is set to 'yes'.
These variables are optional and can be completely omitted.
With these optional variables the so-called MTU (maximum transmission unit) and the MRU (maximum receive unit) can be set. By default MTU and MRU are set to 1492. This setting should only be changed in special cases! These variables don't exist for OPT_PPTP.
For some providern these effects can occur:
To work around this problems fli4l manipulates the MTU as a default. In some cases this is not enough so fli4l explicitely permits setting of the MSS (message segment size) to a value given by the provider. If the provider does not give any values 1412 is a good start to try. If a MTU is given by the provider, subtract 40 Byte here ( mss = mtu - 40). These variables are optional and can be completely omitted. These variable doesn't exist for OPT_PPTP.
For communication via a DSL connection usually the PPPoE package is necessary because the provider does not provide a full blown router, but only a DSL modem. Between the fli4l router and the modem the PPP protocol is used, but in this case specifically over Ethernet.
One or two ethernet cards can be used in fli4l:
The better choice is to use two ethernet cards. This way both protocols - IP and PPPoE - are clearly separated from each other.
But the method with one ethernet cards works as well. In this case the DSL-modem has to be connected to the network hub like all other clients. The maximum transfer speed can be slightly affected this way.
If experiencing communication problems between the modem and the network card you can try to slow down the speed of the NIC, eventually even switching it to half-duplex mode. All PCI cards but only a few PCI-ISA network cards can be configured to run in various speed modes. Either use ethtool from the package advanced_networking or create a DOS boot media and include the native configuration tool there. Start fli4l with this media and execute the card's native tool to choose and save the slower operation mode to the card. The configuration tool usually is available on the driver media or can be downloaded from the website of the card manufacturer. You may also find it in a search in the wiki:
If using two network cards you should use the first for the LAN and the second for the connection to the DSL modem.
Only the first card does need an IP address.
This means:
IP_NET_N='1' # Only *one* card with IP-address!
IP_NET_1xxx='...' # Usual parameters
For PPPOE_ETH set the second ethernet card to 'eth1' and
define *no* IP_NET_2-xxx-variables.
OPT_PPPOE='no'.
Name of the ethernet interface
| 'eth0' | first ethernet card |
| 'eth1' | second ethernet card |
| ... | ... |
Default setting: PPPOE_ETH='eth1'
PPPOE stands for transmission of PPP-packets over ethernet lines. Data to be transmitted is transformed to ppp-packets in a first step and then in a second step wrapped in pppoe-packets to be transmitted over ethernet to the DSL-modem. The second step can be done by the pppoe-daemon or by the kernel. PPPOE_TYPE defines the way of pppoe packet generation.
Somebody did a comparison between the various variants
on a Fujitsu Siemens PCD-H, P75 the results are shown in table
4.3 4.3.
|
Using PPPoE-type in_kernel and dialmode auto, timeout can be set to 'never'. The router then no longer hangs up and after a forced disconnection by the provider dials again automatically. Subsequent changing of the dialmode is not possible anymore.
Internet connection by Fritz! Card DSL is activated here. A
Fritz! Card DSL by AVM is used for the internet connection.
Since the drivers for these cards are not subject to the GPL
it is not possible to provide them with the DSL package. It is
essential to download these drivers before from
http://www.fli4l.de/download/stabile-version/avm-treiber/
and to extract them into the fli4l directory.
Circuit-support for Fritz!Card DSL was realised with friendly help from Stefan Uterhardt (email: zer0@onlinehome.de).
OPT_FRITZDSL='no'.
Several Fritz!-cards exist for a DSL connection. The card used will be specified by FRITZDSL_TYPE, have a look at table 4.4 for enumerating the supported cards.
|
Default setting:
FRITZDSL_TYPE='fcdsl'
With this option the type of the remote station is set. Possible options are:
U-R2, ECI, Siemens, Netcologne, oldArcor, Switzerland, Belgium, Austria1, Austria2, Austria3, Austria4
In Germany almost always UR-2 i used. Siemens and ECI are only used with very old ports.
For Switzerland and Belgium, the options are self-explanatory and in Austria you
have to try what works for you.
If anyone has a better description for the options in Austria please tell.
Default setting:
FRITZDSL_PROVIDER='U-R2'
In Austria (and other european countries) PPTP-protocol is used instead of PPPoE. A separate ethernet card is connected to a PPTP-Modem in this case.
As of version 2.0 connecting via PPTP is realised as a Circuit - with the friendly help of Rudolf Hämmerle (email: rudolf.haemmerle@aon.at).
PPTP uses two cards. The first card should be used for connecting the LAN and the second for connecting to the DSL-modem.
Only the first card can have an IP-address.
This means:
IP_NET_N='1' # Only *one* card with IP-address!
IP_NET_1xxx='...' # the usual parameters
PPTP_ETH is set to 'eth1' for the second ethernet card and *no* IP_NET_2-xxx-variables are defined.
OPT_PPTP='no'.
Name of the ethernet interfaces
| 'eth0' | first ethernet card |
| 'eth1' | second ethernet card |
| ... | ... |
Default setting: PPTP_ETH='eth1'
There are several PPTP modem types to realise a pptp connection.
Define PPTP_MODEM_TYPE to define the modem type. Possible
types are shown in table 4.5.
|
Default setting:
PPTP_MODEM_TYPE='telekom'
Support for Inode xDSL@home was implemented using information found on Inode's support pages4.4.
At the moment there are sometimes problems with renewing of leases for the interface (the IP for the interface is delivered by dhcp and has to be renewed in regular periods). Hanging up and reconnecting via imonc does not work well by now. Help by providing patches or as a tester is highly appreciated.
With xdsl two further options exist for pptp:
The pptp-client which is used for xdsl under certain circumstances must rearrange and buffer packets. It usually waits 0.3 seconds for a packet. By setting this variable you can vary the timeout between 0.00 (no buffer) and 10.00. Times always must be provided with two decimales.
Here you can define how much debug output will be produced by the pptp-client. Values are 0 (little), 1 (default) und 2 (much).
PPPoE-Status-Monitor for DSL Connections was developed by Thorsten Pohlmann.
With setting OPT_POESTATUS='yes' dsl status can be watched
on the third fli4l console at any time. Switch to the third console
by pressing ALT-F3 and back to the first console with ALT-F1.