[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems with pppd




On Tue, 26 Jun 2001, Oded Arbel wrote:
> 
> > compile the kernel module (IMO, simple), write a five line config file and
> > run the daemon.  Set up the routes and you're done.
> 
> hmm.. would you be so kind as to send/post your configurtion files
> (sensitive information removed, of course :-) ?

As far as routes, mine are simple:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.2.1        0.0.0.0         255.255.255.255 UH    0      0        0 cipcb0
192.168.2.0     10.0.2.1        255.255.255.0   UG    0      0        0 cipcb0
..

.and the file:
---
# Surprise, this file allows comments (but only on a line by themselves)

# This is probably the minimal set of options that has to be set

# Without a "device" line, the device is picked dynamically

# the peer's IP address
ptpaddr         10.0.2.1
# our CIPE device's IP address
ipaddr          10.0.1.1
# The static key. Keep this file secret!
# The key is 128 bits in hexadecimal notation.
key             764efa883dda1e11db47671c4a3bbd9e
# my UDP address. Note: if you set port 0 here, the system will pick
# one and tell it to you via the ip-up script. Same holds for IP 0.0.0.0.
me              0.0.0.0:6789
# ...and the UDP address we connect to. Of course no wildcards here.
peer            192.114.47.57:6789
---

For the other machine, switch the ptpaddr and ipaddr addresses and change
the peer address.  Note: you can choose any port instead of 6789.

I just remembered that there's another method besides the static key.  I
chose the static key method because it is simple.  I agree that the DH key
exchange stuff is a bit more difficult to set up..

Actually, I'm trying to get SMB/CIFS stuff to work but having
difficulty.  It may be that the ipaddr/ptpaddr should be something like
10.0.1.1 / 10.0.1.2 instead.  I still haven't got the P-t-P network stuff
straight in my head.. comments?

-Cedar


=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il