From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<Cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Getting ssh (or DHCP options) on Cerowrt
Date: Tue, 14 Jun 2016 18:45:35 -0700 [thread overview]
Message-ID: <CAA93jw40PoRv_w-iJCgoP7WE=WYCd7wQe7O1kvFdA-yagjtLPQ@mail.gmail.com> (raw)
In-Reply-To: <20160614163853.489ec952@xeon-e3>
in CeroWrt, ssh is managed and spawned by xinetd. You can add another
port to spawn it on (and restrictions on it) using xinetd's conf
files. You may need to also open the port in the /etc/config/firewall.
Alternatively, upgrade to lede. While I am not aware of any
devastating bugs exposed in CeroWrt, the dnssec support in particular
has been broken by events since.
As for the dhcp options, there is no gui for it, but the alternate
dhcp options can be added in /etc/config/dhcp.
https://wiki.openwrt.org/doc/uci/dhcp
On Tue, Jun 14, 2016 at 4:38 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> I need to add some TFTP boot options to one system on the network.
> But can't figure out how to get ssh console access to work. I have
> full web client menu access, but when I try enabling SSH on normal
> or other port nothing happens. I suspect some clash between the Dropbear
> ssh server in OpenWrt and some of the honey pots that are in Cerowrt.
>
>
> Alternatively, is there a way to edit the DHCP options sent in responses.
> I know that for Vyatta we ended up having to have a free-form edit box
> kind of response because there were so many possiblities.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
prev parent reply other threads:[~2016-06-15 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 23:38 Stephen Hemminger
2016-06-15 1:45 ` Dave Taht [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='CAA93jw40PoRv_w-iJCgoP7WE=WYCd7wQe7O1kvFdA-yagjtLPQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=Cerowrt-devel@lists.bufferbloat.net \
--cc=stephen@networkplumber.org \
/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