<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
There are no button presses to bring the box back, as you can with
some TP-Link routers.<br>
<br>
You could use a serial lead if you opened the case. No one has
mentioned trying this with cero on the list.<br>
<br>
So far, all bridging attempts with cero have been unproductive.
However sound the theoretical approach, they have not worked in
practice.<br>
<br>
As you would expect, subnetting a /48 works. DT has got subnetting
working with a /60 in the last 2 weeks.<br>
<br>
That is the current state of play.<br>
<br>
6relayd on OpenWRT is very difficult to configure. dnsmasq tends to
be simpler.<br>
<br>
Perhaps Kelley has something to say about configuration with, say, a
/64 provided by free.fr<br>
<br>
I know of only one ISP which provides a /48 to customers.<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 24/02/14 11:35, Vincent Frentzel
wrote:<br>
</div>
<blockquote
cite="mid:CACCCjEU+OY7qxNy8OqaqiRRDNHdV=q4sb2FW2-YsJGAzsVF2GQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>I am familiar with that command :) Was wondering if there
was something I could do when I cannot ssh into the router.
As mentioned above, when trying to configure the bridge I
hit a point where I could nt get in the router anymore.<br>
<br>
</div>
I understand the design decisions of the project and far from
me the idea of challenging them :) I was simply trying to
provide an alternative config with a standard bridge ethernet
+ wifi for reference. I believe that in the case mentioned by
Sebastian (multiple, mobile, devices accessing resources
across segments) bridging is a simple way forward.<br>
<br>
</div>
In my particular case, correct route propagation is a problem on
IPV6 (im not running babel) and I have only 2 wifi clients...
Bridging has never shown any perf issues in the past so I 'd
like to switch back to this simpler setup. I can picture that
this might not fit the bill for more intensive use cases.<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Feb 24, 2014 at 12:03 PM, Fred
Stratton <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:fredstratton@imap.cc" target="_blank">fredstratton@imap.cc</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> So much for memory<br>
<br>
mtd -r erase rootfs_data<br>
<br>
is the correct invocation.
<div>
<div class="h5"><br>
<br>
<br>
<div>On 24/02/14 10:18, Fred Stratton wrote:<br>
</div>
<blockquote type="cite"> I suggest you read the cero
wiki. This details the original design decisions. On
the router,<br>
<br>
ssh in, and use<br>
<br>
mtd -r erase fs_data<br>
<br>
to recover to defaults. See <br>
<br>
<a moz-do-not-send="true"
href="http://wiki.openwrt.org/doc/techref/mtd"
target="_blank">http://wiki.openwrt.org/doc/techref/mtd</a><br>
<br>
If you ever have used BB daily builds, you can type
this in your sleep.<br>
<br>
<br>
<br>
<br>
<div>On 24/02/14 10:05, Vincent Frentzel wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex"> <br>
I could be totally out for lunch
here, but shouldn't that be se00 (secure
ethernet) instead of eth0.1? At least on <a
moz-do-not-send="true"
href="tel:3.10.28-14" value="+13102814"
target="_blank">3.10.28-14</a> neuter
"ifconfig" nor /etc/config/network
mentions eth0.1 at all. Could you post
both of these (so the result of calling
ifconfig on a terminal on the router and
the content of /etc/config/network ;), I
am sure you know what I meant, just dying
to be verbose for the sake of people
stumbling over the archive of the mailing
list)<br>
</blockquote>
<div><br>
<br>
</div>
<div>Hi Sebastian,<br>
</div>
<div><br>
</div>
<div>Understood. I will come back to you
with the ifconfig.<br>
<br>
</div>
<div>For info, I did try both se00 and
eth0.1. The reason I stuck with eth0.1 was
that barrier breaker usually uses eth0.1
for br-lan with vlan enabled (eth0.1
appears in Luci in cerowrt). So in cero I
just reenabled the vlan and used a type
"bridge" on the network section (I renamed
this section se99 instead of se00). <br>
<br>
I then added se99 it to the "lan" zone of
the firewall. In the wireless config I
specified network as "se99" instead of
sw10 and sw00. I confirmed that the setup
was correct in the web interface where
eth0.1 sw00 and sw10 appeared under the
new bridged interface ( there was the nice
icon with the iface in brackets).<br>
<br>
</div>
<div>I went on to modify the dhcp config of
se00 and changed se00 occurences for se99
and commented out entries for sw10/sw00.
--> this would give me dhcp running on
my new bridge.<br>
<br>
</div>
<div>After a dnsmasq restart dnsmasq.conf
shows the dhcp ranges line with interface
se99. (I was expecting to see br-se99 but
maybe that file is alias aware, could be
wrong here).<br>
<br>
</div>
<div>After a network restart I lost
connectivity on cable. Wireless was
working.<br>
<br>
</div>
<div>I played a tad more and eventually lost
wifi as well and had to reflash the router
via tftp/factory image (maybe there is a
reset trick you could give me to avoid
this step).<br>
<br>
</div>
<div>Are you running cerowrt in bridge mode?
If yes could you share your
network/firewall/dhcp config? Is there
another file I should have edited and
missed?<br>
<br>
</div>
<div>Cheers,<br>
V<br>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Cerowrt-devel mailing list
<a moz-do-not-send="true" href="mailto:Cerowrt-devel@lists.bufferbloat.net" target="_blank">Cerowrt-devel@lists.bufferbloat.net</a>
<a moz-do-not-send="true" href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Cerowrt-devel mailing list
<a moz-do-not-send="true" href="mailto:Cerowrt-devel@lists.bufferbloat.net" target="_blank">Cerowrt-devel@lists.bufferbloat.net</a>
<a moz-do-not-send="true" href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Cerowrt-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Cerowrt-devel@lists.bufferbloat.net">Cerowrt-devel@lists.bufferbloat.net</a><br>
<a moz-do-not-send="true"
href="https://lists.bufferbloat.net/listinfo/cerowrt-devel"
target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>