How to config the Coherence to work under multiple physical interfaces surrounding?

3 messages Options
Embed this post
Permalink
szhairui

How to config the Coherence to work under multiple physical interfaces surrounding?

Reply Threaded More More options
Print post
Permalink
 Hi everyone!

I met with a problem while using coherence under multiple physical interfaces surrounding.

As we known, we can use "interface = eth0" to specify coherence to use the interface eth0.

But my problem is that I use one wired network interface and one wireless network interface.

How can i get the interface name to configure coherence to use the wifi interface ?

I can find the name "wlan0" on Linux , but I can see nothing about the interface alias such

as "eth0" on win32. Where can i found it?

And one more question, how Coherence determind which interface to use without the config file

or without the interface configuration item under multiple pyhysical interfaces surrounding?

Thanks for your notice. And any response will do me a great favour.

_______________________________________________
coherence-dev mailing list
[hidden email]
http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev
Frank Scholz

Re: How to config the Coherence to work under multiple physical interfaces surrounding?

Reply Threaded More More options
Print post
Permalink
Hi,

> How can i get the interface name to configure coherence to use the wifi
> interface ?
>
> I can find the name "wlan0" on Linux , but I can see nothing about the
> interface alias such
> as "eth0" on win32. Where can i found it?
isn't there an 'ifconfig' command on Windows too? That should display
the available interfaces.

On Windows I recommend to use the netifaces module, the plain python
methods to determine the interface to use don't work that well there.

> And one more question, how Coherence determind which interface to use
> without the config file
> or without the interface configuration item under multiple pyhysical
> interfaces surrounding?

Atm Coherence does only support one active interface - this will change
on the way to 0.7.

We try first to get the hostname and resolving that to an IP address.
If that fails or we get a loopback address back, we switch to plan b.

On Windows we use the first interface we get back from netifaces and
use that IP address. On Linux/BSD/OS-X we try either to parse
'/proc/net/route' or the output of the 'route -a' command to
determine the interface used for the default route, which on
a single homed host is usually the interface to use.

Regards,
Frank

_______________________________________________
coherence-dev mailing list
[hidden email]
http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev
szhairui

Re: How to config the Coherence to work under multiple physical interfaces surrounding?

Reply Threaded More More options
Print post
Permalink


--------------------------------------------------
From: "Frank Scholz" <[hidden email]>
Sent: Tuesday, May 26, 2009 4:42 AM
To: "discussions about development and usage issues of Coherence"
<[hidden email]>
Subject: Re: [coherence-dev] How to config the Coherence to work under
multiple physical interfaces surrounding?

> Hi,
>
>> How can i get the interface name to configure coherence to use the wifi
>> interface ?
>>
>> I can find the name "wlan0" on Linux , but I can see nothing about the
>> interface alias such
>> as "eth0" on win32. Where can i found it?
> isn't there an 'ifconfig' command on Windows too? That should display
> the available interfaces.

The similar command on win32 is ipconfig, but it doesn't show any network
interface alias.

>
> On Windows I recommend to use the netifaces module, the plain python
> methods to determine the interface to use don't work that well there.
>
>> And one more question, how Coherence determind which interface to use
>> without the config file
>> or without the interface configuration item under multiple pyhysical
>> interfaces surrounding?
>
> Atm Coherence does only support one active interface - this will change
> on the way to 0.7.

That's really a good news for us who want a more powerful MediaServer
Framework.

>
> We try first to get the hostname and resolving that to an IP address.
> If that fails or we get a loopback address back, we switch to plan b.
>
> On Windows we use the first interface we get back from netifaces and
> use that IP address. On Linux/BSD/OS-X we try either to parse
> '/proc/net/route' or the output of the 'route -a' command to
> determine the interface used for the default route, which on
> a single homed host is usually the interface to use.

BTW, can someone suggest any primer studying materials for a newbie of UPnP
just like me?

>
> Regards,
> Frank
>
> _______________________________________________
> coherence-dev mailing list
> [hidden email]
> http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev
>
_______________________________________________
coherence-dev mailing list
[hidden email]
http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev