What is this board??? Help!
-
If it's a C2K SoC it will have 4 igb NICs built in, you should see that in the boot logs. In pfSense they may well show as unattached if they have an unknown phy type.
I imagine they are the 2 WANs, the sfp port and one to a switch for the LAN ports.
Check
pciconf -lvfor other devices.What does the detected NIC show for
ifconfig -vm igb0? Assuming it is igb0.You got photos?
Steve
-
@ChrisMontrose said in What is this board??? Help!:
How awesome of a pfsense router would this be??
Not that much really. Any C2xxx Atom or even better the newer C3000 Denverton Atoms would be far more "awesome" than that - especially if they somehow modified the PHY part so they won't work as igb or ix style interfaces. ;)
-
@stephenw10
Hey Steve! Thank you so much for your reply.
I really appreciate any help I can get.
FYI / Warning I am new to pfsense and linuxOk here is a pic of the ports on the back
Here is the top of the board
i noticed in pfsense when i run
ifconfig -vm igb0
it shows f0:8e:db:01:29:73
and i see this mac address on a sticker on im guessing for the 4th lan port based on this pictureAnd the bottom
This is the readout of the console on boot with its original velocloud software before I flashed it with pfSense
velocloud boot info.txtand here is the boot info with pfSense and the
pciconf -lv and
ifconfig -vm igb0
commands pfsense boot info.txtwhen assigning wan interface I tried auto with no luck. When I plug a Ethernet cable from my current router lan port i get link lights on the velocloud lan ports but not the wan ports but cant get pfsense to show a link.
-
Ok so it's running an old OpenWRT, you could try the generic x86 image and see what happens.
It has a Marvel switch and 4 igb NICs as expected. Three of them are not supported by the standard driver:
device_attach: igb0 attach returned 6The switch is connected via Eth1?
[ 2.344164] eth1[0]: detected a Marvell m88e6176 switchWhat are the other two Marvell ICs on the bottom of the board? I'd guess they are the PHYs for the 3 non detected NICs.
Since only one is detected I'd guess it's the SFP port but the reported media types do no reflect that in which case it may be the switch connection. Since the two WANs I would expect to be the same.Supported Atheros adapter is nice.
Make sure you get that heat pad back in some useful way.
Steve
-
-
Ha!
Well there's always a chance.
Getting the NICs to recognise new PHYs can be.... challenging! As can configuring the switch, which would be all command line in CE.
I would think there's a good chance of getting OpenWRT up on it though. Better on their forum for that.Getting those chip IDs would be the first step.
You might also try a 2.5 snapshot. The FreeBSD 12 drivers probably support more PHY combinations.
Steve
-
@chrismontrose So I have a few of these, did you make any progress with this?
-
Mmm, I'd forgotten about this.
I have a learnt a little more since then though. To make this work with pfSense fully you would need a custom igb driver. Both because it looks like it's rejecting the PHYs attached to them in the standard driver and because you need one that has code to generate the mdio device attached to igb0 so that etherswitch can use it to setup the switch. The switch ports will remain disabled until that is done.
If I had one I would try booting a 2.4.5p1 image and a 2.5 image to see if either have an igb driver that can see the PHYs.
I would also try booting in verbose mode to see if any other errors are shown by the NIC driver.Steve
-
@stephenw10 I am going to give that the good old college try.
-
@ryno5514 I have a 5x0 Edge 520-AC
I'd like to help this project. Here's what I could find so far.
https://gist.github.com/bubbadestroy/6dba169e79e144a70b9005a92816a474
And the commercial Open Source attempt at sd-wan
https://docs.flexiwan.com/overview/open-source.html -
The driver to allow connecting to the switch must have existed somewhere at some point because Stormshield/Netasq had some devices using identical switches with SoCs and their OS is also FreeBSD based. However it appears the never upstreamed the driver changes. Or at least I cannot find them.
Steve
-
@bubbadestroy Thanks!!!! I will take a look at this, I have 3 of them and will have 200 if this works.
-
Anyone try booting OpenWRT on it yet? They have far more extensive switch drivers.
-
@stephenw10 I have not but will give that a try also.
-
@stephenw10 said in What is this board??? Help!:
The driver to allow connecting to the switch must have existed somewhere at some point because Stormshield/Netasq had some devices using identical switches with SoCs and their OS is also FreeBSD based. However it appears the never upstreamed the driver changes. Or at least I cannot find them.
Steve
I was just about to suggest that.
My direction next was to brush upon the architecture as if to build a similiar but open source virtual machine from baremetal into pfsense open source enviornment and find a CVE to expose and exploit for eng/dev/su permlission (I have Earthlink and a Mitel as well.
I believe this board had a massive CVE in the early on merge of VMware and velocloud... that I had backed up and ill dig up.
On that note. If this picks up... the boxes are being tossed on ebay at 50, and theyll take or best offers for half! I believe the vulnerabilities and companies shifting around affiliate rights with new partners (DELL is open sauce now I think) made these early models EOL to enterprise purpose and ready to tinker on.
https://fccid.io/NCC/CCAJ16LP3430T2
https://fccid.io/NCC/CCAJ20Z10010T2
-
This post is deleted! -
What you're looking for to get functionality to the ports is a FreeBSD igb driver that differs from the default driver by:
- Allowing it to attach to a device that has an unrecognised PHY or knows about the PHY used here.
- Exposes the MDIO connection so that the FreeBSD mdio driver can attach to it. The etherswitch framework requires that to read/configure the switch.
There is a possibility the switch can be controlled by some other bus, i2c for example, but that seems to be far less common. Everything I've looked at controls it via the MDIO line on one of the NICs. Like here or here
Steve
-
Thank you that clears it up. I was learning as I read and u to chalk it up to I'll write up how it goes after I try :)
TLDR
You guys most likely know this.. But do (I understand?) This is the gist of what I am reading I believe.
Researched more into for myself now.
Before getting in or getting too off the scope of topic here.Super TLDR: get intel drivers from a dev cloud like mediatek or whatever. be careful before u compile and deploy the final firmware build onto the controllers microchip. as it does come with crypto-auth signing codes through an Over The Air checkpoint/cloud/orchestrato.
I have yet to Read more about FIDO and uPCE
Here's are what we're dealing with.You're working against Intel's sandbox right?
That's what the driver signing is for. you need a white-box. Possibly you can register this one as a white-box on an open platform that won't attempt to sandbox you ..Just be careful. Maybe use the intel uCPE to build and sign the rest of the box via ssh through their cloud API.
I mean if anyone is going to help individual devs build on safe but not jailed box it should be the microchip manufacturers that control what you can expose OTI anyhow.Reading up for myself SD-WAN. I'm quite new to this in general.. I just try to Read the Docs and "hack" my way through. Like mario bros.
Anyhow hopefully its set up for you to just go in, orchestrate a virtual dev-workstation, fine tune it and call up some driver scripts over ssh API to load up firmware that is good to go, signed and all through intel.
Should look into a git, or the platform will force you to have one, which is good.Some things to read
Vendor Agnostic Provisioning:
Ability to provision any device
(Intel or ARM hardware) to any
vendor’s DMS system.
• Provision Edge Services. Ability
to provision “white box” universal
customer premises equipment
(uCPE), with virtual networking
functions (VNFsTheir uCPE dashboard...According to im reading.
If the board has the Intel chip. You should be able to get the whole thing legally signed off for open source to use however you like Pfsense, free too imagine as far as Intels personal licensing cost is concerned. -
Um, no. This is nothing to do with SD-WAN etc. And most driver sources you find will be Linux.
What you would need here is specifically a FreeBSD igb driver that supports the NICs found in the C2K CPU but with the additional code to allow the MDIO bus driver.
This is the driver we ship: https://github.com/pfsense/FreeBSD-src/tree/RELENG_2_4_5/sys/dev/e1000
That can be compiled against FreeBSD 11.3/4 to produce a kernel module that can be loaded into pfSense in preference to the in-kernel driver.
If there is a patch set out there somewhere that can be applied to allow the mdio interface that could work but I've never found one.If you were doing this you should probably also start out using a 2.5 dev snapshot as the FreeBSD 12 drivers are significantly different to 11.
Steve
-
@stephenw10 thank you sir. I'll stay OT with pfsense in mind for sure. I do have the network gateway box the OP started up this project for this is such a nifty piece of hardware, it would make one hell of a little development server for a home IoT lab.
If there's anything I can do to upload from hardware let me know. But I think at this point vmware should have the entire device code virtually available to tool with on their cloud api dashboard no?P.S.
Glad I you are active on this, thought I was going to get lost here:https://github.com/search?o=desc&q=bios+intel&s=stars&type=Repositories -
VMware may have opensourced some of it. But the boot output we had previously looked like it was running OpenWRT anyway. So that code may already be available. It doesn't help is much in FreeBSD though as it Linux based, unless you're able to port that.
Steve
-
I cannot get the USB to show as a COM for connection, how did you guys get this to happen?
-
I don't have one of these but what does it show up as?
How are you trying?
-
@stephenw10 looking at the picture above posted before I tried USB B to USB B, I also tried USB B to USB C.
I can do normal SSH but the command to flash to the other image is normally in the start up process. Not sure if I know of a way to do it via SSH and not "console" a bit out of my skill level.
-
As I say I don't have one to test but I assume the serial console is the port on the side which I expect to be mini-USB B but I can't see that closely in the pictures. Exactly like most of our own hardware is.
Steve
-
@stephenw10 There is no console port on the unit, usb rj45 or anything, just USB marked ports, REJ45 and SFP.
-
In the photo above there is a cable connected to a port on the side. That looks like it's the console. It might be an internal port with no hole in the case....
-
@stephenw10 Good eye!!! the blue on the bottom right got me. I did not see the black one on the left, I see it on the MB also now.
-
@ryno5514 Got it loaded.
The unit has 6 ETH Ports and looks like the "LAN" ports are Intel pro100 each has its own mac. However, I cannot get any other ports but #4 to show
Network interface mismatch -- Running interface assignment option.
Valid interfaces are:
igb0 f0:8e:dbXXXX (down) Intel(R) PRO/1000 Network Connection, Version
Do VLANs need to be set up first?
If VLANs will not be used, or only for optional interfaces, it is typical to
say no here and use the webConfigurator to configure VLANs later, if required.Should VLANs be set up now [y|n]?
-
Yes, that's expected with the default igb driver. It fails to attach to three of the NICs there probably because it doesn't recognisce the connected PHY.
Steve
-
@ryno5514 This is from the official device manual, maybe something useful in there to help your PFSense on velocloud edge500 build.
https://docs.vmware.com/en/VMware-SD-WAN/3.3/velocloud-admin-guide-33/GUID-325E1415-EF99-4B22-902F-DA64CD5D8473.html
-
That is a link to 'Enable SR-IOV on KVM'. It seems completely unrelated.
I doubt they would ever put up an actual service manual.
Steve
-
@stephenw10 I just loaded 2.5
freebsd-version
12.2-STABLEStill has the same issue so going to tinker a little more
-
@ryno5514 said in What is this board??? Help!:
@stephenw10 I just loaded 2.5
freebsd-version
12.2-STABLEStill has the same issue so going to tinker a little more
Tried the following also
cat /boot/loader.conf
kern.cam.boot_delay=10000
kern.ipc.nmbclusters="1000000"
kern.ipc.nmbjumbop="524288"
kern.ipc.nmbjumbo9="524288"
boot_multicons="YES"
boot_serial="YES"
console="comconsole,vidconsole"
comconsole_speed="115200"
autoboot_delay="3"
hw.hn.vf_transparent="0"
hw.hn.use_if_start="1"
legal.intel_iwi.license_ack=1
legal.intel_ipw.license_ack=1
net.link.ifqmaxlen=2048
net.isr.defaultqlimit=2048
net.inet.tcp.soreceive_stream=1
net.inet.tcp.syncache.hashsize=1024
net.inet.tcp.syncache.bucketlimit=100
net.pf.source_nodes_hashsize=1048576echo "dev.igb.0.enable_lro=0" >>/etc/sysctl.conf
echo "dev.igb.1.enable_lro=0" >>/etc/sysctl.conf
echo "dev.igb.2.enable_lro=0" >>/etc/sysctl.conf
echo "dev.igb.3.enable_lro=0" >>/etc/sysctl.conf -
I purchased a mSATA-PCIe-Mini-VGA-Adapter-Cable..
Plugged it into the Msata port on the bottom of the device.. put a vga wire to screen plugged in router hit keyboard button f12, enter, f2, Q, F and escape i belive..https://www.ebay.com/itm/IEI-Add-on-Video-Graphic-Card-IGCME-1300-R10-mSATA-PCIe-Mini-VGA-Adapter-Cable/353020687468
Ive gotten visual display to show bios options on monitor! I'll update any thing else. But yes, VGA from Msata is working on bottom pcie port.
-
@bubbadestroy said in What is this board??? Help!:
Ive gotten visual display to show bios options on monitor! I'll update any thing else. But yes, VGA from Msata is working on bottom pcie port.
Thats a great find, I might pull the Wifi off and do that myself. I am going to put an LTE radio for the other slot but having video out would be nice.
Still trying to get this driver to work myself.
-
Interesting. Are there any options for the NICs or switch?
-
I think this is what you're asking
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xf0a0-0xf0bf mem 0xdfe60000-0xdfe7ffff,0xdff2c000-0xdff2ffff irq 20 at device 20.0 on pci0
igb0: Setup of Shared code failed, error -2
igb0: IFDI_ATTACH_PRE failed 6
device_attach: igb0 attach returned 6
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xf080-0xf09f mem 0xdfe40000-0xdfe5ffff,0xdff28000-0xdff2bfff irq 21 at device 20.1 on pci0
igb0: Setup of Shared code failed, error -2
igb0: IFDI_ATTACH_PRE failed 6
device_attach: igb0 attach returned 6
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xf060-0xf07f mem 0xdfe20000-0xdfe3ffff,0xdff24000-0xdff27fff irq 22 at device 20.2 on pci0
igb0: Setup of Shared code failed, error -2
igb0: IFDI_ATTACH_PRE failed 6
device_attach: igb0 attach returned 6
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xf040-0xf05f mem 0xdfe00000-0xdfe1ffff,0xdff20000-0xdff23fff irq 23 at device 20.3 on pci0
igb0: Using 1024 TX descriptors and 1024 RX descriptors
igb0: Using 2 RX queues 2 TX queues
igb0: Using MSI-X interrupts with 3 vectors
igb0: Ethernet address: f0:8e:db
igb0: netmap queues/slots: TX 2/1024, RX 2/1024 -
TLDR: C.E. USB bootable PFSense totally loads (in second USB port for me) and displays with that mpcie vga adapter plugged in to a vga monitor.
That particular seller accepted an offer of
ITEM PRICE:US $20.00Other things I wondered was maybe a displaylink, but for sure that mpcie card work ed out well. I ended up relocating the mpcie vga adapter card top of the box.. carved a portal for the wire to stick out of in the roof of chassis housing... then relocated the wifi card that is in the primary slot to the secondary slot on the bottom (above the ami flash memory) . It reaches just-so without rewiring or modding.
So far, on the edge500 at least, it seems the AMI bios picks it up just fine when using a boot-able USB ISO image of any type (Linux 2.6 around about or above i assume)
Whatever image that would have normally been natively boot-able on a machine for Intel atom c2000-3000 | AMI Bios compatible... seems to load with display adapter in either mpcie slot... however, I think having serial usb in has craused it to halt the boot order due to default bios settings.. I could use a hand optimizing the bios settings for atom.
Photos to come sooner or later if interested.
-
@ryno5514 said in What is this board??? Help!:
@stephenw10
I think this is what you're askingI meant in the BIOS. We already know the igb driver will not attach to the NICs in the default setup but it might have something you could set there to change that.
It probably won't though based on other devices users have looked at.Steve
)