dbeacon sending reports out of eth0 instead of sixxs tunnel
Shadow Hawkins on Friday, 20 March 2009 19:16:01
Hi,
I'm trying to set up IPv6 multicast on my LAN router. This is a standard x86 box running Ubuntu Server 8.10, the Shorewall firewall, Aiccu, and Radvd.
First off, my normal IPv6 connection (subnet R4956 via tunnel T11589 to iedub01) is working fine -- I can connect to IPv6 sites, ping, see the dancing kame, and so forth.
I've installed ecmh and dbeacon, but dbeacon is listing my server under "Beacons with no connectivity" on the matrix. I've done some tracing with tcpdump, and found that the dbeacon reports are being sent out of 'eth0'. For instance, calling dbeacon like this:
philpem@wolf:~$ dbeacon -c /etc/dbeacon/dbeacon.conf -v
Sending Report to ff1e::1:f00d:beac/10000
Mar 20 18:07:48.348332 Local name is `philpem` [Beacon group: ff1e::1:f00d:beac/10000, Local address: 2001:770:170:1::1]
Sending Report to ff1e::1:f00d:beac/10000
Sending Report to ff1e::1:f00d:beac/10000
(...snip...)
gets me this tcpdump output on eth0:
philpem@wolf:/var/www/dbeacon$ sudo tcpdump -i eth0 port 10000
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
18:09:51.197060 IP6 2001:770:170:1::1.49324 > ff1e::1:f00d:beac.10000: UDP, length 106
18:09:51.289530 IP6 2001:770:170:1::1.49324 > ff1e::1:f00d:beac.10000: UDP, length 12
18:09:51.389500 IP6 2001:770:170:1::1.49324 > ff1e::1:f00d:beac.10000: UDP, length 12
(...snip...)
Marc Manthey's post in https://www.sixxs.net/forum/?msg=setup-691237 on on Sunday, 23 March 2008 21:48:39 suggests that if the report packets aren't being sent to the PoP, then multicast won't work.
I've tried adding an IP route to force the packets to be sent out through the 'sixxs' interface:
$ sudo ip -6 route add ff1e::1:f00d:beac dev sixxs metric 1
but this had no effect -- the packets are still being sent out of eth0.
This is my dbeacon.conf file:
name: philpem
contact: XXXX@XXXXXXX.XX.uk
addr: ff1e::1:f00d:beac
website: http://www.philpem.me.uk
matrix: http://wolf.philpem.me.uk/dbeacon/
CC: GB
ssmping: false
interface: sixxs
dump: /var/www/dbeacon/dump.xml
interval: 30
(which is a modified version of the example on the SixXS website -- note that the email address is valid in the config file, but I've blanked it in this forum post)
Can someone please tell me what I'm doing wrong here? Why are the multicast reports going out of eth0 instead of sixxs, even though I have a route that should be forcing them to be sent down the tunnel?
Thanks,
Phil.
dbeacon sending reports out of eth0 instead of sixxs tunnel
Shadow Hawkins on Tuesday, 09 June 2009 20:16:55
Hi Phil,
I think I'm experiencing similar things here on my server as well. I tried to set up multicast support here at home for the first time, but does not really work, indeed :).
I tried "ping6 ff7e:440:2001:630:d0:f001:9000:1215" from my laptop which is connected to my server (on eth1, running radvd, ecmh, sixxs/pop-tunnel) and wireshark showed me on my server, that it forwards the traffic to eth0 (instead of sixxs). I tried enabling mc_forwarding under /proc/sys/net/ipv6/conf/sixxs/ and /proc/sys/net/ipv6/conf/eth1, but this had no effect.
I'm not quite sure yet, but maybe the forwarding is working fine on my laptop... could it be a kernel-issue? I'm running 2.6.26-2 on my server and 2.6.29-2 on my laptop.
Cheers, Linus
dbeacon sending reports out of eth0 instead of sixxs tunnel
Shadow Hawkins on Wednesday, 23 December 2009 14:06:24
I got the same interface problem.
I am not even able, to enable mc_routing on Linux 2.6.31 and 2.6.30.
# echo -e 1 >/proc/sys/net/ipv6/conf/all/mc_forwarding
-bash: /proc/sys/net/ipv6/conf/all/mc_forwarding: Permission denied
Posting is only allowed when you are logged in. |