Mochabin is shipping again (or so I am told)

Full disclosure.. I am an FAE supporting Marvell products. This means my posts may be tainted (but not misleading).

However, Some are receiving these boards from crowdfunding. I hope to see mine soon.
I chose the one with OpenWRT installed and hope to replace my 4G mobile hotspot with this one.

Based on this, I welcome insight from others who have already received their Mochabin and plan to share mine once I get the device in hand.

Thanks for letting me join the forum and I hope we can share info!

Just got mine (from the Kickstarter) 8gb supposedly with OpenWRT on it. I see some ICMPv6 activity on the LAN ports, but nothing for ipv4. Nothing at OpenWRT's usual 192.168.1.1 default IP. Do I really need to hook up a serial connection to get this going? (I don't know from ipv6) It's physically larger than i expected, but no fan is nice. Haven't opened it up yet, but plan to install a 5g modem.

Nice. I was just given a tracking number today. So, Saturday I get mine. I opted for the 5g modem.
Also, I don't have experience with it yet.

So, all guess work here.

I would connect to one of the 1G LAN ports (probably one of the 4-port pack) ports and see if your DHCPREQUEST gets ad DHCPACK and you get served a IP from the Mochabin.

If you get an IP on your PC, see if you can get browser page to the gateway device (probably will be 192.168.1.1).

I will bring mine up soon after it arrives and know a bit more.

Also, is there a new Access point in your list? If you find a new one, it may be the Mochabin. If you can attach, then try the gateway address (probably 192.168.1.1).

I certainly hope we don't have to attach via serial console to u-boot. But, it seems pretty standard if I do need to.

If one attached to the serial console we can hope it is a log in prompt and not a u-boot shell.

If it is a u-boot shell try the command 'run $bootcmd' (no quotes).

thanx, Frank. Yes, I'm pretty good with dhcp and ipv4. as mentioned, no signs of ipv4 life (dhcp or otherwise) from it. no ping at any address in the 192.168.0.0/24. just some icmpv6 packets, apparently doing the equivalent of ARP? (router solicitation and listener report packets) Could they have enabled ipv6 only and not ipv4? seems odd... Looking forward to hearing others experience and how to "make it go"...

Thanks. Sorry if I seemed to describe the obvious. We all have our individual knowledge strengths. So I sort of posted 'mid-way'.

I look forward to getting mine (tomorrow??). Then I will be able to test before I speculate.

Globalscale is responsive (thanx Kevin!) and it seems I ordered the 'standard early bird', not the OpenWRT flavor. Still trying to determine what that would be and how to access it over ethernet. I'll do the serial connection to get vanilla OpenWRT (and eventually Rooter) on it if that's what it takes, but seems weird to not have any IPv4 interface accessible out of the box, whatever the pre-installed image...

per the 'qucik start' pdf at https://globalscaletechnologies.com/wp-content/uploads/2021/09/MOCHABIN-BOX-Quick-Start-Guide-Jan10-2020.pdf, I connected to console via USB. it's got Linux with no ipv4 configured by default:

root@moca289e49:~# uname -a
Linux moca289e47 5.4.163-00034-ga7e9e3c22288 #1 SMP PREEMPT Mon Aug 29 10:38:30 CST 2022 aarch64 aarch64 aarch64 GNU/Linux
root@moca289e49:~# ifconfig
bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST>  mtu 1500
        ether f0:ad:4e:28:9e:47  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
        ether f0:ad:4e:28:9e:47  txqueuelen 2048  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1508
        inet6 fe80::f2ad:4eff:fe28:9e48  prefixlen 64  scopeid 0x20<link>
        ether f0:ad:4e:28:9e:48  txqueuelen 2048  (Ethernet)
        RX packets 192219  bytes 40109586 (40.1 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 55  bytes 5530 (5.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
        ether f0:ad:4e:28:9e:47  txqueuelen 2048  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f0:ad:4e:28:9e:48  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::f2ad:4eff:fe28:9e48  prefixlen 64  scopeid 0x20<link>
        ether f0:ad:4e:28:9e:48  txqueuelen 1000  (Ethernet)
        RX packets 192219  bytes 35880768 (35.8 MB)
        RX errors 0  dropped 53465  overruns 0  frame 0
        TX packets 30  bytes 3096 (3.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lan2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f0:ad:4e:28:9e:48  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lan3: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f0:ad:4e:28:9e:48  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 17146  bytes 1125682 (1.1 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17146  bytes 1125682 (1.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@moca289e49:~#

My Moca arrived with OpenWrt working.
I used the ETH method I outlined above and as able to enable Wireless.
Basic functions that work so far:

  1. RJ45/ETH WAN
  2. One of the RJ45/ETH LAN (have not tested them all)
  3. Wifi 5G and 2.4G

My next plan is to take an update from here:
https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa72/openwrt-mvebu-cortexa72-globalscale_mochabin-squashfs-sdcard.img.gz
(although I am concerned about 'sdcard' in the file name).

After that I will install the provided 5G Modem and antennae.

Oh good. It is booted to the OS.
I don't know if it is appropriate to talk non-WRT stuff here.
But, I would:

  1. dhclient or the like to get an IP from your existing network
  2. install dnsmasq and config it for the 40-pack of ports and go from there if I wanted this to be a router

i just wanted to run Rooter (openwrt fork) on it. I know it's a kickstarter and all that, and I'll get there eventually (determined this one is) but would be nice to have an easier path to functionality...

I just realized that for use with 4g/5g modems, it's lacking any holes in the case for external antenna connections...

I tried the download I indicated and it failed to work. Gave me an error. So, I may have to go down to u-boot to replace the openwrt from factory so I can update to one from tree.

Yes. the antennae are stick-on for inside the chassis. So, if I want to add the paddle antennae I need to rework the chassis.

So, i'm a bozo. I was trying to connect from the LAN ethernet and that was not configured by default. However, plugging the WAN ethernet port into my network, it got a IPV4 DHCP lease and i was able to ping it and log in, so that explains what was going on there.

I was able to simply copy the OpenWRT/Rooter image onto a USB flash drive, mount it from the serial interface, and follow the instructions starting at the 'Gunzip and dd the image:' section of https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=78cf3e53b1f4ea6428925302d78f743a693d5fb1

I present the (world's first?) MochaBin Rooter: https://flic.kr/p/2nZ34sj

have yet to try doing anything with it, so stay tuned... Next, to open it up and install a modem.

2 Likes

Fun fact: Marvell has a very „special“ place in the heart of many OpenWRT users.

A while ago Marvell sold the router chip business to NXP and NXP then got the idea, to drop driver support for a kind of relevant chip series used in the famous Linksys 2017 WRT router series (which was by the way the most anticipated router series for years in this forum). And sadly this sell-off happened, before a lot of relevant bugs got fixed or any relevant driver stuff got finished or opensourced.
…Nothing personal, just dont be surprised that a lot of OpenWRT users have some trust issues towards a few company names since then.

This project seems very similar to the Banana Pi BPI-R3. I'm glad to see more projects like this. I think I prefer the BPI-R3, due to the 2GHz quad core CPU, and Mediatek chips - I've become a big fan of Mediatek. But it's always good to see more projects like this.

This is one reason why I love Mediatek. They are very Linux friendly.

Doesn't look like an alternative if you want a 5G router. Miini-PCIe slot is a bit dated and probably implies USB2 only. I believe the Mochabin has USB3 on the LTE/5G m.2 slot. And the BPI-R3 PoE layout looks braindead. Who ever came up with that idea?

And 2.5Gbits SFPs? 2 of them? Really? If all you can do is 2.5 then you might as well include the phy and RJ45 port. Those slots are nothing more than ordinary SFP slots if you are going to use when with fibre. Why didn't they add at least one SFP+?

The Mediatek SoCs look nice, but it should be possible to create a much better board than that one.

I agree that strapping the 5G onto USB3 is less than ideal. One can possibly use some of the 6 SERDES lanes. This would likely have been at the cost of the board design/assembly/test.
However, is this pic not showing an available SFP+ on the MochaBin?

(https://ksr-ugc.imgix.net/assets/035/139/865/cfcb06d0fe6e83834e8d700da485a333_original.jpg?ixlib=rb-4.0.2&w=680&fit=max&v=1633540806&gif-q=50&q=92&s=5469e06638b34b769b1b19bc975d505b)

Yes, but as stated, the BPI-R3 has 2 SFPs.

1 Like

Well, it's much better than USB2 which seems to be the alternative here. Using PCIe for 5G is still somewhat uncommon.

Yes, that was what I meant. I complained about the Banana Pi BPI-R3 which was presented as a similar Mediatek based board. Sorry if that wasn't clear.

If I read this correctly this is 2@2.5GbE SFP

As opposed to 1@10GbE and 1@1GbE of MochaBin.

Certainly a tradeoff. if one has no need for 10GbE one can definitely slow down the 10G. But one may not be able to take the 1GbE to 2.5 agreed.

I have not tested. However, in favor or the BPI-R3, I have heard that both optical interfaces may not be usable at the same time on MochaBin. TBD.