After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 397768 - Network interfaces list not updated
Network interfaces list not updated
Status: RESOLVED DUPLICATE of bug 324564
Product: ekiga
Classification: Applications
Component: general
GIT master
Other All
: Normal minor
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on: 335088
Blocks:
 
 
Reported: 2007-01-17 21:03 UTC by Jan Kratochvil
Modified: 2007-03-29 16:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Jan Kratochvil 2007-01-17 21:03:28 UTC
Please describe the problem:
My systems starts with Ekiga but it is offline that time.
That time it has only eth0 (intranet, unused).
I start ppp0 (ADSL, ueagle-atm) by hand.
Ekiga does not detect the new interface, it still has in its Preferences->Network Settings->Network Interfaces->Listen on only the "eth0" interface.
One has to restart Ekiga and switch it by hand back to "ppp0" to get it functioning correctly.


Steps to reproduce:
1. killall br2684ctl;rmmod br2684 # kill ADSL (ppp0)
2. ekiga &
3. adsl # start ADSL (ppp0)


Actual results:
Ekiga has only "eth0" interface listed. It does not function properly.

Expected results:
Does it need the specific interface at all? Why not to listen on all the available ones? And periodically recheck their current list (as named(8) does).
Also not sure why you need to bind to the specific interfaces, isn't the default INADDR_ANY access enough?

Not sure of the right way. It should at least remember it was last set to "ppp0" and use the last manually set interface if it gets up again.
It should also periodically check the list of system interfaces.


Does this happen every time?
Yes.

Other information:
Comment 1 Jan Kratochvil 2007-01-17 21:23:18 UTC
In some way it may be considered as a duplicated of Bug 335088 but not completely.
Comment 2 Snark 2007-03-29 16:37:12 UTC
In fact, we indeed already have some bug reports about ekiga not being able to cope well with multiple and/or dynamic network interfaces. I'm trying to melt them into one.

*** This bug has been marked as a duplicate of 324564 ***