[Commotion-dev] 2-port Ubiquiti NanoStations
Ben West
ben at gowasabi.net
Tue Feb 3 00:00:23 EST 2015
My guess is that eth0 and eth1 (at least as they are enumerated on power-up
to OpenWRT on the NSM5 I have) do not both sit on the embedded switch. The
AR7240 has two ethernet interfaces, with one intended as dedicated WAN
port, and the other (through the built-in switch) with capacity for
multiple LAN ports. The swconfig output you see for the unused ports may
just indicate that they auto-negotiate to 10Mbit when nothing is populated
there. Not sure about the connectivity you're nevertheless seeing b/w the
Nano and the Bullet, despite the former having no "eth1" address configured.
Perhaps see what "arp -s" has to say on the Nano? Maybe eth1 is being
implicitly bridged?
On Mon, Feb 2, 2015 at 8:02 PM, Joe Ayers <joe at ayerscasa.com> wrote:
> Here is what is peculiar I'm getting to the bottom of. We have
> configured in our image eth0.2, also an interface in olsr, to create what
> we call Device to Device Linking (DtDlink). A user insists he has
> connected a cat5 cable between the Bullet M2 into the secondary port of a
> Nanostation M2 at the top of a mast. I have remote access over this mesh
> and the two devices are communicating with each other over this vlan2. Our
> firmware and configuration has nothing configured for eth1. The swconfig
> command on the NSM2 shows the same except port 3, 4, and 5 have "link:up
> speed:10basetT". There must be more to the story...
>
> On Mon, Feb 2, 2015 at 5:43 PM, Ben West <ben at gowasabi.net> wrote:
>
>> If you mean the UBNT Nanostation M2 and M5 products, their LAN ports are
>> presented to OpenWRT as eth0 and eth1 (master & secondary, respectively),
>> with the switch only appearing in relation to eth1.
>>
>> Here is what swconfig has to say on an NSM5 I have running Attitude
>> Adjustment. May guess is that the switch chipset is only connected to the
>> SoC (port 1) and secondary LAN jack (port 0).
>>
>> root at router:~# swconfig dev eth1 help
>> switch0: eth1(AR7240/AR9330 built-in switch), ports: 5 (cpu @ 0), vlans:
>> 16
>> --switch
>> Attribute 1 (int): enable_vlan (Enable VLAN mode)
>> Attribute 2 (none): apply (Activate changes in the hardware)
>> Attribute 3 (none): reset (Reset the switch)
>> --vlan
>> Attribute 1 (int): vid (VLAN ID)
>> Attribute 2 (ports): ports (VLAN port mapping)
>> --port
>> Attribute 1 (int): pvid (Primary VLAN ID)
>> Attribute 2 (string): link (Get port link information)
>>
>> root at router:~# swconfig dev eth1 show
>> Global attributes:
>> enable_vlan: 0
>> Port 0:
>> pvid: 0
>> link: port:0 link:up speed:1000baseT full-duplex txflow rxflow
>> Port 1:
>> pvid: 0
>> link: port:1 link:up speed:100baseT full-duplex auto
>> Port 2:
>> pvid: 0
>> link: port:2 link:down
>> Port 3:
>> pvid: 0
>> link: port:3 link:down
>> Port 4:
>> pvid: 0
>> link: port:4 link:down
>> VLAN 0:
>> vid: 0
>> ports: 0 1 2 3 4
>>
>>
>> On Mon, Feb 2, 2015 at 6:31 PM, Joe Ayers <joe at ayerscasa.com> wrote:
>>
>>> We at www.bbhndev.org and www.BroadBand-HamNet.org are looking at the
>>> UBNT NanoStations with 2 ports. Has anyone run across information on the
>>> internal wiring between the AR7240 and AR9330 chipsets to properly
>>> configure switch0?
>>>
>>> By the way, we might want to connect up for other reasons. BBHN is
>>> essentially doing the same thing on top of OpenWRT for our community.
>>>
>>> regards,
>>> Joe Ayers AE6XE
>>>
>>> _______________________________________________
>>> Commotion-dev mailing list
>>> Commotion-dev at lists.chambana.net
>>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>>
>>>
>>
>>
>> --
>> Ben West
>> http://gowasabi.net
>> ben at gowasabi.net
>> 314-246-9434
>>
>
>
--
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20150202/6266c786/attachment.html>
More information about the Commotion-dev
mailing list