Мое решение для подключения модема megafon e1550 , этот метод позволяет не использовать Mobile Partner (у меня эта приблуда ощутимо тормозила )
1) root@test1:/etc/network# lsusb
Bus 002 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
Bus 002 Device 002: ID 80ee:0021  
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
2)root@test1:/etc/network# ls /dev |grep USB
ttyUSB0
ttyUSB1
ttyUSB2
3)проверяем стоит ли в системе пакет ppp (dpkg -l ppp) если его нет доставляем 
4)Создаем файл, я назвал его 3g, в котором мы пропишем команды для нашего соединения.
root@test1:/etc/ppp/peers# mcedit 3g
Далее необходимо вписать следующее:
#это наш модем
connect "usr/sbin/chat -f /etc/ppp/3g"/dev/ttyUSB0
#если у вас гарантированно есть покрытие сетей UMTS(3G), то оставляем как есть, иначе 115400
460800
crtscts
noauth
usepeerdns
defaultroute
#Так как для выхода в интернет через ОпСоСа Мегафон не нужно указывать логи и пароль, оставляем как есть
user ""
password ""

Теперь нам нужно создать файл с именем 3g в /etc/ppp/ и внести в него следующее:
TIMEOUT 35
ECHO ON
ABORT '\nBUSY\r'
ABORT '\nERROR\r'
ABORT '\nNO ANSWER\r'
ABORT '\nNO CARRIER\r'
ABORT '\nNO DIALTONE\r'
ABORT '\nRINGING\r\n\r\nRINGING\r'
ABORT '\nUsername/pASSWORD Incorrect\r'
''  \rAT
OK  'AT+CGDCONT=1,"IP","internet"'
OK  ATD*99***1#CONNECT  ""

Собственно все, для запуска нашего соединения даем команду pon 3g (poff 3g для отключения  ) изаконекчиваемся к нету 

Ахда еще в /etc/network/interfaces нужно прописать  gateway  10.64.64.64
иначе пакеты в нет не уходят 
основу взял с http://tylkas.ru/?p=901

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=4e55e121-cbc6-498d-8227-678e525489f9 /               ext3    errors=remount-ro 0       1
# /home was on /dev/sda6 during installation
UUID=03452e94-e5ca-4c1b-911a-ff33ecbefd6d /home           ext3    defaults        0       2
# swap was on /dev/sda5 during installation
UUID=98c6d08b-3321-447e-86a9-7d8666c4a1c3 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/md0        /my_raid        ext3     defaults           0       0

Во время работы виртуальной машины произошла ошибка! Подробности ошибки приводятся ниже. Вы можете попытаться исправить ситуацию и возобновить работу виртуальной машины.
The I/O cache encountered an error while updating data in medium "ahci-0-2" (rc=VERR_INVALID_PARAMETER). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

root@test1:~# dpkg -l |grep xen 
rc  libc6-xen                          2.11.2-10                    Embedded GNU C Library: Shared libraries [Xen version]
rc  libxenstore3.0                     4.0.1-2                      Xenstore communications library for Xen
ii  linux-headers-2.6.32-5-common-xen  2.6.32-31                    Common header files for Linux 2.6.32-5-xen
ii  linux-headers-2.6.32-5-xen-686     2.6.32-31                    Header files for Linux 2.6.32-5-xen-686
rc  linux-image-2.6.32-5-xen-686       2.6.32-31                    Linux 2.6.32 for modern PCs, Xen dom0 support
rc  xen-hypervisor-4.0-i386            4.0.1-2                      The Xen Hypervisor on i386
rc  xen-utils-common                   4.0.0-1                      XEN administrative tools - common files
root@test1:~# aptitude remove xen-hypervisor-4.0-i386

root@test1:~# dpkg -l |grep xen 
rc  libc6-xen                          2.11.2-10                    Embedded GNU C Library: Shared libraries [Xen version]
rc  libxenstore3.0                     4.0.1-2                      Xenstore communications library for Xen
ii  linux-headers-2.6.32-5-common-xen  2.6.32-31                    Common header files for Linux 2.6.32-5-xen
ii  linux-headers-2.6.32-5-xen-686     2.6.32-31                    Header files for Linux 2.6.32-5-xen-686
rc  linux-image-2.6.32-5-xen-686       2.6.32-31                    Linux 2.6.32 for modern PCs, Xen dom0 support
rc  xen-hypervisor-4.0-i386            4.0.1-2                      The Xen Hypervisor on i386
rc  xen-utils-common                   4.0.0-1                      XEN administrative tools - common files

root@test1:~# dpkg --list |grep xen 
ii  libc6-xen                          2.11.2-10                    Embedded GNU C Library: Shared libraries [Xen version]
ii  libxenstore3.0                     4.0.1-2                      Xenstore communications library for Xen
ii  linux-headers-2.6.32-5-common-xen  2.6.32-31                    Common header files for Linux 2.6.32-5-xen
ii  linux-headers-2.6.32-5-xen-686     2.6.32-31                    Header files for Linux 2.6.32-5-xen-686
ii  xen-hypervisor-4.0-i386            4.0.1-2                      The Xen Hypervisor on i386
ii  xen-utils-4.0                      4.0.1-2                      XEN administrative tools
ii  xen-utils-common                   4.0.0-1                      XEN administrative tools - common files
ii  xenstore-utils                     4.0.1-2                      Xenstore utilities for Xen

ebiantest:/etc/apt# ssh 192.168.3.25 
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
81:17:24:c9:c7:d0:30:c1:33:6b:75:d3:c4:5a:bf:13.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending key in /root/.ssh/known_hosts:4
RSA host key for 192.168.3.25 has changed and you have requested strict checking.
Host key verification failed.
debiantest:/etc/apt# 

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile	%h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

debiantest:/etc# ls -l /dev/disk/by-uuid/
итого 0
lrwxrwxrwx 1 root root 10 Мар 17 13:43 3198e629-ab6a-426a-8980-5bd4f342d4af -> ../../sdb5
lrwxrwxrwx 1 root root 10 Мар 17 13:43 379168A327F2C3EF -> ../../sda1
lrwxrwxrwx 1 root root 10 Мар 17 13:43 92931fd0-92e1-4226-be34-eadd0b13e97f -> ../../sdb1
lrwxrwxrwx 1 root root 10 Мар 17 13:43 f8706fb1-abcf-4af1-97ec-b03cdc90b6ca -> ../../sdb7
lrwxrwxrwx 1 root root 10 Мар 17 13:43 feccd901-3b97-48e8-bf5e-89de7bfdc74c -> ../../sdb6

поставил 
linux-image-2.6.32-5-xen-686
xen-hypervisor-4.0-i386
xen-utils-4.0
плюс подтянулись зависимости 
при загрузке выбираяю ядро с xen

debiantest:~# xm dmesg
WARNING!  Can't find hypervisor information in sysfs!
Error: Unable to connect to xend: No such file or directory. Is xend running?

debiantest:/etc/hal/fdi/policy# du -shc /home/*
56G     /home/andreym
772K    /home/lost+found
332M    /home/test
56G     итого

debiantest:/etc/hal/fdi/policy# du -shc /home/andreym/*
58M     /home/andreym/1
4,0K    /home/andreym/Desktop
8,0K    /home/andreym/Downloads
24K     /home/andreym/drwtoday.txt
48K     /home/andreym/drwtoday.vdb
3,6M    /home/andreym/install
7,7G    /home/andreym/rab
12K     /home/andreym/vboxdrv
7,8G    итого
debiantest:/etc

 
virdebian:/var/log/bind/log# date 
Пнд Фев 28 10:05:05 MSK 2011
делаем рестарт bind9 
virdebian:/var/log/bind/log# service bind9 restart 
проверяем файл логов 
28-Feb-2011 07:04:58.728 general: info: received control channel command 'stop -p'
28-Feb-2011 07:04:58.729 general: info: shutting down: flushing changes
28-Feb-2011 07:04:58.730 general: notice: stopping command channel on 127.0.0.1#953
28-Feb-2011 07:04:58.730 general: notice: stopping command channel on ::1#953
28-Feb-2011 07:04:58.741 network: info: no longer listening on 127.0.0.1#53
28-Feb-2011 07:04:58.741 network: info: no longer listening on 192.168.3.25#53
28-Feb-2011 07:04:58.810 general: notice: exiting
28-Feb-2011 07:05:00.290 general: info: zone 0.in-addr.arpa/IN: loaded serial 1
28-Feb-2011 07:05:00.293 general: info: zone 127.in-addr.arpa/IN: loaded serial 1
28-Feb-2011 07:05:00.297 general: info: zone 3.168.192.in-addr.arpa/IN: loaded serial 1
28-Feb-2011 07:05:00.302 general: info: zone 255.in-addr.arpa/IN: loaded serial 1
28-Feb-2011 07:05:00.312 general: info: zone localhost/IN: loaded serial 2
28-Feb-2011 07:05:00.314 general: info: zone test/IN: loaded serial 1
28-Feb-2011 07:05:00.316 general: error: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
28-Feb-2011 07:05:00.317 general: info: managed-keys-zone ./IN: loaded serial 0
28-Feb-2011 07:05:00.332 general: notice: running

В итоге получается разница между реальным временем в системе и временем в логах в чём касяк ? 

Настройки bind9 

acl "virdebian" { 192.168.3.0/24; 127.0.0.1; };
options {
    directory "/etc/bind";

    pid-file   "/etc/bind/named.pid";
    dump-file  "/var/log/named/cache_dump.db";
    statistics-file  "/var/log/named/named_stats.txt";
    memstatistics-file  "/var/log/named/named_mem_stats.txt";
    
    #от кого разрешаем принимать запросы 
    allow-query { "virdebian"; };
    
    #Разрешаем выполнять рекурсивные запросы только с virdebian
    allow-recursion { "virdebian"; };
    
    #каким днс перенаправляем запрос если у нашего нет данных 1,2 днс провайдера 2 google 
    forwarders { 83.149.24.243;
    83.149.24.244;
    8.8.8.8;
    };

    #скажем на каких портах обслуживать днс запросы
    listen-on port 53 {
    127.0.0.1;
    192.168.3.25;
    };
    #инфа о сервере 
    version "virdebian DNS";
    

    
    auth-nxdomain no;    # conform to RFC1035
    #отключаем ipv 6
    listen-on-v6 { none; };
    };
    #Дополнительный вывод логов в отдельные файлы 
    logging {
    channel warning {
    file "/var/log/dns_warning" versions 3 size 10m;
    severity warning;
    print-category yes;
    print-severity yes;
    print-time yes;
    };
    
    channel general_dns {
    file "/var/log/dns_logs" versions 3 size 10m;
    severity info;
    print-category yes;
    print-severity yes;
    print-time yes;
    };
    category default { warning; };
    category default { general_dns; };

};

acl "virdebian" { 192.168.3.0/24; 127.0.0.1; };
options {
	directory "/etc/bind";

	pid-file   "/etc/bind/named.pid";
	dump-file  "/var/log/named/cache_dump.db";
	statistics-file  "/var/log/named/named_stats.txt";
	memstatistics-file  "/var/log/named/named_mem_stats.txt";
	
	#от кого разрешаем принимать запросы 
	allow-query { "virdebian"; };
	
	#Разрешаем выполнять рекурсивные запросы только с virdebian
	
	
	#каким днс перенаправляем запрос если у нашего нет данных 1,2 днс провайдера 2 google 
	forwarders { 83.149.24.243;
	83.149.24.244;
	8.8.8.8;
	};

	#скажем на каких портах обслуживать днс запросы
	listen-on port 53 {
	127.0.0.1;
	192.168.3.25;
	};
	#инфа о сервере 
	version "virdebian DNS";
	

	
	auth-nxdomain no;    # conform to RFC1035
	#отключаем ipv 6
	listen-on-v6 { none; };
	};
	#######################################ведение лога
	logging {
	channel warning {
	file "/var/log/dns_warning" versions 3 size 10m;
	severity warning;
	print-category yes;
	print-severity yes;
	print-time yes;
	};
	
	channel general_dns {
	file "/var/log/dns_logs" versions 3 size 10m;
	severity info;
	print-category yes;
	print-severity yes;
	print-time yes;
	};
	category default { warning; };
	category default { general_dns; };

};

25-Feb-2011 09:59:28.734 general: info: zone 0.in-addr.arpa/IN: loaded serial 1
25-Feb-2011 09:59:28.774 general: info: zone 127.in-addr.arpa/IN: loaded serial 1
25-Feb-2011 09:59:28.787 general: info: zone 3.168.192.in-addr.arpa/IN: loaded serial 1
25-Feb-2011 09:59:28.800 general: info: zone 255.in-addr.arpa/IN: loaded serial 1
25-Feb-2011 09:59:28.821 general: info: zone localhost/IN: loaded serial 2
25-Feb-2011 09:59:28.830 general: info: zone test/IN: loaded serial 1
25-Feb-2011 09:59:28.830 general: error: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
25-Feb-2011 09:59:28.839 general: info: managed-keys-zone ./IN: loaded serial 0
25-Feb-2011 09:59:28.865 general: notice: running