Sponsored Content
Full Discussion: Four PCs Sharing ADSL
Top Forums UNIX for Dummies Questions & Answers Four PCs Sharing ADSL Post 31797 by PxT on Wednesday 13th of November 2002 02:17:04 PM
Old 11-13-2002
Couple of problems i noticed in your post:

On the machine connected directly to the DSL line, your external interface needs to have a real routable IP address. You should have received this from your ISP (or maybe it is DHCP). It looks like you are using 192.168.0.1 which is a non-routable address.

In your iptables command, you are telling it to masquerade out the ppp0 interface. It doesnt sound like you are using dialup, so you should replace that with eth0 or whatever your external interface is.
 

9 More Discussions You Might Find Interesting

1. IP Networking

Unix and ADSL

Is ADSL support available for Unix/Linux? If I want to set up a internet server, will it have to be Windows with a seperate unix box? Or can it be a clean unix server? (2 Replies)
Discussion started by: vannie
2 Replies

2. UNIX for Dummies Questions & Answers

PPPoE + ADSL on FreeBSD 4.4

Hi everyone, This is basically my problem. I setup freebsd, and wanted to get my adsl connection up which uses pppoe to connect. I followed the steps in this (http://free.mine.nu/~squirrel/PPPoE/FreeBSD%20PPPoE%20Howto.htm) manual and configured everything successfully. The problem begins when i... (7 Replies)
Discussion started by: Luftwaffe
7 Replies

3. UNIX for Dummies Questions & Answers

ADSL with Darwin 1.41

Hey everyone, just to let you all know "I'm an uber n00b" I'm connected to Telstra Bigpond's (Australian ISP) ADSL network, now I;m running Darwin 1.41 on an Apple Macintosh PPC computer. I don't know how to set up ADSL on this system, can someone please guide me. (3 Replies)
Discussion started by: Syphor
3 Replies

4. Solaris

Solaris 10 ADSL USB modem problem

Hi, I have USB Siemens Santis 100 ADSL modem.I need driver for this modem on Solaris 10.Please help me with some info.Platform is x86.Thanks. (2 Replies)
Discussion started by: Upravnik
2 Replies

5. IP Networking

sharing of IP address for load sharing avoiding virtual server & redirection machine

I have RedHat 9.0 installed on three of my servers (PIII - 233MHz) and want that they share a common IP address so that any request made reaches each of the servers. Can anyone suggest how should I setup my LAN. I'm new to networking in Linux so please elaborate and would be thankful for a timely... (2 Replies)
Discussion started by: Rakesh Ranjan
2 Replies

6. Solaris

Installing USB adsl modem?

Hello all, granted that I am an absolute beginner with Solaris, I'd like to use my adsl modem, t's a Zyxel prestige 630. I managed to install and configure it under Ubuntu using the drivers from Conexant AccessRunner ADSL USB modems with Linux ; is there a chance to do the same under Solaris 10... (0 Replies)
Discussion started by: clalfa
0 Replies

7. IP Networking

Sharing Adsl Link

Hi guyz, got a little bit of a situation here. we are sharing an ADSL link with another organization. so there are 2 networks. network 1: has the adsl router and the whole n/w is on subnet 192.168.0.* the adsl router has its ip as 192.168.0.1 network 2(now us): we have set up a linux... (0 Replies)
Discussion started by: royashoya
0 Replies

8. Shell Programming and Scripting

Using Net::Telnet in Perl to connect to an adsl modem

Hello, First of all, congratulations on this forum! Very mice material! This is my fist thread and it has to do with connecting to an adsl modem and executing some commands. Heres what I do: $username = 'admin'; $passwd = 'admin'; $telnet = new Net::Telnet ( Timeout=>10,... (2 Replies)
Discussion started by: Ravendark
2 Replies

9. IP Networking

Configuring ADSL/3G/4G connectivity with Failover and Fallback capability

Hello All, I have one requirement in which, i have 3 connections one ADSL and two 4G dongle (Jio/Airtel). Where i need to configure ADSL and 4G connections, which i have configured and able to connect internet throught them, Now i need to create set-up for failover and fall back between them,... (0 Replies)
Discussion started by: linux.amrit
0 Replies
PPTPD.CONF(5)							File Formats Manual						     PPTPD.CONF(5)

NAME
pptpd.conf - PPTP VPN daemon configuration DESCRIPTION
pptpd(8) reads options from this file, usually /etc/pptpd.conf. Most options can be overridden by the command line. The local and remote IP addresses for clients must come from the configuration file or from pppd(8) configuration files. OPTIONS
option option-file the name of an option file to be passed to pppd(8) in place of the default /etc/ppp/options so that PPTP specific options can be given. Equivalent to the command line --option option. stimeout seconds number of seconds to wait for a PPTP packet before forking the pptpctrl(8) program to handle the client. The default is 10 seconds. This is a denial of service protection feature. Equivalent to the command line --stimeout option. debug turns on debugging mode, sending debugging information to syslog(3). Has no effect on pppd(8) debugging. Equivalent to the command line --debug option. bcrelay internal-interface turns on broadcast relay mode, sending all broadcasts received on the server's internal interface to the clients. Equivalent to the command line --bcrelay option. connections n limits the number of client connections that may be accepted. If pptpd is allocating IP addresses (e.g. delegate is not used) then the number of connections is also limited by the remoteip option. The default is 100. delegate delegates the allocation of client IP addresses to pppd(8). Without this option, which is the default, pptpd manages the list of IP addresses for clients and passes the next free address to pppd. With this option, pptpd does not pass an address, and so pppd may use radius or chap-secrets to allocate an address. localip ip-specification one or many IP addresses to be used at the local end of the tunnelled PPP links between the server and the client. If one address only is given, this address is used for all clients. Otherwise, one address per client must be given, and if there are no free addresses then any new clients will be refused. localip will be ignored if the delegate option is used. remoteip ip-specification a list of IP addresses to assign to remote PPTP clients. Each connected client must have a different address, so there must be at least as many addresses as you have simultaneous clients, and preferably some spare, since you cannot change this list without restarting pptpd. A warning will be sent to syslog(3) when the IP address pool is exhausted. remoteip will be ignored if the dele- gate option is used. noipparam by default, the original client IP address is given to ip-up scripts using the pppd(8) option ipparam. The noipparam option pre- vents this. Equivalent to the command line --noipparam option. listen ip-address the local interface IP address to listen on for incoming PPTP connections (TCP port 1723). Equivalent to the command line --listen option. pidfile pid-file specifies an alternate location to store the process ID file (default /var/run/pptpd.pid). Equivalent to the command line --pidfile option. speed speed specifies a speed (in bits per second) to pass to the PPP daemon as the interface speed for the tty/pty pair. This is ignored by some PPP daemons, such as Linux's pppd(8). The default is 115200 bytes per second, which some implementations interpret as meaning "no limit". Equivalent to the command line --speed option. NOTES
An ip-specification above (for the localip and remoteip tags) may be a list of IP addresses (for example 192.168.0.2,192.168.0.3), a range (for example 192.168.0.1-254 or 192.168.0-255.2) or some combination (for example 192.168.0.2,192.168.0.5-8). For some valid pairs might be (depending on use of the VPN): localip 192.168.0.1 remoteip 192.168.0.2-254 or localip 192.168.1.2-254 remoteip 192.168.0.2-254 ROUTING CHECKLIST - PROXYARP Allocate a section of your LAN addresses for use by clients. In /etc/ppp/options.pptpd. set the proxyarp option. In pptpd.conf do not set localip option, but set remoteip to the allocated address range. Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). The server will advertise the clients to the LAN using ARP, providing it's own ethernet address. bcrelay(8) should not be required. ROUTING CHECKLIST - FORWARDING Allocate a subnet for the clients that is routable from your LAN, but is not part of your LAN. In pptpd.conf set localip to a single address or range in the allocated subnet, set remoteip to a range in the allocated subnet. Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). The LAN must have a route to the clients using the server as gateway. The server will forward the packets unchanged between the clients and the LAN. bcrelay(8) will be required to support broadcast protocols such as NETBIOS. ROUTING CHECKLIST - MASQUERADE Allocate a subnet for the clients that is not routable from your LAN, and not otherwise routable from the server (e.g. 10.0.0.0/24). Set localip to a single address in the subnet (e.g. 10.0.0.1), set remoteip to a range for the rest of the subnet, (e.g. 10.0.0.2-200). Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). Enable masquerading on eth0 (e.g. iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ). The server will translate the packets between the clients and the LAN. The clients will appear to the LAN as having the address corre- sponding to the server. The LAN need not have an explicit route to the clients. bcrelay(8) will be required to support broadcast proto- cols such as NETBIOS. FIREWALL RULES
pptpd(8) accepts control connections on TCP port 1723, and then uses GRE (protocol 47) to exchange data packets. Add these rules to your iptables(8) configuration, or use them as the basis for your own rules: iptables --append INPUT --protocol 47 --jump ACCEPT iptables --append INPUT --protocol tcp --match tcp --destination-port 1723 --jump ACCEPT SEE ALSO
pppd(8), pptpd(8), pptpd.conf(5). 29 December 2005 PPTPD.CONF(5)
All times are GMT -4. The time now is 04:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy