[Cerowrt-devel] CeroWrt port numbering
dave.taht at gmail.com
Fri Mar 2 05:50:24 EST 2012
On Thu, Mar 1, 2012 at 8:22 PM, Richard Brown
<richard.e.brown at dartware.com> wrote:
> While I was posting a note about 3.3-rc5-1 and tidying the site, I noticed that the table on the Default Network Numbering page (http://www.bufferbloat.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.
> 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 data, especially rows 58-66. It was taken from bql-40, but I believe it's the 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 could go to a /26 if more wired devices were needed. But let's keep to the rule "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
> - 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 that by design?
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
> - I don't understand the pattern of the OUIs for the interfaces: why is the 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 ethernet and wireless. (This is related to the previous item.)
> sw00 C4:3D:C7:9D:E3:9A
> ge00 C4:3D:C7:9D:E3:9B
> sw10 C4:3D:C7:9D:E3:9C
> se00 C6:3D:C7:9D:E3:9A
> gw00 C6:3D:C7:9D:E3:9B
> gw01 C6:3D:C7:9D:E3:9C
> gw10 C6:3D:C7:9D:E3:9D
> gw11 C6: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 address 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
where Z=1 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.
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
US Tel: 1-239-829-5608
More information about the Cerowrt-devel