How do I configure my x86_64 HW to connect to the internet? Default IP, 192.168.1.1 doesn't come up when I ping from any port on the HW. Do I need to manually configure ethernet/optical ports? Either ports are functional, I have or tried an optical/ethernet SFP+ adapter too.
I've successfully booted up on NVME SSD image file, Combined-EFI (EXT4), on this mini PC, CWWK Intel Alder Lake N100. Has 16G RAM, 256Gb NVME SSD.
I'm switching to x86 to support higher speeds from my ISP.
Post the network config (/etc/config/network).
It is likely only a single port is configured for LAN by default.
Probably defaulted to eth0 as LAN, and eth1 as WAN
i had the same topic on my cwwk n100 with 6 intel lans.
i connected a monitor/keyboard to it, added all ports to the bridge except the wan and configured the rest via luci when i was able to connect via lan.
Only eth0 is on LAN.
If it’s not possible to tell externally (or by just trying them all), add all ports to the br-lan device
list ports ‘eth2’
list ports ‘eth3’
Etc
Eth1 is WAN.
Luci doesn't come up on Eth0. I'll need CLI commands spelled out help. Ping is unsuccessful on default IP.
Does ifconfig eth0 from the console show anything (i.e., the MAC address of the interface, Tx or Rx traffic, assigned IP, etc.)?
When you plug a computer into the ports on the x86 router, does any one of the ports result in a successful DHCP lease being issued to the computer?
I’ve never dealt with SFP modules but my understanding is they show up as ethX interfaces.
My assumption is that dhcp works on a brand new install, so maybe the lan is up but bound to an SFP slot.
Find a list of how many eth interfaces you have
cat /proc/net/dev | grep eth
For each one listed, add it to the lan bridge
uci add_list network.@device[0].ports=ethX
Where X is the eth identifier found in the list.
Repeat this for everything except eth0 (already on lan) and eth1 (as that is already set for WAN and we will leave it alone for now).
uci commit
/etc/init.d/network restart
This should add all (except for 1) port to your LAN. Try pinging on different ports now and see if you can get in.
Here's the ifconfig eth0 response. List of ethernet devices comes up 0 is what is appears from this response show in the screen shot.
My remote PC is sent to same subnet (static address) as OpenWRT (192.168.1.1). The router is not using DHCP yet from what I can tell.
I'll go ahead and try your commands (lantis1008) and report back the result.
ifconfig is deprecated, use ip link show instead.
You are looking for the status to be both UP and LOWER_UP. UP means that the port is enabled. LOWER_UP on an eth port means that a live cable is plugged in, i.e. the signal carrier is on. You can identify which port on the box has which kernel name by plugging a cable into them one at a time and checking the status again. These names may not match the manufacturer's label on the box but it will be consistent through reboots.
Now I need for the WAN to work with the SFP+ modules (see the link is below) to work with eth0 and eth1.
Your uci command was successful, I now have access to eth2, eth3, eth4 and eth5.
(Off topic btw, but the enclosure printed HW is labelled respectively in this order eth0, eth1, eth2, eth3). Software (Openwrt) labels them eth2, eth3, eth4, eth5 respectively). So this tells me that eth0 is HW label "SFP+1" and eth1 is "SFP+2". WTSFOPTC SFP+ module should support 1.25Gbps up to 10Gbps. I have a 1Gbps network adapter.
When I connect my 1Gbps cable from the PC to the SFP+ module it doesn't light up. Looks like need a compatible SFP+ adapter although several on Amazon has successfully used 1Gbps connection.
OK, later on, I realized I have a network switch that supports 1G, 2.5G, 5G 10G and that supports these SFP+ transceivers. Connected a ethernet between the two transceivers I mentioned and WAN (aka labelled SFP+2) connected to the internet now.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
