aftr hassles

Dave Taht dave.taht at gmail.com
Sat Mar 24 05:04:53 UTC 2012


I just spent the last 6 hours debugging an aftr problem, that I
thought was a sd-cpe problem with my new images.

If you run aftr in the foreground it will generate output like this:

root at io:~/isc/rt28354# ./aftr -g
tunnel add 2001:db8:0:1::2
tunnel add 2001:db8:0:1::3
tunnel add 2001:db8:0:1::4
+ awk {print $2}
+ awk -F/ {print $1}
+ ip addr show dev eth0
+ grep -w inet
+ PUBLIC=149.20.63.20
+ aftr_start
+ sysctl -w net.ipv4.ip_forward=1
net.ipv4.ip_forward = 1
+ sysctl -w net.ipv6.conf.all.forwarding=1
net.ipv6.conf.all.forwarding = 1
+ sysctl -w net.ipv4.conf.all.rp_filter=0
net.ipv4.conf.all.rp_filter = 0
+ ip link set tun0 up
+ ip addr add 192.0.0.1 peer 192.0.0.2 dev tun0
+ ip route add 149.20.74.65/32 dev tun0
+ ip -6 route add 2001:db8::/64 dev tun0
+ exit 0
no dynamic mapping will be created until the PCP daemon enables this
multicast(filterin)
multicast(filterin)
multicast(filterin)
....


BUT, if you try to toss it into the background (or worse, disconnect
yourself from the session),
the following happens:

^Z
[1]+  Stopped                 ./aftr -g
root at io:~/isc/rt28354# bg
[1]+ ./aftr -g &
root at io:~/isc/rt28354#
closed(ioctl)?
root at io:~/isc/rt28354#
[1]+  Exit 255                ./aftr -g

Similarly, stuff like this will silently exit:

nohup ./aftr -g 2> /dev/null > /dev/null

and stuff like this
./aftr -g &

will end up blocking on output.

In all cases the tunnel(s) stop working.

because of this I did not get to work on the icmp problem or the sdctl
remap problem.


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net


More information about the sdcpe-devel mailing list