From: Richard Brown <Rich.Brown@intermapper.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt 3.7.2-3 released, still in a battle with ipv6
Date: Sat, 19 Jan 2013 00:41:09 +0000 [thread overview]
Message-ID: <54532012A5393D4E8F57704A4D55237E42ADDEBB@CH1PRD0510MB381.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAA93jw7bT6W7xHbtw8F54dngWDynx_4QyWdDFKoKe_PDP_U3rQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4087 bytes --]
Dave,
Could you post the generated dnsmasq.conf file and your network file and cc steven barth?
Here's my /etc/dnsmasq.conf file and the /etc/config/network file. (I have taken out the hemet credentials (!))
I don't have Steven Barth's address.
Rich
--------------------------
root@OpenWrt:/tmp# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config interface 'se00'
option ifname 'se00'
option proto 'static'
option ipaddr '172.30.42.1'
option netmask '255.255.255.224'
option ip6assign '64'
config interface 'ge00'
option ifname 'ge00'
option proto 'dhcp'
config interface 'ge01'
option ifname '@ge00'
option proto 'dhcpv6'
option broadcast '1'
option metric '2048'
option reqprefix '60'
config interface 'sw00'
option type 'none'
option proto 'static'
option ipaddr '172.30.42.65'
option netmask '255.255.255.224'
option ip6assign '64'
config interface 'sw10'
option type 'none'
option proto 'static'
option ipaddr '172.30.42.97'
option netmask '255.255.255.224'
option ip6assign '64'
config switch
option name 'rtl8366s'
option reset '1'
option enable_vlan '0'
option blinkrate '2'
option max_length '3'
config switch_vlan
option device 'rtl8366s'
option vlan '1'
option ports '0 1 2 3 5t'
config switch_port
option device 'rtl8366s'
option port '1'
option led '6'
config switch_port
option device 'rtl8366s'
option port '2'
option led '9'
config switch_port
option device 'rtl8366s'
option port '5'
option led '2'
config interface 'gw00'
option type 'none'
option proto 'static'
option ipaddr '172.30.42.129'
option netmask '255.255.255.224'
option ip6assign '64'
config interface 'gw10'
option type 'none'
option proto 'static'
option ipaddr '172.30.42.161'
option netmask '255.255.255.224'
option ip6assign '64'
config interface 'gw01'
option proto 'ahcp'
config interface 'gw11'
option proto 'ahcp'
config interface 'henet'
option proto '6in4'
option mtu '1424'
option ttl '64'
option peeraddr '209.51.161.14'
option ip6addr 'xxxx::2/64'
option ip6prefix 'xxxx::/48'
option tunnelid '#######'
option username 'tbxxxxxx'
option password 'xxxxxxxx'
----------------------------------------------------
root@OpenWrt:/etc# cat dnsmasq.conf
# Change the following lines if you want dnsmasq to serve SRV
# records.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# A SRV record sending LDAP for the example.com<http://example.com> domain to
# ldapserver.example.com<http://ldapserver.example.com> port 289
#srv-host=_ldap._tcp.example.com<http://tcp.example.com>,ldapserver.example.com<http://ldapserver.example.com>,389
# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com<http://tcp.example.com>,ldapserver.example.com<http://ldapserver.example.com>,389,1
#srv-host=_ldap._tcp.example.com<http://tcp.example.com>,ldapserver.example.com<http://ldapserver.example.com>,389,2
# A SRV record indicating that there is no LDAP server for the domain
# example.com<http://example.com>
#srv-host=_ldap._tcp.example.com<http://tcp.example.com>
# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD.
# The fields are <name>,<target>
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf.
# The fields are <name>,<text>,<text>...
#Example SPF.
#txt-record=example.com<http://example.com>,"v=spf1 a -all"
#Example zeroconf
#txt-record=_http._tcp.example.com<http://tcp.example.com>,name=value,paper=A4
# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
# The fields are <cname>,<target>
#cname=bertand,bert
[-- Attachment #2: Type: text/html, Size: 13435 bytes --]
next prev parent reply other threads:[~2013-01-19 0:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5563.1358459264.1742.cerowrt-devel@lists.bufferbloat.net>
2013-01-18 13:23 ` Richard Brown
2013-01-18 15:26 ` Dave Taht
2013-01-18 15:53 ` Richard Brown
2013-01-18 15:54 ` Dave Taht
2013-01-18 18:07 ` Robert Bradley
2013-01-18 18:11 ` Dave Taht
2013-01-18 18:30 ` Robert Bradley
2013-01-19 0:41 ` Richard Brown [this message]
2013-01-19 9:45 ` Maciej Soltysiak
2013-01-16 11:37 Dave Taht
2013-01-16 21:12 ` Maciej Soltysiak
2013-01-16 21:48 ` Dave Taht
2013-01-16 21:53 ` Maciej Soltysiak
2013-01-17 21:45 ` Maciej Soltysiak
2013-01-17 21:47 ` Dave Taht
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=54532012A5393D4E8F57704A4D55237E42ADDEBB@CH1PRD0510MB381.namprd05.prod.outlook.com \
--to=rich.brown@intermapper.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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