From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id EB56120099A for ; Fri, 2 Mar 2012 02:50:26 -0800 (PST) Received: by wibhj6 with SMTP id hj6so931031wib.16 for ; Fri, 02 Mar 2012 02:50:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=PmLTqXo1abWEdtAX6FuQGgzJB5AwNCB7r2D72WiM3a0=; b=kreBi43QYUcvaEPesQfs4WROjmM99J39CPj0UY20gY8Y0iSgoE0hoNCWrdaFqN1YuU /y7ts+A6zuQN0l7KO4kGnIJZmSybLuDuQnMOmx6ncqbLOlljT79BaYgE08uEZYTsY28G kTfIzrMZMkBKpHBa+KnPDdVn14QFmRY+V5jemT7PE6syYwEgCCoGF+cAQuXfJyaPnEMR HCcYC4JSPgBUu46YmofOM8NUxl0OTKu4g3BVscD3vBMA86D3awJUr+1E4X6/G55qmus3 N2heh0OMF2cUlATKEOWMH/QSqOVn6wgYAzOP2IQ+C6xUo1mmmN3aph/4Y3LEPcQBEZtO PwVQ== MIME-Version: 1.0 Received: by 10.180.76.175 with SMTP id l15mr3246096wiw.2.1330685424830; Fri, 02 Mar 2012 02:50:24 -0800 (PST) Received: by 10.223.151.8 with HTTP; Fri, 2 Mar 2012 02:50:24 -0800 (PST) In-Reply-To: <1E158A98-D7F5-489F-89B6-B1673FBB8E84@intermapper.com> References: <1E158A98-D7F5-489F-89B6-B1673FBB8E84@intermapper.com> Date: Fri, 2 Mar 2012 02:50:24 -0800 Message-ID: From: Dave Taht To: Richard Brown Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "" Subject: Re: [Cerowrt-devel] CeroWrt port numbering X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 10:50:27 -0000 On Thu, Mar 1, 2012 at 8:22 PM, Richard Brown wrote: > While I was posting a note about 3.3-rc5-1 and tidying the site, I notice= d that the table on the Default Network Numbering page (http://www.bufferbl= oat.net/projects/cerowrt/wiki/Default_network_numbering) was incorrect - it= still showed the default se00 at 172.30.42.33. It's fixed. I also added a = row for ge00 as the public IP. thx! > > This led me to look at the various tables made available via SNMP, and I = had a couple consistency questions. (See the attached spreadsheet for the d= ata, especially rows 58-66. It was taken from bql-40, but I believe it's th= e same for 3.3.) I won't be able to look into the snmp stuff until next week. I'd like to know how well that is working with ipv6, btw, overall. > > - I note that there's no interface at 172.30.42.33/27. I believe this is = correct, but just checking. (It's thinkable that the se00 wired interface c= ould go to a /26 if more wired devices were needed. But let's keep to the r= ule "Everything's a /27" for a while longer.) I thought about widening the default /27 in this case, but long on my mind has been getting to where vlans could be successfully used and tested, so mentally that's 'reserved for dmz vlan'. This was actually why .33 was used instead of .1 for the main router interface in the early days, but too many people found that puzzling. > > - I'm a little surprised that the babel interfaces both have ...224/32. (= But I don't know anything about babel...) Actually that's an 'AHCP'-ism. Babel is capable of mesh routing, and with p2p wireless links nothing more than a /32 or /128 (for ipv6) is needed to be distributed on mesh node links. It makes failover simpler in the mesh routing case. > > - I'm confused about the OUI's for the interfaces. As expected, C4:3D:C7.= .. is the OUI for Netgear. But C6:3D:C7... isn't allocated to anyone. Is th= at by design? Two issues: There is no separate mac address for one of the network devices on the wndr, so we take a known good address from one of the devices, and flip the 'local mac' bit. Each wireless VIF creates it's own mac address as well, based on incrementing the underlying mac, and I don't remember the algo offhand. > > - I don't understand the pattern of the OUIs for the interfaces: why is t= he C4 prefix issued to the Ethernet ge00 and wireless sw00 and sw10, while = C6 goes to Ethernet se00 and the remaining wireless interfaces? > > - I also note that the MAC addresses sort to an odd order, intermixing et= hernet and wireless. (This is related to the previous item.) > > sw00 =A0 =A0C4:3D:C7:9D:E3:9A > ge00 =A0 =A0C4:3D:C7:9D:E3:9B > sw10 =A0 =A0C4:3D:C7:9D:E3:9C > > se00 =A0 =A0C6:3D:C7:9D:E3:9A > gw00 =A0 =A0C6:3D:C7:9D:E3:9B > gw01 =A0 =A0C6:3D:C7:9D:E3:9C > gw10 =A0 =A0C6:3D:C7:9D:E3:9D > gw11 =A0 =A0C6:3D:C7:9D:E3:9E Hopefully what I wrote above sort of explains this. > - Finally, I haven't fired up 6to4 or anything, but will the global IP ad= dress assignments be randomized more than the local (fe80) address? Not sure what you mean here. In the case of ipv6 autoconfiguration, you get EUI-64s based on the underlying mac addresses, which are long... In the case of 6to4 autoassignment ( the openwrt feature that didn't work for me in this week's test), each interface gets a 2002:X:Y:Z::1/64 where Z=3D1 for se00, and increments by one for every interface configured for the ge01 device. In the case of using dhcp-pd youu can either use ipv6 autoconfiguration for the downstream nodes, or install a dhcpv6 server to give more rationally numbered clients. > > Best, > > Rich > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net