Users have same ip addresses
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Users have same ip addresses

Started by Elix, 09 October, 2008, 19:02:50

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Elix

Strange bug in 0.4.1.1-posix (run on freebsd).

After some days hub start to see many users under same ip, but ips are different!
Restart helps, but every day restarts isn't a good idea...

ATAG

We run 0.4.1.1 on ubuntu and gentoo with several thousand users but I never faced this problem. Can you show some example?

Elix

Today it happened again.
I see many same ips in user list. When i check ips using lua script, i see same addresses too.

Perhaps this is related to option #53 (Check IP in commands). Now i turned it on, perhaps this will help.

Also, how can i view some debug log?

ATAG

Quote from: Elix on 12 October, 2008, 18:35:46
Also, how can i view some debug log?
With the UDP Debug Receiver and the "!debug <udp_port>" command :)

Elix

#4
Nothing... Debug log is empty.
Also this bug goes every two days, and i restart a hub.

Elix

#5
All scripts i wrote myself :)

it appears that the number of users with the same address is no more than setting #112 - Maximum users from same IP.

I don't think that the error was in one script, because all the scripts see user with one address, although it should be another.
And hub sends $UserIP with this ip too.

ATAG

Have you got some compile warnings?

Snooze

This could be done by a simple "firewall" and/or "router" error config, either hardware or software.
I suggest checking both.

/Snooze

Elix

Again :(

In debug:

19:11:06 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:07 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:08 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:09 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:10 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:11 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:12 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:13 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:14 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:15 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:16 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:17 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:18 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
19:11:19 - [ERR] accept() for port 411 has returned an INVALID_SOCKET.
...

?StIfFLEr??

With the UDP Debug Receiver and the "!debug <udp_port>" command

Thanks ATAG
+1

Elix

I started ptokax on another server (freebsd too). 0 users, only me.

I see a lot of messages: "[ERR] accept() for port 411 has returned an INVALID_SOCKET" every one second.
What is it? :)

ATAG

Try higher port number then 1024...

Elix

Quote from: ATAG on 21 November, 2008, 22:19:37
Try higher port number then 1024...

[ERR] accept() for port 4000 has returned an INVALID_SOCKET
[ERR] accept() for port 56734 has returned an INVALID_SOCKET

This is very strange :)

Elix

Also, there are no error messages when hub runs on windows.

bastya_elvtars

I am in no way a programmer but digging through the web I found that invalid_socket should not be returned under Unix. Look at this page.
Everything could have been anything else and it would have just as much meaning.

ATAG

You will get this message on any (but 2) errors in accept(). The "timering" (1 error/sec) is very interesting :)

SMF spam blocked by CleanTalk