Help on ppp server

[Raju_8]

Hello Every Body,

Iam from India and I am a novic in networking . I want to network our head office and one branch using the ordinary 56kbps dial up line. I am using RedHat Linux 8 for this . My head office and branch office servers are using RedHat linux 8 and both offices have about 10 windows98 Clients connected to the linux server. I am using Postgresql as data base .
I want to dial up between the two RH servers and access the Head office windows 98 client from the Branch office Windows 98 Client and vice versa by supplying the IP address. Now the problem is that When I dial from the branch office Server I can ping the HO server and from the head office server i can ping the branch office server. But I can't access the branch office clients or the head office clients through the network. My network configuration is as follows.


Server IP No : 192.168.1.30 net mask 255.255.255.0 Gate way 192.168.1.254 and Primary name server 192.168.1.1
Clients IP nos :192.168.1.20 to 192.168.1.29

The head office and branch office are using the same IP configuration

I have changed the following things to set up the server

1. /proc/sys/net/ipv4/ip_forward to 1
2. Modified /etc/sysconfig/network and changed
FORWARD_IPV4=true.
3. Edited and added the following line to /etc/inittab
S0:2345:respawn:/sbin/mgetty ttyS0 -D /dev/ttyS0
4. Changed pppd permission to chmod u+s /usr/sbin/pppd
6. Next, changed the /etc/mgetty+sendfax/login.config to
/AutoPPP/ - - /usr/sbin/pppd file /etc/ppp/options.server
7. Next added the following stuff to /etc/ppp/options.server file

-detach
asyncmap 0
modem
crtscts
lock
require-pap
refuse-chap
login
proxyarp


8.Nnext edited /etc/ppp/pap-secrets file and added the follwing line

* * "" *

9.Created the file /etc/ppp/options.ttyS0 and added the following line to it
192.168.1.30:192.168.1.72


I am using kppp to connect to the server using the default options


is any one can help me ?

Thanks in advance

Raju.

[Vincent Fleming]

Your problem is that you are using 192.168.1.* for the dial-up ip addresses. It's making the clients think that the remote site is on the same LAN segment, which it is not.

Try using another LAN address for the remote links, such as 10.1.1.* (one would be 10.1.1.1, and the other 10.1.1.2), and make sure IP forwarding is enabled.

You could make it work by changing the netmask, but that's not for novices. It's complicated, and the 10. addresses will work just as well.

Good luck,

Vince