谁用的xsupplicant上网?能不能把你们的配置文件给贴出来?我xsupplicant的配置文件见内

仅供存放个人的配置文件,不要在本版发问。
回复
rucstudent
帖子: 633
注册时间: 2007-05-09 16:52

谁用的xsupplicant上网?能不能把你们的配置文件给贴出来?我xsupplicant的配置文件见内

#1

帖子 rucstudent » 2007-06-06 21:24

谁用的xsupplicant上网?能不能把你们的配置文件给贴出来?我xsupplicant的配置文件见内


我配置了半天也配置不了...
运行日志里面的内容是:
Interface initalized!
No configuration information for network "(null)" found. Using default.
An error occured binding to socket. (Error : Address already in use)
There was no active method in eap_cleanup()!
AAAH! Trying to delete an undefined config type.
Notify developers. Type: 0x12


ps:我们学校用的是港湾网络认证,dhcp自动分配地址,可是我是手工指定的IP(之前用的是mystar认证,必须手工指定IP才能上)
IP:10.64.9.15
子望眼马:255.255.255.0
网关:10.64.9.1
DNS:202.112.112.200/202.112.112.100

运行xsupplicant后终端提示:[我把帐号和密码全部用汉字写出来了]
root@lanpeng-ubuntu:/# xsupplicant -i eth0
Using default config!
network_list: all
Default network: "default"
Startup command: "echo "some command""
First_Auth command: "dhclient %i"
Reauth command: "echo "authenticated user %i""
Logfile: "/var/log/xsupplicant.log"
Allow Types: ALL
Dest Mac: FF:FF:FF:FF:FF:FF
ID: "我的用户名"
tls user cert: "/path/to/certificate"
tls user key: "/path/to/private/key"
tls user pass: "password for key"
tls root_cert: "/path/to/root/cert"
tls root_dir: "/path/to/valid/root/certs"
tls chunk: 1398
tls rand: "/path/to/random/source"
md5 username: "我的用户名"
md5 password: "我的密码"
ttls root_cert: "/path/to/root/certificate"
ttls chunk: 1398
ttls rand: "/path/to/random/source"
ttls phase2_type 'pap'
pap username: "papuser"
pap password: "pappasswd"
chap username: "chapuser"
chap password: "chappasswd"
mschap username: "mschapuser"
mschap password: "mschappasswd"
mschapv2 username: "mschapv2user"
mschapv2 password: "mschapv2passwd"
leap username: "leapuser"
leap password: "leapuserpass!"
mschapv2 username: "eapmschapv2user"
mschapv2 password: "eapmschapv2userpass!"
peap user cert: "/path/to/certificate"
peap root_dir: "/path/to/root/certificate/dir"
peap crl_dir: "/path/to/dir/with/crl"
peap user key: "/path/to/private/key"
peap user pass: "password for key"
peap chunk: 1398
peap rand: "/path/to/random/source"
peap CN check : "myradius.radius.com"
match CN exactly : "yes"
Session Resumption = YES
PEAP Allow Types: ALL
mschapv2 username: "phase2mschapv2"
mschapv2 password: "phase2mschapv2pass"
sim username: "simuser"
sim password: "simuserpass!"
sim auto_realm: "yes"
Type: Wired
SSID: "mvemjsnp"
Allow Types: ALL
ID: "Check this out- any char!#$"
SSID: "up to 32 character ASCII string"
ID: "testuser@testnet.com"
Allow Type: TLS
Type: Wireless
SSID: "foo-network!"
Type: Wired
ID: "this will work too"
Couldn't initalize daemon socket!




我的配置文件是:


# This is an example configuration file for xsupplicant versions after 0.8b.

### GLOBAL SECTION

# network_list: defines all of the networks in this file which
# should be kept in memory and used.Comma delimited list or "all"
# for keeping all defined configurations in memory. For efficiency,
# keep only the networks you might roam to in memory.
# To avoid errors, make sure your default network is always
# in the network_list. In general, you will want to leave this set to
# "all".

network_list = all
#network_list = default, test1, test2

# default_netname: some users may actually have a network named "default".
# since "default" is a keyword in the network section below, you can
# change which is to be used as the replacement for this keyword

default_netname = default
#default_netname = my_defaults

# In the startup_command, first_auth_command, and reauth_command you can
# use "%i" to have xsupplicant fill in the interface that is being used.
# This allows a single network profile to work across different wireless
# cards.

# startup_command: the command to run when xsupplicant is first started.
# this command can do things such as configure the card to associate with
# the network properly.
startup_command = <BEGIN_COMMAND>echo "some command"<END_COMMAND>

# first_auth_command: the command to run when xsupplicant authenticates to
# a wireless network for the first time. This will usually be used to
# start a DHCP client process.
first_auth_command = <BEGIN_COMMAND>dhclient %i<END_COMMAND>

# reauth_command: the command to run when xsupplicant reauthenticates to a
# wireless network. This may be used to have the dhcp client rerequest
# it's IP address.
reauth_command = <BEGIN_COMMAND>echo "authenticated user %i"<END_COMMAND>

# When running in daemon, or non-foreground mode, you may want to have the
# output of the program. So, define a log file here. Each time XSupplicant
# is started, this file will be replaced. So, there is no need to roll the
# log file.
logfile = /var/log/xsupplicant.log

# The auth_period, held_period, and max_starts modify the timers in the state
# machine. (Please reference the 802.1x spec for info on how they are used.)
# For most people, there is no reason to define these values, as the defaults
# should work.

#auth_period = 30

#held_period = 30

#max_starts = 3

# Defining an interface in "allow_interfaces" will bypass the rules that
# xsupplicant uses to determine if an interface is valid. For most people
# this setting shouldn't be needed. It is useful for having xsupplicant
# attempt to authenticate on interfaces that don't appear to be true
# physical interfaces. (i.e. Virtual interfaces such as eth0:1)

#allow_interfaces = eth0, wlan0

# Defining an interface in "deny_interfaces" will prevent xsupplicant from
# attempting to authenticate on a given interface. This is useful if you
# know that you will never do 802.1x on a specific interface. However,
# allows will take priority over denies, so defining the same interface in
# the allow_interfaces, and deny_interfaces will result in the interface
# being used.

#deny_interfaces = eth1

### NETWORK SECTION



# The general format of the network section is a network name followed
# by a group of variables.

# Network names may contain the following characters: a-z, A-Z, 0-9, '-',
# '_', '\', '/'
# Those interested in having an SSID with ANY character in it can use
# the ssid tag within the network clause. Otherwise, your ssid will
# be the name of the network.

## The default network is not a network itself. These values are
## the default used for any network parameters not overridden
## in another section. If it's not in your network configuration
## and not in your default, it won't work!!

default
{
# type: the type of this network. wired or wireless, if this value is not
# set, xsupplicant will attempt to determine if the interface is wired or
# wireless. In general, you should only need to define this when
# xsupplicant incorrectly identifies your network interface.
#type = wireless

# wireless_control: If this profile is forced to wired, this will not do
# anything. However, if the interface is forced, or detected to be wireless
# XSupplicant will take control of re/setting WEP keys when the machine
# first starts, and when it jumps to a different AP. In general, you won't
# need to define, or set this value.
# wireless_control = yes

# allow_types: describes which EAP types this network will allow. The
# first type listed will be requested if the server tries to use something
# not in this list.
# allow_types = eap_tls, eap_md5, eap_gtc, eap-otp
allow_types = all

# identity: what to respond with when presented with an EAP Id Request
# Typically, this is the username for this network. Since this can
# be an arbitrary string, enclose within <BEGIN_ID> and <END_ID>
identity = <BEGIN_ID>我的用户名<END_ID>

# Force xsupplicant to send it's packets to this destination MAC address.
# In most cases, this isn't needed, and shouldn't be defined.
#dest_mac = 00:aA:bB:cC:dD:eE

## method-specific parameters are kept in the method
eap_tls {
user_cert = /path/to/certificate
user_key = /path/to/private/key
user_key_pass = <BEGIN_PASS>password for key<END_PASS>
root_cert = /path/to/root/cert
root_dir = /path/to/valid/root/certs
#crl_dir = /path/to/dir/with/crl
chunk_size = 1398
random_file = /path/to/random/source

# To enable TLS session resumption, you need to set the following
# value to "yes". By default, session resumption is disabled.
#session_resume = yes
}

eap-md5 {
username = <BEGIN_UNAME>我的用户名<END_UNAME>
password = <BEGIN_PASS>我的密码<END_PASS>
}

eap-ttls {
#user_cert = /path/to/certificate
#as in tls, define either a root certificate or a directory
# containing root certificates
root_cert = /path/to/root/certificate
#root_dir = /path/to/root/certificate/dir
#crl_dir = /path/to/dir/with/crl
#user_key = /path/to/private/key
#user_key_pass = <BEGIN_PASS>password for key<END_PASS>
chunk_size = 1398
random_file = /path/to/random/source
#cncheck = myradius.radius.com # Verify the server certificate
# has this value in it's CN field.
#cnexact = yes # Should it be an exact match?
#session_resume = yes
# phase2_type defines which phase2 to actually DO. You
# MUST define one of these.
phase2_type = pap
## These are definitions for the different methods you might
## do at phase2. only the one specified above will be used
## but it is valid to leave more than one here for convenience
## and easy switching.
pap {
username = <BEGIN_UNAME>papuser<END_UNAME>
password = <BEGIN_PASS>pappasswd<END_PASS>
}
chap {
username = <BEGIN_UNAME>chapuser<END_UNAME>
password = <BEGIN_PASS>chappasswd<END_PASS>
}
mschap {
username = <BEGIN_UNAME>mschapuser<END_UNAME>
password = <BEGIN_PASS>mschappasswd<END_PASS>
}
mschapv2 {
username = <BEGIN_UNAME>mschapv2user<END_UNAME>
password = <BEGIN_PASS>mschapv2passwd<END_PASS>
}
}

eap-leap {
username = <BEGIN_UNAME>leapuser<END_UNAME>
password = <BEGIN_PASS>leapuserpass!<END_PASS>
}

eap-mschapv2 {
username = <BEGIN_UNAME>eapmschapv2user<END_UNAME>
password = <BEGIN_PASS>eapmschapv2userpass!<END_PASS>
}

eap-peap {
user_cert = /path/to/certificate
# As in tls, define either a root certificate or a directory
# containing root certificates.
#root_cert = /path/to/root/certificate
root_dir = /path/to/root/certificate/dir
crl_dir = /path/to/dir/with/crl
user_key = /path/to/private/key
user_key_pass = <BEGIN_PASS>password for key<END_PASS>
chunk_size = 1398
random_file = /path/to/random/source
cncheck = myradius.radius.com # Verify the server certificate
# has this value in it's CN field.
cnexact = yes # Should it be an exact match?
session_resume = yes

#Currently 'all' is just mschapv2
#If no allow_types is defined, all is assumed
allow_types = all # where all = MSCHAPv2, MD5, OTP, GTC, SIM
#allow_types = eap_mschapv2

# right now you can do any of these methods in PEAP:
eap-mschapv2 {
username = <BEGIN_UNAME>phase2mschapv2<END_UNAME>
password = <BEGIN_PASS>phase2mschapv2pass<END_PASS>
}
}

eap-sim {

# In order to obtain the IMSI from the SIM card, the password
# *MUST* be defined here! Otherwise, you need to specify your
# IMSI as the username below.
username = <BEGIN_UNAME>simuser<END_UNAME>
password = <BEGIN_PASS>simuserpass!<END_PASS>
auto_realm = yes
}
}

# In this network definition, "test1" is the friendly name. It can match
# the essid of the network, which means you won't have to set the "ssid"
# variable. However, if it doesn't match, you need to set the "ssid"
# variable in order for the network to be detected correctly.
test1
{
type = wired
# ssid: you should not define this unless you have characters
# other than those specified above in the ssid of your network
ssid = <BEGIN_SSID>mvemjsnp<END_SSID>

allow_types = all
identity = <BEGIN_ID>Check this out- any char!#$<END_ID>

}


test2
{
# ssid: you should not define this unless you have characters
# other than those specified above in the ssid of your network
ssid = <BEGIN_SSID>up to 32 character ASCII string<END_SSID>
identity = <BEGIN_ID>testuser@testnet.com<END_ID>

allow_types = eap-tls
type = wireless
}

test3
{
# ssid: you should not define this unless you have characters
# other than those specified above in the ssid of your network
ssid = <BEGIN_SSID>foo-network!<END_SSID>

type = wired

identity= <BEGIN_ID>this will work too<END_ID>
}
icokeljh
帖子: 108
注册时间: 2006-12-22 20:40
联系:

#2

帖子 icokeljh » 2007-06-07 16:02

xsupplicant整个软件包吗?我想下载!!请楼主发个网址!!!
rucstudent
帖子: 633
注册时间: 2007-05-09 16:52

#3

帖子 rucstudent » 2007-06-07 22:28

icokeljh 写了:xsupplicant整个软件包吗?我想下载!!请楼主发个网址!!!
我是google的...
你会配置么?
蛋壳羊
帖子: 113
注册时间: 2006-11-04 19:56

#4

帖子 蛋壳羊 » 2007-06-14 16:07

我们学校也是万恶的港湾
希望能有达人帮忙出来配置下
BillyChow
帖子: 42
注册时间: 2007-06-12 17:49

#5

帖子 BillyChow » 2007-06-24 15:14

根本就是子虚乌有吧...
我试过了N个版本的XSupplicant 配置了N次都连不上...
现在用MYSTAR解决了
回复