Szokovacs Robert wrote on 08/13/2015 01:59 PM: > On 2015-08-13 13:11, Stefan Sayer wrote: >> Hi Robert, >> >> Szokovacs Robert wrote on 08/12/2015 05:57 PM: >>> Hi, >>> >>> We are running SEMS on a machine that has aliased interfaces (ex.: eth1 >>> and eth1:0), and it stopped working when upgraded to 1.6. I traced the >>> problem to the usage of if_nametoindex() in fillSysIntfList(), which >>> translates all the aliased interfaces to the same index. I'm not sure if >>> it's the specified behaviour of if_nametoindex or it's a bug in libc. >>> I'm not sure if this new indexing of the interfaces used anywhere else, >>> please advise! >>> >> what exactly is failing? I'm using SEMS usually with alias interfaces >> without problems. It's normal and correct that the system interface >> determined in dillSysIntfList is the same one for all aliased interfaces. >> >> Are you e.g. using autodetected interfaces in the sbc? maybe it'll >> work better if you explicitely set the outgoing interface in the profile. >> > > The startup is failing immediately: > > Konsole output > ./sems -E -f ./sems.conf > [#7f0376103740/64913] [init_logging, log.cpp:180] INFO: Logging > initialized > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='lo';ip='127.0.0 > .1';flags=0x10049 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='bond0';ip='10.1 > 20.67.30';flags=0x11443 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='vlan286';ip='10 > .1.170.30';flags=0x11043 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='vlan495';ip='10 > .120.66.30';flags=0x11043 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='vlan287';ip='10 > .1.171.30';flags=0x11043 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='vlan287:0';ip=' > 10.1.171.39';flags=0x11043 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='vlan497';ip='10 > .120.68.30';flags=0x11043 > [#7f0376103740/64913] [fillSysIntfList, AmConfig.cpp:1019] DEBUG: > iface='lo';ip='::1';fl > ags=0x10049 > [#7f0376103740/64913] [finalizeIPConfig, AmConfig.cpp:1139] ERROR: > could not determine s > ignaling IP for interface 'default' > [#7f0376103740/64913] [main, sems.cpp:658] INFO: Disposing plug-ins > [#7f0376103740/64913] [cleanup, SipCtrlInterface.cpp:411] DEBUG: > Stopping SIP control in > terface threads > [#7f0376103740/64913] [main, sems.cpp:678] INFO: Exiting (failure) > > Konsole output I havesip_ip=vlan287 in the config. The vlan287 and > vlan287:0 have different IPs. Actually, we have two instances of sems > running here, one on vlan287, the other is vlan287:0. If i put > sip_ip=vlan287:0 to the config, it will start up apperantly fine, but as per the log, SEMS couldn't figure out the IP address of the interface 'vlan287': ERROR: could not determine signaling IP for interface 'default'
does it work if you put the IP address and not the interface name in the config? i.e. sip_ip=1.2.3.4 ? > will use vlan287's IP, which isn't fine at all. All these are regression > from 1.5.0. it's right that SEMS 1.6 does quite some things more there with the interfaces, because the multiple interfaces support is much different in that version. Stefan _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
