Hello Marius When I ask these rules ipencap is start and encap.txt is update but there is the following problem stops traffic to the network 44
if remove this:
iptables -t nat -A PREROUTING -p 4 -j DNAT --to 192.168.1.2
44 traffic is start and encap update is stoped.
probably wrong somewhere but trying to figure out where?
network structure to me is the following:
INTERNET-> TP-LINK wr841n(with Openwrt) -> Mikrotik (2.9.27 /in its settings no problem/) -> Debian (ampr-ripd gateway)
when TP-LINK wr841n is with original tp-link firmware and dmz to mikrotik is no problem to update encap and normal routing 44 network.
73, Miro LZ4NY
----- Цитат от Marius Petrescu (marius@yo2loj.ro), на 30.07.2016 в 16:10 ----- (Please trim inclusions from previous messages) _______________________________________________ Hi Miro,
If your primary router (the one you are setting the rules) does not need to process proto 4 and RIP, you can drop the 2 input rules.
The prerouting DNAT should be enough.
Marius, YO2LOJ
On 2016-07-30 12:51, lz4ny@mail.bg wrote: (Please trim inclusions from previous messages) _______________________________________________
Hello, I had a problem to let rip44d after an OpenWrt Chaos Calmer 15.05, but was dropped dmz traffic ipencap 169.228.66.251 not passed to the second router.
In openwrt menu: Network -> Firewall -> Custom Rules
I add:
---
iptables -A INPUT -p 4 -j ACCEPT iptables -A INPUT -p udp --dport 520 -j ACCEPT iptables -t nat -A PREROUTING -p 4 -j DNAT --to 192.168.1.2
---
192.168.1.2 is ip of second router or 44 gateway with rip44d
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-------------------------------------
ПП: СуперХостинг.БГ пазят място за твоя сайт. Имат супер летни отстъпки за нови и настоящи клиенти. Можеш да разглеждаш и другите им промоции. http://www.superhosting.bg/promo/summer?utm_source=MailBG&utm_medium=foo...