From: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
To: "Richard E. Brown" <richb.hanover@gmail.com>
Cc: 'Richard Brown' <Rich.Brown@intermapper.com>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Got DHCPv6 working in CeroWrt 3.7.x over HE.net tunnel
Date: Sun, 27 Jan 2013 10:46:29 +0200 [thread overview]
Message-ID: <5104E965.8030003@etorok.net> (raw)
In-Reply-To: <EE30C9AE-1B20-480A-82B9-4BC5FB2578A4@gmail.com>
On 01/27/2013 06:17 AM, Richard E. Brown wrote:
> Thanks to Dave Täht and Robert Bradley for the pointers to making CeroWrt 3.7.x hand out IPv6 addresses to LAN devices. (This has been tested with 3.7.4-2.) The process is indeed a few simple steps:
>
> 1) remove dnsmasq & dnsmasq-dhcpv6, then install again (see Dave Täht's note below)
> 2) Add config to /etc/dnsmasq.conf to hand out DHCPv6 addresses (as suggested by Robert Bradley)
Yep, that sounds like what I've done too.
> 3) Tweak the firewall to put henet 6in4 tunnel into WAN zone
> 3) Bring up henet and restart network, firewall, dnsmasq
Not related to ipv6, but if you want a ntp server for your LAN you have to do this:
# opkg remove luci-app-ntpc
# opkg remove ntpclient
# killall ntpclient
# uci set system.ntp.enable_server 1
# uci commit system
# /etc/init.d/sysntpd restart
Otherwise sysntpd will fail to start because ntpclient has already bound the ntp port.
According to http://wiki.openwrt.org/doc/uci/system busybox ntpd can act both as a client&server so
I think that ntpclient is unnecessary.
>
> There's a fully-functional script at: http://www.bufferbloat.net/attachments/download/165/tunnelbroker.sh that does this. (You'll have to substitute your own credentials there…) Save the script as a
> file in /tmp and execute it - it does all the configuration for you.
Just one note regarding this comment in your script:
# Append proper configuration commands to /etc/dnsmasq.conf
# This is the proper configuration file: you can ignore both
# /etc/config/dhcp and /var/etc/dnsmasq.conf as they seem not to have any effect
/var/etc/dnsmasq.conf is overwritten when you '/etc/init.d/dnsmasq restart', thats why it seems to not have an effect.
BTW initially I was doing this:
# /etc/init.d/dnsmasq stop
# vi /var/etc/dnsmasq.conf
# /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -d
....
^C
# vi /var/etc/dnsmasq.conf
# /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -d
....
But after reinstalling dnsmasq-dhcpv6 I realized that just modifying /etc/dnsmasq.conf and restarting dnsmasq worked too
(presumably due to this entry in /var/etc/dnsmasq.conf: conf-file=/etc/dnsmasq.conf).
Best regards,
--Edwin
next prev parent reply other threads:[~2013-01-27 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54532012A5393D4E8F57704A4D55237E42B20614@CH1PRD0510MB381.namprd05.prod.outlook.com>
[not found] ` <CAA93jw5six+LmsvDOUnSjMy0NJdzG5N+pUdg-YJ7u2V-ok9tag@mail.gmail.com>
[not found] ` <510471bf.4a63b40a.4aa1.67a7@mx.google.com>
2013-01-27 4:17 ` Richard E. Brown
2013-01-27 8:46 ` Török Edwin [this message]
2013-01-27 11:25 ` Dave Taht
2013-01-27 11:28 ` Dave Taht
2013-01-27 11:35 ` Török Edwin
2013-01-27 11:47 ` Dave Taht
2013-01-27 15:11 ` Richard E. Brown
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=5104E965.8030003@etorok.net \
--to=edwin+ml-cerowrt@etorok.net \
--cc=Rich.Brown@intermapper.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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