[pptp-server] Re: Numerous IPX Questions (PoPToP mailing list)
tmk
tmk at netmagic.net
Wed Sep 1 19:00:19 CDT 1999
i can't help you with everything, but as far as the tty goes, it's ttyS1 for /dev/pty/1.. i don;t have my 2.2.x kernel with me, so i can't say for sure right now.. anyone care to verify or correct me? You could also do a [ps xww] to see what tty pppd is getting called with, i don't think it's /dev/pty/?
pppd has options to do ipx network numbers and such. [man pppd] =)
basically, once you get options files going, you have ipx going
Kevin
here's some cut/paste's
ipx Enable the IPXCP and IPX protocols. This option is
presently only supported under Linux, and only if
your kernel has been configured to include IPX sup-
port.
ipx-network n
Set the IPX network number in the IPXCP configure
request frame to n, a hexadecimal number (without a
leading 0x). There is no valid default. If this
option is not specified, the network number is
obtained from the peer. If the peer does not have
the network number, the IPX protocol will not be
started.
ipx-node n:m
Set the IPX node numbers. The two node numbers are
Set the IPX node numbers. The two node numbers are
The first number n is the local node number. The
second number m is the peer's node number. Each
node number is a hexadecimal number, at most 10
digits long. The node numbers on the ipx-network
digits long. The node numbers on the ipx-network
option is not specified then the node numbers are
obtained from the peer.
----- Original Message -----
From: Andrew Miklas
To: tmk at netmagic.net
Sent: Wednesday, September 01, 1999 1:31 PM
Subject: Re: Numerous IPX Questions (PoPToP mailing list)
Hi there,
Sorry about the long delay, just wanted to ask you a bit of stuff about the info in your post.
>can ipx be routed? not really. Unless i missed the release of the ipx
>routing tools, ipx is still client-only in the later versions of linux
>(2.2.x kernels) there was an ipxroute util for 2.0.x i believe.
I think it can be routed. I am trying to use a package called ipxripd, but am having a bit of trouble using it. However, once this routing daemon is running properly, it should be able to route between all IPX networks attached to the computer, including the main IPX network on eth1 and the IPX network on the pppx series.
>poptop uses code that returns a free tty, usually ttyS?? on linux
>machines. Perhaps a better way to do custom configs based on who's calling
>would be to use the /etc/ppp/ip-up script (gets called whenever a ppp
>connection starts) and use one of the many bits of info it gives you
>(local ip, remote ip, ppp device, etc) to set routing info or other
>conifigurations. See the ppp-howto for more on this.
PoPToP doesn't seem to be returning a free tty. When I add a command like "echo $2 > /thefile.txt" to my ip-up script, the result is /dev/pts/1. As well, the PoPToP log has a line something like ppp0 <-> /dev/pts/1. I don't think I can make a file like options./dev/pts/1, and options.1 also doesn't work. Using the IP-UP script to handle the routing is a great idea, except that the trouble I am having is seting IPX network and node numbers. I don't think these can be set by a script after PPPd has already initilized the interface using the settings it has found in options. How, therefore, can I allow more than one user establish a VPN, and be able to use IPX over it, while still keeping it the servers responsibility to set network addresses, and local/remote node numbers?
Thanks for any help,
Andrew Miklas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schulte.org/mailman/private/pptp-server/attachments/19990901/fa1e373f/attachment.html>
More information about the pptp-server
mailing list