Got it working, thanks for the help
On Tue, Jun 6, 2017 at 9:26 PM, Gabriel Kerneis
wrote:
> On Tue, Jun 6, 2017, at 20:41, Jehan Tremback wrote:
>
> No, our only way to configure nodes for any given protocol is a shell
> script. I could make it write out a file, but I was trying to keep it
> si
Hi Juliusz,
Thanks for your support.
I'm using the following topology to understand the diversity behaviour,
R1(AP mode) ---> R2( Station mode)
Both R1,R2 having two radio's 2.4 and 5 Ghz.I'm getting following result for
with diversity and without diversity. It seems only change i can s
> R1(AP mode) ---> R2( Station mode)
All of your routes are single-hop, so there's no diversity information
being propagated. You'll need some longer routes in order to see anything..
> The channel information remains as 11 and 36 for station mode but ap
> mode it is 255. Whether it is e
Hi everybody!
I would like to know which is the proper method to get the string
representation of the ipv4 address of an interface.
I would appreciate very much something working like this:
struct interface *ifp=...assume that it really points to some interface...
char addr[16];
get_ifaddress(ifp
> I tried to take advantage from ifp->ipv4 but I am in trouble...
> please, can somebody help me? :)
ifp->ipv4 is either NULL (in which case there is no IPv4 address on this
interface), or a four-octet array of unsigned char which you can pass to
inet_ntop(AF_INET).
-- Juliusz
__
Hi, I was wondering what is the best way to enable the RTT metric with
sensible defaults. It looks like max-rtt-penalty is the option that turns
it on. What is a good value to set this at starting out?
-Jehan
___
Babel-users mailing list
Babel-users@list
6 matches
Mail list logo