Skip to main content

Example script for mobile HSDPA with "wvdialconf"

This is an example for mobile HSDPA modem which use USB connection.
In this configuration, i use IndosatM2 as internet provider. And it used as a APN name. And will dial to *99# according to indosatm2 configuration.

####################################
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Ask Password = 1
Phone = *99#
APN = indosatm2
Idle Seconds = 300
Modem Type = Analog Modem
Stupid Mode = 1
Compuserve = 0
Baud = 9600
Auto DNS = 1
Dial Command = ATDT
modem = /dev/ttyUSB0
ISDN = 0
Username = type your username here
#####################################

And you'll prompt to insert a password with no shown you for what character you input.

Comments

Post a Comment

Popular posts from this blog

Improving (network) I/O performance

Introduction The reason for the current work is to analyze different methods for efficent delivery of network events from kernel mode to user mode. Five methods are examined, poll() that has been chosen as the better old-style method, standard /dev/poll interface, standard RT signals, RT signals with one-sig-per-fd patch and a new /dev/epoll that uses a quite different notification method. This work is composed by : 1) the new /dev/epoll kernel patch 2) the /dev/poll patch from Provos-Lever modified to work with 2.4.6 3) the HTTP server 4) the deadconn(tm) tool to create "dead" connections As a measurement tool httperf has been chosen coz, even if not perfect, it offers a quite sufficent number of loading options. The new /dev/epoll kernel patch The patch is quite simple and it adds notification callbacks to the 'struct file' data structure : ******* include/linux/fs.h struct file { ... /* file callback list */ rwlock_t f_cblo...
1 comment
Read more

HOWTO: Securing A Website With Client SSL Certificates

Let's assume that you have an Apache webserver and a website that you want VERY finite access controls on. You could do it a number of ways, right? You could craft a clever login page and use cookies, session IDs, etc. You could use a simple authentication method like .htaccess. Or, you could create a custom SSL certificate and give that certificate to very specific users that should have access to your site. In a perfect world, only these users could communicate with your site AND the connection would be secured via the magic of SSL. I know what you're thinking. "But Chief, what if someone STEALS your certificate?" Hey, what if someone steals your car keys? :-) I have always wanted a good how-to document on doing this, and reader 'Null' (who I must also point out is a heck of a nice guy, and a fun sort to hang out at Def Con with) came through big time. Without further ado, here is Null's write-up on the subject. Enjoy! ~ Chief Reader 'Null' write...
Post a Comment
Read more