opensand team mailing list archive
-
opensand team
-
Mailing list archive
-
Message #00109
Cannot initialize OpenSAND interfaces: IPV6 address
-
To:
<opensand@xxxxxxxxxxxxxxxxxxx>
-
From:
<hongfei.du@xxxxxxxxxxxx>
-
Date:
Fri, 19 Jul 2013 14:45:35 +0100
-
Accept-language:
en-US, en-GB
-
Acceptlanguage:
en-US, en-GB
-
Thread-index:
AQHOhIXvw9GhEZ7zkUazqm5AW1SHYg==
-
Thread-topic:
[Opensand] Cannot initialize OpenSAND interfaces: IPV6 address
Hello Everyone,
We are currently in the initial stage of configuring Opensand emulation platform on top of a rack of 6 machines running on Ubuntu 12.04 LTS (64bits), which are expected to form a platform of 1 SAT, 1 GW, 2 STs and 2 WSs, SAT/GW/ST can be detected from the manager on 2 machines, but found the following errors on converting the ipv6 address to GW/ST in the daemon.log on the other 4 machines.
Jul 19 13:02:38 testbed sand-daemon[3158]: address 192.168.18.2/24 already exists on eth0
Jul 19 13:02:38 testbed sand-daemon[3158]: listen on 0.0.0.0:5926
Jul 19 13:02:38 testbed sand-daemon[3158]: address 192.168.20.5/24 already exists on eth1
Jul 19 13:02:38 testbed sand-daemon[3158]: address fe80::21c:23ff:fee2:9b91/64 already exists on eth1
Jul 19 13:02:38 testbed sand-daemon[3158]: cannot initialize OpenSAND interfaces: invalid literal for int() with base 10: '9b91'
Jul 19 13:02:38 testbed sand-daemon[3158]: listen for states on 0.0.0.0:5358
Jul 19 13:02:38 testbed sand-daemon[3158]: Starting the stats handler
Jul 19 13:02:40 testbed sand-daemon[3158]: service thread is not started correctly: quit
GW configuration:
[service]
name = gw
instance = 0
type = _opensand._tcp
interface =
port = 3141
[command]
port = 5926
[state]
port = 5358
[network]
config_level = advanced
emu_iface = eth0
emu_ipv4 = 192.168.18.2/24
lan_iface = eth1
lan_ipv4 = 192.168.20.5/24
lan_ipv6 = fe80::21c:23ff:fee2:9b91/64
Currently only 2 machines can work with each other and found as SAT/GW/ST from the manager, the other 4 machines give the same error right after configuring the daemon, does anyone encountered similar problem? Is it a ipv6 issue or some others relating to string conversion or wrong configuration? I can hardly see there is any problem of converting fe80::21c:23ff:fee2:9b91 to int, All machines are freshly installed with same settings, and connected via a switch.
Any comments would be more than helpful. Thanks!
Best regards,
Hongfei
Follow ups