I just did a pull of your head, built it, started a new babel...
waited 2 minutes (I was assuming the calculation for the routerid had
changed?)... and did not get a working route to elsewhere until I
tried talking to another route.

(note I did not update the other 2 babelds in operation on this
network from the old openwrt "babels")

I get working routes locally, but the next box upstream refused any connection.

d@ganesha:~/git/babeld$ ip route
default via 172.26.22.224 dev wlan0  proto babel onlink
76.102.227.25 via 172.26.22.224 dev wlan0  proto babel onlink
172.26.0.0/16 dev wlan0  proto kernel  scope link  src 172.26.65.1
172.26.16.0/24 via 172.26.22.224 dev wlan0  proto babel onlink
172.26.16.1 via 172.26.22.224 dev wlan0  proto babel onlink
172.26.17.0/24 via 172.26.18.224 dev wlan0  proto babel onlink
172.26.17.1 via 172.26.22.224 dev wlan0  proto babel onlink
172.26.18.0/24 dev wlan0  proto kernel  scope link  src 172.26.18.225
172.26.19.0/24 via 172.26.22.224 dev wlan0  proto babel onlink
172.26.20.0/24 via 172.26.18.224 dev wlan0  proto babel onlink
172.26.22.224 via 172.26.22.224 dev wlan0  proto babel onlink
172.26.128.0/27 dev eth0  proto kernel  scope link  src 172.26.128.18
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.202
d@ganesha:~/git/babeld$ ssh [email protected]

fails.

Weirdness - after I tried connecting to here

traceroute to 172.26.19.1 (172.26.19.1), 30 hops max, 60 byte packets
 1  172.26.22.224  102.543 ms  102.529 ms  103.409 ms # 100ms????
 2  172.26.19.1  104.586 ms  107.553 ms  107.572 ms

stuff started to work.

I went back to the older version and got the same result for over 2
minutes but it did eventually work. Then I went back to the newer one
waiting over 2 minutes... and that too, eventually did work.

running ubuntu 3.19.0-15-generic, ath9k wifi. Babeld.conf is:

ipv6-subtrees true
out if vpn6 ip 0.0.0.0/0 deny
in if vpn6 ip 0.0.0.0/0 deny

I am going to put this down to a bug not in babel. (100ms to my next hop? wtf?)

And I am getting on a plane transiting paris in the next few minutes.
See you in prague!

~

On Fri, Jul 10, 2015 at 11:53 AM, Juliusz Chroboczek
<[email protected]> wrote:
>> This means that all the interfaces on a node will have a link-local
>> address?  That's a very bad idea.
>
> This was meant to say "the same link-local address".
>
> _______________________________________________
> Babel-users mailing list
> [email protected]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users



-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

_______________________________________________
Babel-users mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Reply via email to