uhub Direct Connect 서버를 설치하고 구성했습니다.
프로그램을 실행하면 "uhub가 시작하고 1511 .....
그러나 DC ++ 클라이언트를 사용하여 위의 허브에 연결하면 클라이언트가 잘못된 CID 오류를 발생시키고 uhub 로그를 확인할 때 "USER : login error. msg_inf_cid_invalid"라고 기록됩니다.
아래는 users.conf 파일입니다
# uHub access control lists.
#
# Syntax: <command> [data]
#
# commands:
# 'user_reg' - registered user with no particular privileges (data=nick:password)
# 'user_op' - operator, can kick or ban people (data=nick:password)
# 'user_admin' - administrator, can do everything operators can, and reconfigure the hub (data=nick:password)
# 'deny_nick' - nick name that is not accepted (example; Administrator)
# 'deny_ip' - Unacceptable IP (masks can be specified as CIDR: 0.0.0.0/32 will block all IPv4)
# 'ban_nick' - banned user by nick
# 'ban_cid' - banned user by cid
# Administrator
# user_admin userA:password1
# user_op userB:password2
# We don't want users with these names
deny_nick Hub-Security
deny_nick Administrator
deny_nick root
deny_nick admin
deny_nick username
deny_nick user
deny_nick guest
deny_nick operator
# Banned users
# ban_nick H4X0R
# ban_cid FOIL5EK2UDZYAXT7UIUFEKL4SEBEAJE3INJDKAY
# ban by ip
#
# to ban by CIDR
# deny_ip 10.21.44.0/24
#
# to ban by IP-range.
# deny_ip 10.21.44.7-10.21.44.9
#
# to ban a single IP address
# deny_ip 10.21.44.7
# (which is equivalent to using):
# deny_ip 10.21.44.7/32
# Will not work, yet
# nat_ip 10.0.0.0/8
# nat_ip 127.0.0.0/8
# If you have made changes to this file, you must send a HANGUP signal
# to uHub so that it will re-read the configuration files.
# For example by invoking: 'killall -HUP uhub'
그리고 내 uhub.conf 파일
# uhub.conf - A example configuration file.
# You should normally place this file in /etc/uhub/uhub.conf
# And change the file_acl and file_motd below.
#
# This file is read only to the uhub deamon, and if you
# make changes to it while uhub is running you can send a
# HUP signal to it, to reparse configuration (only on UNIX).
# Bind to this port and address
# server_bind_addr=any means listen to "::" if IPv6 is supported
# by the host OS, otherwise 0.0.0.0.
server_port=1511
server_bind_addr=any
# The maximum amount of users allowed on the hub.
max_users=500
# If 1, will show a "This hub is running uhub/version".
show_banner=1
# Allow only registered users on the hub if set to 1.
registered_users_only=0
# A server name and description.
hub_name=uHub
hub_description=Powered by uHub
# Set this to 0, and the hub will disconnect everyone
hub_enabled=1
# Access control list (user database)
file_acl=/etc/uhub/users.conf
# This file can contain a message of the day. A welcome
# message send to any client when connecting.
# If the file does not exist, is empty, or cannot be opened
# the motd will not be sent to the clients.
# Normally this message is sent to clients when connecting.
file_motd=/etc/uhub/motd.txt
# Configure status message as sent to clients in different circumstances.
msg_hub_full = Hub is full
msg_hub_disabled = Hub is disabled
msg_hub_registered_users_only = Hub is for registered users only
msg_inf_error_nick_missing = No nickname given
msg_inf_error_nick_multiple = Multiple nicknames given
msg_inf_error_nick_invalid = Nickname is invalid
msg_inf_error_nick_long = Nickname too long
msg_inf_error_nick_short = Nickname too short
msg_inf_error_nick_spaces = Nickname cannot start with spaces
msg_inf_error_nick_bad_chars = Nickname contains invalid characters
msg_inf_error_nick_not_utf8 = Nickname is not valid utf8
msg_inf_error_nick_taken = Nickname is already in use
msg_inf_error_nick_restricted = Nickname cannot be used on this hub
msg_inf_error_cid_invalid = CID is not valid
msg_inf_error_cid_missing = CID is not specified
msg_inf_error_cid_taken = CID is taken
msg_inf_error_pid_missing = PID is not specified
msg_inf_error_pid_invalid = PID is invalid
msg_ban_permanently = Banned permanently
msg_ban_temporarily = Banned temporarily
msg_auth_invalid_password = Password is wrong
msg_auth_user_not_found = User not found in password database
msg_error_no_memory = No memory
모든 설정으로 땜질을 시도했지만 여전히 문제를 파악할 수 없습니다.
서버의 오류 메시지를 어디로 보냅니 까? 서버 쪽에서 이를 확인해야 하며 이는 클라이언트 쪽 보다 훨씬 유익합니다 .
—
MariusMatutiae 2016 년
태그 재 지정-리눅스도 아니고 네트워킹 문제도 아니고 순수한 DC ++
—
Lazy Badger
@MariusMatutiae conf가 서버 측에서 왔으며 서버 측 설정을 확인했지만 해결책을 찾을 수 없었습니다 .uHub는 위의 두 개의 conf 파일 만 사용하며 둘 다 CID 구성에 대한 특정 설정이 없습니다.
—
Antony
클라이언트에서 uhub에 연결을 시도 할 수 있습니까?
—
Lazy Badger
@Lazy Badger 죄송합니다. ISP에서 퍼블릭 IP를 할당하지 않았습니다. 내 LAN에있는 사람들 만 내 허브에 액세스 할 수 있습니다.
—
Antony