sudo aptitude install postfix libsasl2 ca-certificate libsasl2-modules

You want to add the fowling lines to your /etc/postfix/main.cf

relayhost = [smtp.gmail.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/gmail_passwd
smtp_sasl_security_options = noanonymous
smtp_tls_CAfile = /etc/postfix/cacert.pem
smtp_use_tls = yes

You need to edit /etc/postfix/gmail_passwd and add the fowling information below, edit it to fit your needs.

[smtp.gmail.com]:587    UserMame@gmail.com:PassWord

Next you need to turn the gmai_passwd file into something that postfix can understand, you can use the command below to accomplish that.

sudo chmod 400 /etc/postfix/sasl_passwd
sudo postmap /etc/postfix/sasl_passwd

Now you can restart postfix but it will complain about not being able to authenticate the certificate.  In order to fix the problem we will use the ca-certificate package we installed earlier to tell it where it can validate the certificate.

cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a /etc/postfix/cacert.pem

Now restart postfix for the final time.

/etc/init.d/postfix

user:/var/www/core# ls -l
total 56
-rw-r–r– 1 root     root      213 2009-06-01 07:14 \
-rw-r–r– 1 user user 378 2009-05-21 09:14 ads.php

We try to delete it but it is not possible because the back slash is a special charter.

user:/var/www/core# rm \
>

So we have to go and list out the inode numbers.  Those are the inode numbers in the first collum.

user:/var/www/core# ls -li
total 56
458132 -rw-r–r– 1 root     root      213 2009-06-01 07:14 \
457759 -rw-r–r– 1 user user 378 2009-05-21 09:14 ads.php

So now we use find to delete the inode number which in turn deletes the file.

user:/var/www/core# find . -inum 458132 -exec rm -i {} \;
rm: remove regular file `./\\’? y
user:/var/www/core# ls -l
total 52
-rw-r–r– 1 user user 378 2009-05-21 09:14 ads.php

When you go and ask the smiley commission paid sales agent what operating systems they support you are just setting your self for the line “no we only support Windows”. Let me start by explaining that all your phone is doing when it is connecting from your phone, what ever weird prosperity connector you have to your phone to the usb on your computer on. Even if you have to be one of the special few that has enough money to spend on a pcmcia EV-DO card. They use ppp through the USB interface standard. The reason that the companies who deployed these deices decided to use two of most widely known, understood and devolved on no matter what OS you are using, is because it was easy. It is as simple as that, the two standards where arlready out there and devoped so why not use them. That same reason the ppp and USB are used is the very reason that even though the silly sales person tells you that it is not supported does not mean that it will not work great.

Apple – I just wanted to start off with apple for the very fact that with OSX there is not additional software that needs to be installed. It is the easiest out of the operating systems out there to set you pone up to the internet. I wish I could include some screen shots but the only time I did use OSX for any sort of extended time was the company that I worked for let me take home one for their laptops. It was really a beautiful thing, it also easily integrated with the built in blue tooth where it could just leave my phone in my pocket while I rode on the train to and from work and the computer could dial the internet completely wirelessly.

Then there is Windows the only operating systems that is supported by Any of the cariers. One of the benefits that Verizon does offer when using Windows is that they offer a program the not only makes it very easy to connect to the Verizon Wireless ISP but they make it possible to download compressed data.

I have to admit that Verizon Wireles is the one that I am most fimilar with, I have done research into some of the competitors.

Some of the other competitors to verizon are Sprint which also uses the cdma standard. But under the Sprint TOS (Term of Service) states they are not allowed to connect a computer to their phone. They are only suppose to use their phone to connect to the internet using the browser that is installed directly on their phone. Now you are saying tht a http request is a http request, and how is Sprint supose to tell the difference. Well the second that you start using any internet application Sprint knows that does not run on your phone such as IRC. They would be within their rights to cut of your service, and or charge you for your internet usage.

Then there is Cingular / At & T which is happy to let you your phone service to connect to the internet but just be ready to pay through the roof on per kb charges. Yes you heard that correctly Cingular charges per the kb unless you buy the unlimited plan which is in my opinion just too expensive.

Then there is the third cellular carier in the US Nextel which uses iDen. I am not fimilar with how well nextel works with their data plans.

You are already paying through the roof for you cell phone. Why not get the most of it that is possible.

This is neat little trick that I have been using for a couple of year

Dial up codes

Verizon

Number to dial: #777

Username: phonenumber@vzw3g.com

Password: vzw

Sprint

Number to dial: #777

Username: username@sprint.com (vision login)
Password: Vision Password

]]> http://www.hacktopia.net/wp/internet-through-you-cell-phone/feed/ 0 http://www.hacktopia.net/wp/set-up-pptp-vpn-server-on-debian-40/ http://www.hacktopia.net/wp/set-up-pptp-vpn-server-on-debian-40/#comments Thu, 08 Jan 2009 03:33:54 +0000 admin http://www.hacktopia.net/wp/?p=67 While being the simplest of the VPN serveer to set up for linx it is also the least secure.  While it is the least secure it is still much better then using nothing.  A quick search for pptpd will give you PoPToP.

PPTPD is good because is comes as part of the base install for many common operation systems like Windows, OS X, and even the IPhone/Ipod.

In past versions of debian you had to to much more work to get pptp to encript your data like installing kernel modules.  Since kernel 2.6.15-rc1 everything is included by default so all you should do is install pptpd, but lets just run a quick check to make sure.  If you get a failure follow these instructions in order to get MPEE workingDebian MPPE HOWTO.

server:/var/log# modprobe ppp-compress-18 && echo success
success

server:/# aptitude  search pptpd
i   pptpd                                                              – PoPToP Point to Point Tunneling Server

Start by installing it by simply isuing the fowling command.

mini:/# aptitude  install pptpd

The first file you will want to edit is /etc/pptpd.conf. You need to put in the ip range of the clients will be assigned and the virtural ip of the PPTP server.  Mare sure you pick a ip range that is not already used!  The remote IP range below will allow 49 hosts to connect.

localip 10.80.0.1
remoteip 10.80.0.2-50

Next we want to set up the pptpd server options.

username@server:~$ cat /etc/ppp/pptpd-options
name hostname.TLD

refuse-pap
refuse-chap
refuse-mschap
require-mschap-v2
require-mppe-128

ms-dns 192.168.1.1

proxyarp
nodefaultroute
lock
nobsdcomp
noipx
mtu 1490
mru 1490
#plugin radius.so

I have the plugin radius.so commented out because that is only necessary for when you are using radius to authenicate the clients.  I will be going over how to set that up in a feture post.  In the mean time we will leave it commented out.

Next we have to set up the user accounts.  The user accounts are set up in a file called /etc/ppp/chap-secrets.  The format is pretty self explanatory but I will go over it any way,  the first filed is the user name that the client will enter into their pptp client, the second filed would be the ip of the PPTP server, just leave it as * for now, forth field is the password the client will have to enter, and the list and final field is the ip adress that the client will be coming from, since you most likely will have no idea where the client will be comign from just leave it as *.  Yes I know password is a really bad password, it is just a example.

server:/etc/ppp# cat chap-secrets
# Secrets for authentication using CHAP
# client    server    secret            IP addresses
username     *     password

Now run

mini:/etc/ppp# /etc/init.d/pptpd start
Starting PPTP Daemon: pptpd.

to start the server up.

You should see some entries in /var/log/syslog like the ones below indicating a secessful start.

Jan  7 22:31:58 mini pptpd[13512]: MGR: Manager process started
Jan  7 22:31:58 mini pptpd[13512]: MGR: Maximum of 49 connections available

Dont forget to put in the proper firewall rules and system settings to foward any necessary traffic.  I will inclue a link to the directions in a fiture post.

Start by pluging it in, yaha.  Below is a snip it from dmesg that shows the usb drive being recognized when plunged in.

cfdisk example output

cfdisk 2.12r

Disk Drive: /dev/sdb
Size: 120034123776 bytes, 120.0 GB
Heads: 255   Sectors per Track: 63   Cylinders: 14593

Name              Flags            Part Type       FS Type                  [Label]               Size (MB)
———————————————————————————————————————-
sdb1                                Primary        NTFS volume set                                120031.52

[Bootable]  [ Delete ]  [  Help  ]  [Maximize]  [ Print  ]  [  Quit  ]  [  Type  ]  [ Units  ]
[ Write  ]

Notice that the dmesg output says sdb so the device path will be /dev/sdb, and the first partition will be /dev/sdb1.

sb 5-5: new high speed USB device using ehci_hcd and address 4
usb 5-5: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver…
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
Vendor: Ext Hard  Model:  Disk             Rev:
Type:   Direct-Access                      ANSI SCSI revision: 04
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 10 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 10 00 00 00
sdb: assuming drive cache: write through
sdb: [mac] sdb1 sdb2
sd 2:0:0:0: Attached scsi disk sdb
usb-storage: device scan complete
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 10 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 10 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1

First you have to delete the osx partition.  I suggest using cfdisk.  It is one of my favorite disk formatting command line gui programs.  fdisk /dev/device also works but is a little trickier to use.

The commands below show how to format the drive

server:~# mkdosfs -n “external disk” /dev/sdb1
mkdosfs 2.11 (12 Mar 2005)

Now go and mount the newly created the file system.

mount /dev/sdb1 /mnt/usb

Now you can unmount it so that it is safe to remove the usb device.

server:/mnt# umount /mnt/usb

server:/mnt# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
mini:/mnt#

Now you can disconnect the usb drive.

usb 5-5: USB disconnect, address 4

server:~# mkdosfs -n “external disk” /dev/sdb1
mkdosfs 2.11 (12 Mar 2005)