You need the tunnel.o (ip-tunnel?) module and de CIPE tools?? Check out the CIPE Howto.
common cave at's:
1) Avoid masquerading the network addresses used for VPN. 2) Ensure forwarding is turned on for the VPN network addresses used (very easy to forget this!) 3) If you must use masquerading consider using multiple network addresses on a particular LAN from different network numbers.
paul: anyone for an update on this please?
First of all, you MUST read Bugtraq and NTbugtraq and see how flaky and unsafe Microsoft implemented encryption. their PPTP sucks. I wouldn't trust it for one bit. But ofcourse, your PHB wants it anyway, so here are some hints:
PPTP stands for "Point to Point Tunneling Protocol". While the IETF does have some RFC's out for "generic" PPTP (aka, Virtual Private Networking), I need support for Microsoft's, ahem, delightful rendition. Their PPTP requires two special hooks in the router and all routers between the cooperative nodes: - port 1723 needs to be "open" - GRE (IP protocol 47) needs to be available and forwarded
http://www.wolfenet.com/~jhardin/ip_masq_pptp.html has all the details. That page states that a couple of kernel patches are indeed required to make what I want to happen fly. (FWIW, I already can PPTP when I use M$'s dialup networking schlock, but then my wife and kids on the in-house LAN can't surf the net, which is the whole reason I want LRP in the first place!)
It's not yet in the LRP kernel AFAIk
Yes, check the ident package on the ftp site. It might need some updateing. Anyone?
Check out Angel Martín Alganza's page
Pre patches by Alan Cox: at Alan's ftp site Port Forwarding
RADIUS - Remote Authentication Dial-In User Service
RADIUS Server: Program (daemon) that contains a list of usernames and passwords and the respective service (RADIUS service, not /etc/services) they are to be authorized for.
RADIUS Client: Program (daemon(s)) that controls the hardware, obtains username and password, communicates with RADIUS server, and starts appropreate service after authorization. The server and client need not be the same platform
Portslave is a radius client that deals with inbound serial lines (modem) and can handle outbound PPP, SLIP, telnet, and rlogin services. You can also hack portslave to handle 'answering' telnet connections. (Keep shell users in a radius file) PAM - Plugable athentication module. A linux program standard to back-end authentication. Their is a Radius-PAM that will also authorize off your RADIUS server. Solaris supports PAM as well.
PAM is not (yet) widely used, but it makes a RADIUS server as a single user database host even more attractive. In the same token the RADIUS server can use PAM to get use information from things like yp, NIS, or a database, instead of it's default text file.
See:
You need the tunnel.o (ip-tunnel?) module and de CIPE tools (?) Check out the CIPE pages.
common cave at's:
Network monitors available
See also, ipgrab, tcpdump, sniffit
Try these:
- tcpdump - ipgrabber - iptraf - sniffit - iplogger-ident