Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Richard E. Brown" <richb.hanover@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] CeroWrt 3.10.18-1 odd firewall warnings
Date: Mon, 2 Dec 2013 20:21:18 -0500	[thread overview]
Message-ID: <D3F1B8DE-9712-43A2-9AF1-B9B2459976F6@gmail.com> (raw)

When I was trying to set up the Hurricane Electric 6in4 tunnel, I got two sets of warnings from CeroWrt 3.10.18-1.

1) I used the tunnel.sh script (see URL below) to set up my tunnel. I got the first set of output. Note the “Error: Failed to connect to ubus” message. Is this OK? (The tunnel did come up after restarting the router.)

2) I then re-ran the firewall restart command (see second set of output) and saw a number of warnings. Any problems/surprises here?

Best,

Rich

============= 1) Restarting the firewall from the script that sets up the HE.net 6in4 tunnel ===========
============= see script at the bottom of: http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel

root@cerowrt:/tmp# sh tunnel.sh
Downloading http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.18-1/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/vancouver.
Package 6in4 (14-1) installed in root is up to date.
Setting up HE.net tunnel
Restarting network... "Device busy (-16)" messages are OK.
Restarting firewall...
Error: Failed to connect to ubus
Done. You should restart the router now to make these take effect.

============== 2) Restarting the firewall from the command line =============

root@cerowrt:~# uname -a
Linux cerowrt 3.10.18 #1 Sun Nov 10 14:35:09 PST 2013 mips GNU/Linux

root@cerowrt:~# /etc/init.d/firewall restart
 * Flushing IPv4 filter table
 * Flushing IPv4 nat table
 * Flushing IPv4 mangle table
 * Flushing IPv4 raw table
 * Flushing IPv6 filter table
 * Flushing IPv6 nat table
 * Flushing IPv6 mangle table
 * Flushing IPv6 raw table
 * Flushing conntrack table ...
 * Populating IPv4 filter table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
   * Rule 'domain'
   * Rule 'ntp'
   * Rule 'dhcp4'
   * Rule 'printers'
   * Rule 'Useful Services'
   * Rule 'blockconfig'
   * Rule 'blockconfig2'
   * Forward 'guest' -> 'wan'
   * Forward 'lan' -> 'wan'
   * Forward 'wan' -> 'lan'
   * Forward 'lan' -> 'guest'
   * Forward 'wan' -> 'guest'
 * Populating IPv4 nat table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
 * Populating IPv4 mangle table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
 * Populating IPv4 raw table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
 * Populating IPv6 filter table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
   * Rule 'domain'
   * Rule 'ntp'
   * Rule 'printers'
   * Rule 'Useful Services'
   * Rule 'ipv6 dfz'
   * Rule 'icmpv6'
   * Rule 'blockconfig'
   * Rule 'Allow-DHCPv6'
   * Rule 'blockconfig2'
   * Forward 'guest' -> 'wan'
   * Forward 'lan' -> 'wan'
   * Forward 'wan' -> 'lan'
   * Forward 'lan' -> 'guest'
   * Forward 'wan' -> 'guest'
 * Populating IPv6 nat table
   * Zone 'wan'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_wan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_wan_rule'
   * Zone 'lan'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_lan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_lan_rule'
   * Zone 'guest'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_guest_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_guest_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'delegate_prerouting'
Warning: fw3_ipt_rule_append(): Can't find target 'delegate_postrouting'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_rule'
 * Populating IPv6 mangle table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
 * Populating IPv6 raw table
   * Zone 'wan'
   * Zone 'lan'
   * Zone 'guest'
 * Set tcp_ecn to on
 * Set tcp_syncookies to on
 * Set tcp_window_scaling to on

             reply	other threads:[~2013-12-03  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  1:21 Richard E. Brown [this message]
2013-12-04  2:35 ` Jim Gettys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D3F1B8DE-9712-43A2-9AF1-B9B2459976F6@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox