|
Home > Archive > Linux/Unix > August 2001 > PPTP for FreeBSD
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| ccieToBe 2001-07-29, 7:01 pm |
| I just got a PPTP server running on a FreeBSD box and thought some of you may be interested in what's involved.
I was origonally going to use PopTop, but found out that its encryption features don't work with the BSD PPP implementation. After some searching the most capable program I could find was MPD Netgraph, so I went with that. I got the server installed very easily, but was having trouble getting clients to stay connected. I kept getting kicked off immediately after establishing a link. It turns out that the problem had to do with a missing encryption parameter in MPD's configuration file.
Overall this is an easy to use program. Each user and connection has to be manually entered in the configuration files, so this may not be practicle for large VPN servers. There will only be a few users of this VPN server though, so it's not a big deal to enter them in. The biggest problem was lack of documentation outside of the man pages. | |
|
| Thanks. I haven't used the programs you mentioned but will give them a try soon. One more test and I will have my CCNP so I haven't had the time to spend with UNIX as much as usual. How are things going? | |
| ccieToBe 2001-08-08, 2:50 am |
| It's good to see you posting again. Right now things are going failrly well, but I wouldn't have told you the same thing yesterday. I spent most of the day running around my college trying to get into the classes I need to graduate in December. I had a lot of trouble with prerequisites and one of the classes not being offered, but I think I'm all set now. I talked to one of the professors who was able to get me a waiver to take the classes I need, and agreed to test me on the class that's not being offered whenever I'm ready. So in December I should graduate with an AS in Networking technologies  After that I'll focus on a BS.
You're going through those exams at a fast clip, congrats on the passes. Is your last exam the troubleshooting one? I've heard that's the toughest. | |
| Randy 2001-08-09, 10:43 am |
| Yes, the TS exam is the only one I have left. I will take the Server+ next, though since Sybex sent me an exam voucher for it, although the CompTIA exams aren't worth much, IMNSHO. Are you going to try for your B.S. after you complete your A.S.? | |
| ccieToBe 2001-08-09, 1:25 pm |
| Yes, I think I'll go for a BS in IT. I was leaning towards CS, but it would take me about a year longer to go the CS route then IT, and in that time I could could almost have a Master's degree. I plan on staying at the community college one more semester after I graduate to get a few more general eduaction requirements out of the way before going on to a University.
After you finish up the CCNP and Server+ you may want to look into Cisco's design exams. I thought the CCDA was a lot of fun to prepare for. Which CCIE are you working towards? | |
|
| I was lokking at the Communications and Services CCIE, but I may look at some of the other options soon. I like dealing with WANs and so on. Just want to be sure of myself before trying the exam . . . it's a bit expensive to be toying with without full preparation.
As for the B.S., yes, it's a good thing to have. I have a pal in his late 40's that I am helping to get through his B.S. in M.E. that he needs for a promotion, so if you don't have one, it can prove very inconvenient later on. And IT does look better than CS . . . a lot of CS degrees that I have seen do not seem to have aged well . . . they seem dated in a way, still teaching COBOL, Assembly and FORTRAN rather than focusing on modern stuff.
By the way here is something that I posted this at Peter's site but I thought you might be interested in it if you haven;t tried it before:
"I just recently found this out and thought that it was cool enough to post, so here goes. You can check your email via TELNET by going to a command line and doing the following:
telnet {www.mymailserver.com} 110
USER {myloginame}
PASS {mypasswd}
STAT
LIST
RETR {n}
DELE {m}
QUIT
Regular TELNET does not encrypt passwords as far as I know so you probably won't be able to use this outside of your own local network . . . most sensible mail servers will not allow you to TELNET into port 110 to d/l your mail, but you might be able to try it all the same. The 'STAT' command lists the number of messages and the mailbox size, the 'RETR {n}' command retrieves 'n' messages (leave the braces off), the DELE {m} command deletes message number 'm',, the 'RSET' command
undoes any changes, and the 'QUIT' command does exactly what you think it would do. I knew that FTP had command that you could use at a command line, but never knew that SMTP was the same way. More information can be had at: http://raddist.rad.com/networks/1998/smtp/smtp.htm -- Anyway, hope this amuses someone for a few minutes." | |
| ccieToBe 2001-08-09, 2:23 pm |
| Yeah, you can telnet into a lot of services. I knew it could be done, but had no idea how beyond specifying the port, so thanks for posting that.
You're right, it is an expensive lab. The lab cost isn't much though compared to the expense of setting up a practice lab  |
|
|
|
|