[gelöst] Forum ist aus FF Wuppertal nicht erreichbar

wupper1 (hier klappt die direkte Verbindung zum Forum):

net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.bat-wup.arp_filter = 0
net.ipv4.conf.bat-wup.rp_filter = 0
net.ipv4.conf.bat-rdv.arp_filter = 0
net.ipv4.conf.bat-rdv.rp_filter = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.eth0.arp_filter = 0
net.ipv4.conf.eth0.rp_filter = 1
net.ipv4.conf.fastd-wup.arp_filter = 0
net.ipv4.conf.fastd-wup.rp_filter = 0
net.ipv4.conf.fastd-rdv.arp_filter = 0
net.ipv4.conf.fastd-rdv.rp_filter = 0
net.ipv4.conf.gre0.arp_filter = 0
net.ipv4.conf.gre0.rp_filter = 1
net.ipv4.conf.gretap0.arp_filter = 0
net.ipv4.conf.gretap0.rp_filter = 1
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.tun-ffw-ber.arp_filter = 0
net.ipv4.conf.tun-ffw-ber.rp_filter = 1
net.ipv4.conf.tun-ffw-fra.arp_filter = 0
net.ipv4.conf.tun-ffw-fra.rp_filter = 1

wupper0 (darüber ist w7 über ipip angebunden):

9: tun-ffw-w07@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1400 qdisc noqueue state UNKNOWN group default 
    link/ipip <w0> peer <w7>
    inet 185.66.194.16/31 scope global tun-ffw-w07
       valid_lft forever preferred_lft forever

net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.eth0.arp_filter = 0
net.ipv4.conf.eth0.rp_filter = 1
net.ipv4.conf.gre0.arp_filter = 0
net.ipv4.conf.gre0.rp_filter = 1
net.ipv4.conf.gretap0.arp_filter = 0
net.ipv4.conf.gretap0.rp_filter = 1
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.tun-ffw-ber.arp_filter = 0
net.ipv4.conf.tun-ffw-ber.rp_filter = 1
net.ipv4.conf.tun-ffw-fra.arp_filter = 0
net.ipv4.conf.tun-ffw-fra.rp_filter = 1
net.ipv4.conf.tun-ffw-w07.arp_filter = 0
net.ipv4.conf.tun-ffw-w07.rp_filter = 0
net.ipv4.conf.tunl0.arp_filter = 0
net.ipv4.conf.tunl0.rp_filter = 1

wupper7:

7: tun-ffw-w00@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1400 qdisc noqueue state UNKNOWN 
    link/ipip <w7> peer <w0>
    inet 185.66.194.17/31 scope global tun-ffw-w00
       valid_lft forever preferred_lft forever

net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.bat-wup.arp_filter = 0
net.ipv4.conf.bat-wup.rp_filter = 0
net.ipv4.conf.bat-rdv.arp_filter = 0
net.ipv4.conf.bat-rdv.rp_filter = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.eth0.arp_filter = 0
net.ipv4.conf.eth0.rp_filter = 1
net.ipv4.conf.fastd-wup.arp_filter = 0
net.ipv4.conf.fastd-wup.rp_filter = 1
net.ipv4.conf.fastd-rdv.arp_filter = 0
net.ipv4.conf.fastd-rdv.rp_filter = 1
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.rp_filter = 1
net.ipv4.conf.sit0.arp_filter = 0
net.ipv4.conf.sit0.rp_filter = 0
net.ipv4.conf.tun-ffw-w00.arp_filter = 0
net.ipv4.conf.tun-ffw-w00.rp_filter = 0
net.ipv4.conf.tunl0.arp_filter = 0
net.ipv4.conf.tunl0.rp_filter = 1

dies wurde der bird.conf auf wupper0 bearbeitet bzw. hinzugefügt

filter hostroute {
	if net ~ 185.66.194.16/31 then accept;
	reject;
};

protocol static {
	route 185.66.194.16/31 via 185.66.194.16;
}

Weitere Konfiguration vom w7 (wobei {fastd,bat}0 jetzt {fastd,bat}-wup sind). Alles routet durch, außer das Forum.

Das Problem wird sich bald von selbst lösen, da w7 kein GW mehr sein wird, da ich mit dem Debuggen fertig bin. Trotzdem ist es interessant, wo hier der Fehler liegt, um daraus zu lernen.