I have problem with network in buildroot on my VirtualMachine. When i typing ifconfig i get answer:
eth0: error fetching interface information: Device not found
While loading buildroot on console i see:
ip: can't find device eth0
ip: SI0CGIFFALGS :No such device
I cant`t find the way resolve this problem.
# make linux-menuconfig
Device drivers —>
Network device support —>
Ethernet driver support—>
Select:
<*> Intel(R) PRO/100+ support
<*> Intel(R) PRO/1000 Gigabit Ethernet support
<*> Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support
<*> Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support
[*] Intel(R) PCI-Express Gigabit adapters HWMON support
<*> Intel(R) 82576 Virtual Function Ethernet support
And should work now with VM.
Your problem is not a Buildroot problem, but a kernel configuration problem.
From the last line in the boot log, you might add Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support as #TadejP mentioned.
[ 0.204512] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[ 0.205444] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 0.220165] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[ 0.362077] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[ 0.362908] ata1.00: 4280320 sectors, multi 16: LBA48
[ 0.364110] ata2.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[ 0.365246] ata2.00: configured for MWDMA2
[ 0.366176] ata1.00: configured for MWDMA2
[ 0.366846] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 0.368118] sd 0:0:0:0: [sda] 4280320 512-byte logical blocks: (2.19 GB/2.04 GiB)
[ 0.369219] sd 0:0:0:0: [sda] Write Protect is off
[ 0.369916] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.371218] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 0.372213] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5
[ 0.387384] sda: sda1 sda2 sda3
[ 0.388409] sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 0.389298] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 0.390163] sd 0:0:0:0: [sda] Attached SCSI disk
[ 0.390976] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 0.548201] e1000 0000:00:03.0 eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56
[ 0.549265] e1000 0000:00:03.0 eth0: Intel(R) PRO/1000 Network Connection
Related
I'm getting the following error on serial output (verbose mode) when my smart device , ESP32 S3 tries to connect over WIFI to the Access point (AP). The SSID is TheScientist
Below is the serial output:
Connecting to TheScientist
[ 1064][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 0 - WIFI_READY
[ 1098][V][WiFiGeneric.cpp:338] _arduino_event_cb(): STA Started
[ 1099][V][WiFiGeneric.cpp:97] set_esp_interface_ip(): Configuring Station static IP: 0.0.0.0, MASK: 0.0.0.0, GW: 0.0.0.0
[ 1099][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 2 - STA_START
.......[ 4750][V][WiFiGeneric.cpp:360] _arduino_event_cb(): STA Disconnected: SSID: TheScientist, BSSID: 3c:cd:5d:a7:f1:13, Reason: 15
[ 4750][D][WiFiGeneric.cpp:929] _eventCallback(): Arduino Event: 5 - STA_DISCONNECTED
[ 4758][W][WiFiGeneric.cpp:950] _eventCallback(): Reason: 15 - 4WAY_HANDSHAKE_TIMEOUT
Although the verbose debug serial output shows a
Reason: 15 - 4WAY_HANDSHAKE_TIMEOUT
in reality the timeout is due to usage of a password longer than the 32 char allowed on ESP32 MCUs . In summary, any ESP32 MCU to successfully connect to any WIFI Access Point , the Network password must not exceed 32 char long.
I have a problem with hotplug ethernet in an embedded Linux (ver 3.6.0-rc5).
If the network cable is connected during boot everything works fine.
But if I connect the cable after boot I do not get an IP address.
My /etc/interfaces look like this:
# The loopback interface
auto lo
iface lo inet loopback
# Wired or wireless interfaces
allow-hotplug eth0
iface eth0 inet dhcp
My startup script includes this command:
ifup eth0
If the ethernet cable is connected at boot I get this after calling 'ifup eth0':
[ 10.257995] davinci_mdio davinci_mdio.0: resetting idled controller
[ 10.265319] net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=davinci_mdio-0:00, id=7c0f1)
udhcpc (v1.19.4) started
Sending discover...
[ 12.261260] libphy: davinci_mdio-0:00 - Link is Up - 100/Full
Sending discover...
Sending select for 192.168.86.100...
Lease of 192.168.86.100 obtained, lease time 86400
adding dns 192.168.86.1
If the ethernet cable is not connected at boot I get this after calling 'ifup eth0':
[ 10.230285] davinci_mdio davinci_mdio.0: resetting idled controller
[ 10.238037] net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=davinci_mdio-0:00, id=7c0f1)
udhcpc (v1.19.4) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
If I then connect the ethernet cable I get this:
[ 346.232391] libphy: davinci_mdio-0:00 - Link is Up - 100/Full
But I do not get an IP address.
So, it appears that Linux knows that the cable got connected, but it doesn't automatically ask for an IP address.
Note: If I do not call ifup during boot then nothing happens when I connect the ethetnet cable.
When the cable is connected I can get an IP address by doing this:
ifdown eth0
ifup eth0
Do I have to tell Linux to look for an address (e.g. ifdown/ifup)?
And if so: how do I do that?
My computer has a Windows 10 and I was following through Microsoft 98-366 Network Fundamentals book.
It had me to open Windows Powershell and type
New-NetIPAddress -InterfaceAlias "Local Area Network" -IPv4Address 192.168.1.101 -PrefixLength "24" -DefaultGateway 192.168.1.1
Then I got the error that it can't find a parameter with the name IPv4Address. It'ns not a typo though, because above was directly copied from the book.
So when I looked up the documentations on New-NetIPAddress it seemed -IPv4Address is not an option and instead I have to use IPAddress. So I tried the below
New-NetIPAddress -InterfaceAlias "Local Area Network" -IPAddress 192.168.1.101 -PrefixLength "24" -DefaultGateway 192.168.1.1
Then I got a new error saying
New-NetIPAddress : Invalid parameter InterfaceAlias Local Area Network
but InterfaceAlias does exist in the documentations, so I'm not sure what causes it to be invalid.
Thanks in advance for any kind of help.
Additionally, the documentation I looked up was this:
Net-NetIPAddress
I think the InterfaceAlias is not valid.
First look at all the network interfaces using the command Get-NetIPInterface. Here is the output in my PC:
InterfaceAlias
--------------
vEthernet (Wi-Fi)
vEthernet (VMware Network ) 2
vEthernet (VMware Network )
vEthernet (VirtualBox Host)
vEthernet (Ethernet)
VMware Network Adapter VMnet8
VMware Network Adapter VMnet1
VirtualBox Host-Only Network
Local Area Connection* 10
Local Area Connection* 9
Ethernet
Wi-Fi
Loopback Pseudo-Interface 1
vEthernet (Wi-Fi)
vEthernet (VMware Network ) 2
vEthernet (VMware Network )
vEthernet (VirtualBox Host)
vEthernet (Ethernet)
VMware Network Adapter VMnet8
VMware Network Adapter VMnet1
VirtualBox Host-Only Network
Local Area Connection* 10
Local Area Connection* 9
Ethernet
Wi-Fi
Loopback Pseudo-Interface 1
Re-check by reading all properties with Get-NetIPInterface | Format-List * will help you identify which is the correct network interface you are looking for.
During testing network, I'm facing a very low throughput with gigabit Ethernet, which was implemented as RGMII mode, as follows:
$iperf - s
Interval Transfer Bandwidth
0.0-10.0 sec 211 MBytes 176 Mbits/sec
$iperf - c <IP>
Interval Transfer Bandwidth
0.0-10.0 sec 101 MBytes 83.6 Mbits/sec
I'm just a beginner with network on Linux then could anyone guide me some direction to debug and fix this issue?
The only thing I tried so far is that reading ethtool. There is nothing wrong observe here.
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 2
Transceiver: external
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes
I'm using vagrant 1.7.4 on Mac OSX El Capitan 10.11.1. I configured public network like below.
config.vm.network "public_network", :bridge => 'en0: Wi-Fi (AirPort)', ip:"192.168.18.31"
But I found it doesn't works on my mac but work on PC. I'm using virtual box 5.0.8 r103449. Also I turned off firewall too.
Does the host network interface you want to route through exist on eth0? Running ifconfig on my Mac OS shows an adapter name matching pattern en0.
You can use multiple interfaces in the bridge parameter if you would like to attempt to use many:
bridge: [
"en1: Wi-Fi (AirPort)",
"eth0: Broadcom NetXtreme Gigabit Ethernet Controller",
]
The first network adapter that exists and can successfully be bridge will be used.