Anope IRC Services

Anope Support => 2.0.x/1.9.x Support => Topic started by: Uli on March 22, 2014, 03:57:41 PM

Title: 2.0Rc4 (win) : uplink error in log
Post by: Uli on March 22, 2014, 03:57:41 PM
Hi,
Trying to make RC4 run on latests Unreal3.2 on windows.
Error log :

Attempting to connect to uplink #1 127.0.0.01:7000
Successfully connected to uplink #1 127.0.0.1:7000
Unable to connect to any uplink

????
So which is it ? Successfully unable ? :)
Title: Re: 2.0Rc4 (win) : uplink error in log
Post by: katsklaw on March 22, 2014, 05:20:41 PM
What does the actual log file say?
Title: Re: 2.0Rc4 (win) : uplink error in log
Post by: wilco on March 23, 2014, 12:47:24 AM
Attempting to connect to uplink #1 127.0.0.01:7000

127.0.0.01 does not excist it should be 127.0.0.1
Title: Re: 2.0Rc4 (win) : uplink error in log
Post by: katsklaw on March 23, 2014, 02:00:11 AM
Attempting to connect to uplink #1 127.0.0.01:7000

127.0.0.01 does not excist it should be 127.0.0.1

That really shouldn't matter since it converts the exact same binary address. The 0 is simple short for 000 so 127.000.000.001 is the same as 127.0.0.1. IPv6 truncates too.

Code: [Select]
scott@atlantis:~$ ping 127.000.000.001
PING 127.000.000.001 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.042 ms
64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.030 ms
64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.031 ms
^C
--- 127.000.000.001 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.030/0.034/0.042/0.007 ms
scott@atlantis:~$

Notice how ping truncates the long address? Then it replies.