Technical data

4. Packages

PPP_NETWORK PPP_NETMASK PPP_NETWORK holds the network used and variable PPP_-

NETMASK the netmask. These two variables are used by the extra package ’samba_lpd’.

Important: Consider the following:

1. Those IP addresses may not originate from the network address range of the eth-

ernet LANs. Point-To-Point-Conﬁguration must use a separate network address

range!

2. For the Client PC’s connection to the Internet this mini-PPP-network has to be

masked in the same way as the LAN. In order to achieve this extend the list of net-

works to be masked via the variable PF_POSTROUTING_% (Page 57) (see next passage).

3. The client PC should be added to the host table of the DNS server.

Causes:

If telnet or ftp should be used from the client PC to the ﬂi4l router the daemons concerned

on ﬂi4l do a reverse DNS lookup to resolve the client PC. If it is not found in the host

table a connection to the Internet will be established to do this - which is of course

useless. To avoid this enter the client PC in the host table.

Example for PPP Conﬁguration over the serial interface:

PPP_DEV='com1'

PPP_SPEED='38400'

PPP_IPADDR='192.168.4.1'

PPP_PEER='192.168.4.2'

PPP_NETWORK='192.168.4.0'

PPP_NETMASK='255.255.255.0'

and further on in conﬁg/base.txt:

PF_POSTROUTING_N='2'

PF_POSTROUTING_1='192.168.6.0/24 MASQUERADE'

PF_POSTROUTING_2='192.168.4.0/24 MASQUERADE'

The ﬁrst network is the one of the ethernet LAN and the second the one of the PPP

network.

Last thing is to adapt DNS Conﬁguration. Example:

HOST_5='192.168.4.2 serial-pc'

Do not forget to increment HOST_N (Page 93)!

If the client PC is running Windows you have to conﬁgure the dial-up adapter for a PPP

connection to the ﬂi4l router.

If a linux client is used create a shell script on the client (i.e. /usr/local/bin/ppp-on):

186