From: "R." <redag2@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] SIP ATA device trouble over wireless Ethernet bridge [NAT-related?]
Date: Sat, 31 May 2014 20:54:53 -0400 [thread overview]
Message-ID: <CACj-SW31ijCDFTDTLgB14aW-1ipUhRqx_VJqqe5TGy6qscKJMg@mail.gmail.com> (raw)
In-Reply-To: <CACj-SW3LcbLewXKUm_D_WkxXAgmj8j6mu9d0AEXq2MSrHB7Y5g@mail.gmail.com>
Well, it seems like issuing this command on boot-up (in rc.local)
fixed the issue:
/etc/init.d/firewall restart;
I tested it on a defaulted Cero firewall configuration. Seems like it
triggered the right stuff?
Will report back if it breaks again.
On Sat, May 31, 2014 at 1:17 PM, R. <redag2@gmail.com> wrote:
> My setup is the following:
>
> Cable modem <- Netgear WNDR3800¹ <- Linksys WRT54GL² <- Linksys
> PAP2T-NA (SIP ATA device) <- Phone
>
>
> While running OpenWRT, the setup was working fine. The ATA was
> connecting/registering without a problem. It does NAT-traversal and
> has STUN enabled.
>
> While running CeroWRT, the setup has had many hiccups. I read on the
> Wiki³ that Cero might have NAT disabled by default.
> I tried many different firewall settings to get it working, without
> success. I've tried putting everything on "accept", "masquerading"=ON
> everywhere, and tried assigning ge00 to all possible (default) zones.
>
> Any ideas as to what could be causing this?
>
>
> ¹ Running Cerowrt 3.10.40-6
> ² Running Tomato
> ³ "CeroWrt is a test platform, and as such we wanted it to co-exist
> within existing networks as best as possible, without conflicting with
> an existing network, and to not require NAT in order to function
> inside that network. NAT skews some test results horribly."
prev parent reply other threads:[~2014-06-01 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 17:17 R.
2014-06-01 0:54 ` R. [this message]
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=CACj-SW31ijCDFTDTLgB14aW-1ipUhRqx_VJqqe5TGy6qscKJMg@mail.gmail.com \
--to=redag2@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