Thanks for the reply oversc0re!
The cron is not the problem, I've tried to run the update_traf.sh manually and followed by plot_traf.sh.
This got a bit big, but heres my iptables -L output:
I'm aware that there are duplicate entries, I ran ./add_iptables.sh two times... But you see my data.
I've made a start.sh which I run from post-boot (it runs after mounting usb-drive).Code:Chain INPUT (policy ACCEPT) target prot opt source destination router_in all -- !192.168.1.0/24 trondelag-dhcxxxxxecom.no router_in all -- !192.168.1.0/24 trondelagxxxxxxxom.no MACS all -- anywhere anywhere DROP all -- anywhere anywhere state INVALID ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere state NEW ACCEPT all -- anywhere anywhere state NEW SECURITY all -- anywhere anywhere state NEW ACCEPT udp -- anywhere anywhere udp spt:bootps dpt:bootpc ACCEPT tcp -- anywhere anywhere tcp dpt:ftp DROP all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination traffic_out all -- anywhere anywhere traffic_in all -- anywhere anywhere traffic_out all -- anywhere anywhere traffic_in all -- anywhere anywhere MACS all -- anywhere anywhere ACCEPT all -- anywhere anywhere DROP all -- anywhere anywhere state INVALID ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED SECURITY all -- anywhere anywhere state NEW ACCEPT tcp -- anywhere 192.168.1.2 tcp dpts:ftp-data:ftp ACCEPT tcp -- anywhere 192.168.1.2 tcp dpts:6881:6882 ACCEPT udp -- anywhere 192.168.1.2 udp dpts:6881:6882 ACCEPT tcp -- anywhere 192.168.1.2 tcp dpt:31214 ACCEPT udp -- anywhere 192.168.1.2 udp dpt:31214 ACCEPT tcp -- anywhere 192.168.1.4 tcp dpt:32493 ACCEPT udp -- anywhere 192.168.1.4 udp dpt:32493 ACCEPT udp -- anywhere anywhere udp dpt:6112 Chain OUTPUT (policy ACCEPT) target prot opt source destination router_out all -- tronxxxxxxcom.no !192.168.1.0/24 router_out all -- tronxxxxxxxxxxom.no !192.168.1.0/24 Chain MACS (2 references) target prot opt source destination Chain SECURITY (2 references) target prot opt source destination RETURN tcp -- anywhere anywhere tcp flags:SYN,RST,ACK/SYN limi t: avg 1/sec burst 5 RETURN tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,ACK/RST limit: avg 1/sec burst 5 RETURN udp -- anywhere anywhere limit: avg 5/sec burst 5 RETURN icmp -- anywhere anywhere limit: avg 5/sec burst 5 DROP all -- anywhere anywhere Chain logaccept (0 references) target prot opt source destination LOG all -- anywhere anywhere state NEW LOG level warning tc p-sequence tcp-options ip-options prefix `ACCEPT ' ACCEPT all -- anywhere anywhere Chain logdrop (0 references) target prot opt source destination LOG all -- anywhere anywhere state NEW LOG level warning tc p-sequence tcp-options ip-options prefix `DROP' DROP all -- anywhere anywhere Chain router_in (2 references) target prot opt source destination all -- anywhere anywhere all -- anywhere anywhere Chain router_out (2 references) target prot opt source destination all -- anywhere anywhere all -- anywhere anywhere Chain traffic_in (2 references) target prot opt source destination all -- anywhere 192.168.1.2 all -- anywhere 192.168.1.3 all -- anywhere 192.168.1.4 all -- anywhere !192.168.1.0/24 all -- anywhere 192.168.1.2 all -- anywhere 192.168.1.3 all -- anywhere 192.168.1.4 all -- anywhere !192.168.1.0/24 Chain traffic_out (2 references) target prot opt source destination all -- 192.168.1.2 anywhere all -- 192.168.1.3 anywhere all -- 192.168.1.4 anywhere all -- !192.168.1.0/24 anywhere all -- 192.168.1.2 anywhere all -- 192.168.1.3 anywhere all -- 192.168.1.4 anywhere all -- !192.168.1.0/24 anywhere
Start.sh:
Edit:Code:#/bin/sh /opt/rrd/add_iptables.sh /opt/rrd/init_traf.sh /opt/rrd/update_traf.sh /opt/rrd/plot_traf.sh
Just add that the image generation works just fine for eth0/eth1 (somehow they both contain data?). Which one is the "wan" port on the back of the router?


Reply With Quote
Keep on trying until the numbers start rolling.