date int64 1,220B 1,719B | question_description stringlengths 28 29.9k | accepted_answer stringlengths 12 26.4k | question_title stringlengths 14 159 |
|---|---|---|---|
1,655,319,444,000 |
I have openSUSE 11.4 installed on my HP pavilion dm4-2015dx.
The ethernet card (Attansic ethernet controler is shown in Yast's hardware info) was not recognized and after many days of googleing i found similar problem that has been solved. I tried to do what is described on ubuntu forum but it didn't work for me. Although I finally have eth0 - but connection cant be established.
Next thing I tried to enable Tumbleweed repository and update to kernel 3.0 (which could have drivers). Short after updating kernel I had two eth devices, but only one was activated when plugged in LAN cable. Still couldn't connect.
After rebooting there is only one eth device - but not sure which one.
How can I "uninstall" drivers from ubuntu forum? Or did Kernel override them?
Any other suggestion on how to solve my problem is more than welcome!
Thanks
|
After couple of updates I'm able to connect with ethernet card!
It seems that Kernel 3.0. solved that issue after all... Or maybe 3.0.1.
You just need to be persistent :)
| Atheros ethernet driver |
1,655,319,444,000 |
I'm using 3 NetworkManager connection profiles in a Linux distribution and all the connection profiles refer to the same ethernet interface: enp3s0. I'm using these connections to manage:
the default static IP configuration
set a new static IP configuration
request a DHCP address
In the rest of the question I'll use the term connection to mean the term connection profile.
To change Ethernet configuration I change the priority of the connection, so if I would like to enable the default static IP configuration I set a priority for that greater than static IP configuration and DHCP configuration.
Read the paragraph "Set properties of the 3 connections" in the continuation of the question to get details about setting of priority of a connection.
The question
If I create connections at boot by a bash script started by a systemd service all works correctly, but if I execute the bash script after the boot has finished, the IP configuration is not correctly managed by NetworkManager and its connection profiles.
Go to the paragraph "The problem" at the end of the question to get a detailed description of the error.
The rest of the question give all details needed to understand the problem.
I apologize for the length of the question but there is a lot of information needed.
Creation of 3 NetworkManager connection profiles
To create the connections I'm using the command nmcli as showed below:
# for default static
nmcli c add ifname enp3s0 type ethernet con-name ethernet_default_ipstatic
# for ethernet_ipstatic
nmcli c add ifname enp3s0 type ethernet con-name ethernet_ipstatic
# for ethernet_dhcp
nmcli c add ifname enp3s0 type ethernet con-name ethernet_dhcp
After the execution of previous commands in the path /etc/NetworkManager/system-connections, there will be present 3 files called:
ethernet_default_ipstatic.nmconnection
ethernet_ipstatic.nmconnection
ethernet_dhcp.nmconnection
Set properties of the 3 connections
Previous commands create 3 connections with default properties, so after creating them it is necessary to set their properties. For this goal I still used the command nmcli as showed below.
For the ethernet_default_ipstatic set the following properties for the connection:
nmcli con mod ethernet_default_ipstatic ipv4.method manual ipv4.addresses 192.168.1.1/24 ipv6.method disabled
Previous command set the following properties for the connection:
ipv4.method = manual (this set IP Static and not DHCP)
ip address 192.168.1.1, netmask 255.255.255.0 (no gateway)
IPV6 disabled
the autoconnection propriety remains to default yes
the priority property remains to default 0
For the ethernet_ipstatic the properties are:
nmcli con mod ethernet_ipstatic ipv4.method manual ipv4.addresses 192.168.1.1/24 ipv4.gateway 192.168.1.100 ipv4.may-fail no ipv6.method disabled connection.autoconnect no connection.autoconnect-priority -1
Previous command set the following properties for the connection:
ipv4.method = manual (this set IP Static and not DHCP)
ip address 192.168.1.1, netmask 255.255.255.0, gateway 192.168.1.100
IPV6 disabled, autoconnection no, priority -1
For the ethernet_dhcp the properties are:
nmcli con mod ethernet_dhcp ipv4.method auto ipv4.addresses '' ipv4.gateway '' ipv4.may-fail no ipv4.dhcp-timeout 20 ipv6.method disabled connection.autoconnect no connection.autoconnect-priority -1 connection.autoconnect-retries 3
Previous command set the following properties for the connection:
ipv4.method = auto (this set DHCP and not Static IP Address)
ip address '', gateway ''
IPV6 disabled, autoconnection no, priority -1
Default configuration
By previous commands the connection ethernet_default_ipstatic has a priority > than others so the ethernet interface enp3s0 is configured with an IP static 192.168.1.1/24.
Execution of nmcli commands by a service
All work correctly If I execute previous nmcli commands at boot by the following service (my_custom_nm_service.service):
[Unit]
Description=Init NetworkManager Ethernet Connections
Requires=NetworkManager.service
After=NetworkManager.service
Before=network.target
[Service]
Type=oneshot
ExecStart=/home/<username>/script_services/init_connections.sh
User=<username>
[Install]
WantedBy=multi-user.target
where init_connections.sh executes previous nmcli commands.
Note. In the unit file note the presence of the opsions:
Requires=NetworkManager.service
After=NetworkManager.service
Before=network.target
The problem
If after the boot has finished I remove all connections, by the command nmcli con del, and I execute the script init_connections.sh I obtain a unpredictable IP configuration for the system.
The typical misconfiguration that occurs is as follows:
the active connection (showed by nmcli con command) is ethernet_default_ipstatic so the system should have the static IP address 192.168.1.1/24
but the system has obtained an IP address by the DHCP server
When the script init_connections.sh is executed by the service, it is executed before network.target, but honestly I don't know if this difference could be important to understand the problem or not.
|
I have found the problem: to set correctly the default configuration I need to execute the nmcli con up command as showed below:
nmcli con up "ethernet_default_ipstatic" iface enp3s0
as also indicated in this post.
Note. In this moment for me is not important to know why the execution of the script init_connections.sh works well at boot by the service my_custom_nm_service.service. My real interest is to make working the script at the end of the boot process.
For completeness I write the steps of my test.
1) remove the service
I have disabled the service my_custom_nm_service.service which started the execution of the script init_connections.sh
2) delete all connections
After the boot has finished I have deleted all the connection by the following script (delete_connections.sh):
nmcli c del ethernet_default_ipstatic
nmcli c del ethernet_ipstatic
nmcli c del ethernet_dhcp
3) creation of the 3 connections: the malfunction appears
Execute the script init_connections.sh:
nmcli con add ifname enp3s0 type ethernet con-name ethernet_default_ipstatic
nmcli con mod ethernet_default_ipstatic ipv4.method manual ipv4.addresses 192.168.1.1/24 ipv6.method disabled
nmcli con add ifname enp3s0 type ethernet con-name ethernet_ipstatic
nmcli con mod ethernet_ipstatic ipv4.method manual ipv4.addresses 192.168.1.1/24 ipv4.gateway 192.168.1.100 ipv4.may-fail no ipv6.method disabled connection.autoconnect no connection.autoconnect-priority -1
nmcli con add ifname enp3s0 type ethernet con-name ethernet_dhcp
nmcli con mod ethernet_dhcp ipv4.method auto ipv4.addresses '' ipv4.gateway '' ipv4.may-fail no ipv4.dhcp-timeout 20 ipv6.method disabled connection.autoconnect no connection.autoconnect-priority -1 connection.autoconnect-retries 3
After the execution of the script, my Linux system, presents the problem described in the question that is:
nmcli con command tells that the active connection is ethernet_default_ipstatic (because it has the greater priority)
the IP address has been assigned by the DHCP Server
4) solution: execute nmcli con up
The solution is execute the command:
nmcli con up "ethernet_default_ipstatic" iface enp3s0
and after that the interface enp3s0 has the default IP address
| Multiple NetworkManager connection profiles for the same ethernet interface not always work correctly |
1,655,319,444,000 |
I am using tc to change the MAC address of incoming packets on a TAP interface (tap0) as follows where mac_org is the MAC address of a guest in a QEMU virtual machine and mac_new is a different MAC address that mac_org should be replaced with.
tc qdisc add dev tap0 ingress handle ffff:
tc filter add dev tap0 protocol ip parent ffff: \
flower src_mac ${mac_org} \
action pedit ex munge eth src set ${mac_new} pipe \
action csum ip pipe \
action xt -j LOG
I also add an iptables rule to log UDP packets on the input hook.
iptables -A INPUT -p udp -j LOG
syslog shows that indeed the DHCP discover packet is changed accordingly. The tc log entry looks as follows:
IN=tap0 OUT= MAC=ff:ff:ff:ff:ff:ff:${mac_new}:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=338 TOS=0x00 PREC=0xC0 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=318
and the log entry of the netfilter input hook which follows the tc ingress hook as the locally incoming packet is passed towards the socket shows the same result slightly differently formatted.
IN=tap0 OUT= MACSRC=${mac_new} MACDST=ff:ff:ff:ff:ff:ff MACPROTO=0800 SRC=0.0.0.0 DST=255.255.255.255 LEN=338 TOS=0x00 PREC=0xC0 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=318
Before starting QEMU I run dnsmasq on tap0 which surprisingly shows the output:
DHCPDISCOVER(tap0) ${mac_org}
Running strace -f -x -s 10000 -e trace=network dnsmasq ... shows a recvmsg call that contains ${mac_org} instead of ${mac_new}.
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(68), sin_addr=inet_addr("0.0.0.0")}, msg_namelen=16, msg_iov=[{iov_base="... ${mac_org} ..." ...
How can that happen? It almost appears as if the packet is altered after the netfilter input hook.
|
My understanding is that you are confusing the Ethernet address that you modify with tc (link layer only), with the inner CHADDR field (client's hardware address) that was embedded by the client inside the DHCPDISCOVER request (application layer which won't ever be altered by tc).
| MAC address rewriting using tc |
1,655,319,444,000 |
I am having some issues with a DP83826 PHY and therefore I want to read some configuration registers. I have used mdio-tool and mii-diag for it, but I just realized that I can only read the first 32 registers.
mii-diag -v (verbose) displays the first 32 registers (which might not be a coincidence) and if I use mdio-tool with an address beyond 0x1F, the address gets shifted to stay within the 0..1F range. I had a look at the code of mdio-tool and it does not limit the register address at all and I also hacked mii-diag -v a bit to get more than 32 registers and it also returns the first 32 registers again and again. So it seems that the limitation is somewhere else, but I have still not found where. I am now trying to find out if the API or the device driver is causing this issue.
I have also tried ethtool -d eth0 but it only dumps the GMAC and DMA registers.
How to read/writte PHY MII registers beyond 0x1F in Linux?
|
I figured out how it works:
The basic standard MDIO address consists of 5 bits and therefore only the [0..32] range can be accessed directly. For devices that offer additional registers beyond the basic standard, there is an MDIO
Manageable Device (MMD) indirect method (defined in IEEE 802.3ah draft for Clause 22) for accessing the extended register set.
In the end that is nothing else as an indirect access through a couple of registers in the base range. In my particular case (and as pointed by @Murray Jensen), REGCR (0x0D) and ADDAR (0x0E) are used for that purpose. The addresses and the bit fields within the registers may (and probably will) vary from one chip to another, but the mechanism should be rather similar.
| Reading PHY MII registers beyond 0x1F |
1,655,319,444,000 |
How can I activate an Ethernet adapter which is visible in lspci but otherwise not exposed?
Messing around, I recently moved an SSD with a Fedora install from one computer to another. Without changing anything, most everything is working quite adequately-- it is great how flexible things were! However, while I can see the network interface hardware on the new computer with lspci, I cannot see it in ifconfig.
The only interfaces I have available are the loopback and a "bridge" interface. The card is not disabled in BIOS and was working to PXE boot previously. I tried manually adding it via ifcfgs generated by nmtui including adding MACADDR/HWADDR fields to those, but with those in place, systemctl would fail to restart networkmanager.
Edit: In front of the system again. Strangely, when I boot with a USB NIC attached to get around this issue, it is not enumerated in ifconfig unless I unplug/re-plug. I am able to in BIOS specify the passthrough MAC to be the NIC1 MAC, so I have the same MAC on the USB Ethernet adapter. This doesn't solve the root issue, which I am still trying to solve.
|
According to your lspci -vvv output Ethernet controller: Intel Corporation Ethernet Connection (11) I219-LM has no kernel driver in use. The kernel you have seemingly doesn't support your HW. You're running the latest released kernel for RHEL 7 which might still be too old.
You've got two options:
Installing kernel 5.17.5 (this one will definitely work) or RHEL 8's kernel (may or may not work - I'm too lazy to check RHEL 8 documentation, sorry). RHEL/Fedora based distros allow to install as many kernels as possible.
Installing the kernel-devel package and then compiling Intel's own driver.
| Ethernet adapter in "lspci" but not available in "nmtui" |
1,655,319,444,000 |
I'm trying to connect my computer to the internet via a new router, and it is refusing to work in the most baffling way I've ever encountered.
If I just connect to the wifi network in the normal way,
Computer --(Wifi)--> Router
then I can ping the router without problems. But I cannot ping 8.8.8.8:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
Needless to say, I also can't access any other websites.
If I instead use ethernet,
Computer --(Ethernet)--> Router
then things are exactly the same as (1), showing it's not a wifi issue.
I then connected two additional phones to the router, like this
Computer --(Wifi)--> Router
Phone 1 --(Wifi)--> Router
Phone 2 --(Wifi)--> Router
Both phones could access the internet fine, and all three devices could ping each other and the router, but the computer still couldn't access the internet.
I tried connecting the computer via USB tethering, using a phone as an intermediary:
Computer --(USB tethering)--> Phone --(Wifi)--> Router
The computer still couldn't connect to the internet. But note that when I switched the phone to mobile data,
Computer --(USB tethering)--> Phone --(Mobile Data)--> Mobile Network
things worked fine, which shows the tethering setup was not at fault.
Things I have tried
Using other routers (in the past). They have all worked.
I have ensured that the computer's wireless regulatory domain is set correctly.
Rebooting the router.
I am not allowed to reset the router.
Faking the computer's MAC address. This made no difference, except when using ethernet, now I couldn't even connect to the router at all.
Using mtr. If I run mtr 8.8.8.8, I get
Host
1. _gateway
2. 10.12.0.1
3. (waiting for reply)
I recognise 10.12.0.1 as the address of the router. But it never gets any further than that, and certainly doesn't make it to dns.google.
Disabling TCP window scaling as suggested on the Arch Wiki. This was a complete shot in the dark. It also didn't work.
Running a Debian LiveUSB instead of Arch Linux.
Lowering the mtu from 1500 to 128. [added]
Other useful information [added]
The contents of /etc/resolv.conf:
# Generated by NetworkManager
nameserver 127.0.0.1
options edns0 trust-ad
The contents of NetworkManager.conf:
[main]
plugins=keyfile
dns=dnsmasq
dhcp=internal
The system log upon connecting via ethernet:
https://pastebin.com/rAQqjvmk
Summary
It seems this router has it in for my computer no matter what I do. Somehow it even recognises my computer when it's hiding behind my phone, with a fake MAC address, and with a fresh operating system. At this point, my best guess is that some hardware identifying information is somehow getting into the ping packets, and that something after the router is blacklisting it. So, the questions are the obvious ones:
What could be causing it not to work?
How do I make it work?
|
Thanks to the discussion in chat, I managed to solve my problem and learn some things too.
Cause
There are two nasty things going on here, both of them to do with a network switch lying between my router and the Internet:
Computer --> Router --> Switch --> Internet
The switch is blocking ping packets.
This means that tools like ping, traceroute, tracepath and mtr wouldn't work even if I could connect to the internet, so they are not useful as diagnostic tools in this case. Apparently, some adminstrators disable these tools for "security reasons", though in my case they just ended up sowing lots of confusion. Because I had never seen this in the wild before, or even heard of it being done, I didn't consider it as an option. The lesson to learn here is that you can't always rely on ping to be available.
Note that the router itself handles ping packets fine. This explains why I could ping any other device connected to the same router, but nothing else.
(Actually, this reasoning might be a bit too naïve. According to @Cbhihe in chat, the router could be doing the blocking after all. I haven't been able to tell, but the above picture is still a useful model for what's going wrong.)
By itself however, this isn't the cause of the problem. It merely frustrates attempts to investigate it. But given that the switch is evil in one way, it's probably evil in other ways too. This brings us to...
The local DHCP server wasn't communicating with my DHCP client properly.
Every computer needs a DHCP client so it can be assigned an IP address when it's connected to a network. Mine was NetworkManager's internal dhcp client, as evidenced by dhcp=internal in NetworkManager.conf. It turns out that this DHCP client is quite basic. Although it has always worked in the past, it didn't work with this DHCP server. The result was that the IP addressing information on my computer wasn't being set correctly.
I don't know exactly what wasn't set correctly. Certainly, my computer had received a valid IP address, as showed by ip addr, otherwise I couldn't have pinged it from my phone. But something else must have been wrong, because the switch was not appeased, and this caused it to drop all my IP packets.
Note that the loopback address 127.0.0.1 in /etc/resolv.conf is not at fault. It just reflects the fact I use dnsmasq for DNS caching, as evidenced by dns=dnsmasq in NetworkManager.conf. The idea is that dnsmasq listens on 127.0.0.1 for DNS requests, checks if they're in its cache, and if not forwards them to the real DNS server. I had turned this on a long time ago as a micro-optimisation. The real DNS server was set to a sensible value, so it seems DNS was not directly a factor here. I still couldn't communicate with the DNS server to resolve anything, but that was because of the problems already mentioned, not because it was set incorrectly.
Solution
The root of the problem is my DHCP client. I swapped it out for the more featureful dhclient instead, and things worked. I still could not ping, but I had internet access, which is what matters.
A better configuration
After some more configuration, I decided to swap out dnsmasq for the newer systemd-resolved, and things are still working. My NetworkManager.conf now reads
[main]
plugins=keyfile
dns=systemd-resolved # Not strictly necessary, but helpful to remind me
dhcp=dhclient
Of these, dhclient requires no setting up, while systemd-resolved requires
systemctl start systemd-resolved
systemctl enable systemd-resolved
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
| Router blocking one specific device |
1,655,319,444,000 |
Two os installed on my pc,today a strange thing happens:my ethernet device lost in debian!
Enter into win10 from grub, i can connect internet with pppoe.
Enter into debian10 from grub :
ifconfig
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 20 bytes 1120 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 1120 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sudo lshw -C network
*-network UNCLAIMED
description: Ethernet controller
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:06:00.0
version: 15
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list
configuration: latency=0
resources: ioport:f000(size=256) memory:fcd04000-fcd04fff memory:fcd00000-fcd03fff
I get the mac address info--xx:xx:70:c2:2c:4a from ipconfig /all in win10.
sudo pppoeconf xx:xx:70:c2:2c:4a
Cannot find device "xx:xx:70:c2:2c:4a"
ioctl(SIOCGIFHWADDR): No such device
Cannot find device "xx:xx:70:c2:2c:4a"
Plugin rp-pppoe.so loaded.
/usr/sbin/pppd: unknown host: nic-00
Download r8168-dkms_8.048.03-1~bpo10+1_all.deb with win10 into usb,and enter into debian10.
sudo mount /dev/sdc /mnt
sudo dpkg -i /mnt/r8168-dkms_8.048.03-1~bpo10+1_all.deb
After re-install it:
sudo pppoeconf xx:xx:70:c2:2c:4a
#input account name and password
sudo pon dsl-provier
plugin rp-pppoe.so load
/usr/sbin/pppd:unknown host nic-00
Just yesterday i can connect to internet with pppoe in debian10,how to fix then?
If Windows was hibernated it could have turn the card into the state when it is unusable in Debian. The solution could be to assure Windows was shut down, not hibernated.
@Nikita Kipriyanov ,i am sure that it is un-related with windows.
I installed a new debian10 with same version after the old debian10 can't recognize ethernet device ,now there are three oses in my pc instead of dual.
Enter into the new installed debian , i can connect internet with pppoeconf!That is to say, both win10 and new installed debian10 can connect with internet!Why my old debian10 can't recognize ethernet device!
I downloaded firmware-realtek_20190114-2_all.deb into usb in win10 and dpkg it in the old debian10,nothing changed!
All drivers show:
modinfo r8169
filename: /lib/modules/5.10.0-0.bpo.7-amd64/kernel/drivers/net/ethernet/realtek/r8169.ko
firmware: rtl_nic/rtl8125b-2.fw
firmware: rtl_nic/rtl8125a-3.fw
firmware: rtl_nic/rtl8107e-2.fw
firmware: rtl_nic/rtl8107e-1.fw
firmware: rtl_nic/rtl8168fp-3.fw
firmware: rtl_nic/rtl8168h-2.fw
firmware: rtl_nic/rtl8168h-1.fw
firmware: rtl_nic/rtl8168g-3.fw
firmware: rtl_nic/rtl8168g-2.fw
firmware: rtl_nic/rtl8106e-2.fw
firmware: rtl_nic/rtl8106e-1.fw
firmware: rtl_nic/rtl8411-2.fw
firmware: rtl_nic/rtl8411-1.fw
firmware: rtl_nic/rtl8402-1.fw
firmware: rtl_nic/rtl8168f-2.fw
firmware: rtl_nic/rtl8168f-1.fw
firmware: rtl_nic/rtl8105e-1.fw
firmware: rtl_nic/rtl8168e-3.fw
firmware: rtl_nic/rtl8168e-2.fw
firmware: rtl_nic/rtl8168e-1.fw
firmware: rtl_nic/rtl8168d-2.fw
firmware: rtl_nic/rtl8168d-1.fw
license: GPL
softdep: pre: realtek
description: RealTek RTL-8169 Gigabit Ethernet driver
ls /lib/firmware/rtl_nic
rtl8105e-1.fw rtl8107e-1.fw rtl8125b-2.fw rtl8168d-2.fw rtl8168e-3.fw rtl8168fp-3.fw rtl8168g-3.fw rtl8402-1.fw
rtl8106e-1.fw rtl8107e-2.fw rtl8153a-3.fw rtl8168e-1.fw rtl8168f-1.fw rtl8168g-1.fw rtl8168h-1.fw rtl8411-1.fw
rtl8106e-2.fw rtl8125a-3.fw rtl8168d-1.fw rtl8168e-2.fw rtl8168f-2.fw rtl8168g-2.fw rtl8168h-2.fw rtl8411-2.fw
No ethernet device such as enp*s*.
ifconfig -a
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 20 bytes 1120 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 1120 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
uname -a
Linux debian 5.10.0-0.bpo.7-amd64 #1 SMP Debian 5.10.40-1~bpo10+1 (2021-06-04) x86_64 GNU/Linux
|
The package r8168-dkms_8.048.03-1~bpo10+1_all.deb includes the file /etc/modprobe.d/r8168-dkms.conf, which will tell the kernel to load the r8168 module instead of the default r8169 for specific card models.
The package includes the r8168 module in source code form only: in order to make it usable, the dkms utility will be used by this package to automatically build the module for every kernel version you're using.
(here's the list of contents for that package)
But DKMS can only do its job if you have the compiler and the linux-headers package that matches your exact kernel version installed. Either you don't have the appropriate linux-headers package for your current kernel installed, or something has gone wrong when DKMS was trying to auto-build the r8168 module for you.
You should begin troubleshooting by verifying DKMS is in the proper state, by running sudo dkms status.
If the kernel module is properly built, the output of the dkms status command should include a line like this:
r8168, 8.048.03, <your current kernel version>, amd64: installed
The <your current kernel version> field should exactly match the output of uname -r.
The word installed at the end means the actual binary module has been successfully built and inserted into the current kernel's /lib/modules/$(uname -r)/... directory tree. Other possible status words are built which means the binary module has been successfully built but has not yet been made available to the kernel, and added which means the source code for the module has been installed but the binary module is not built yet.
You should verify that you have the appropriate linux-headers package installed, and then retry building the module by running:
sudo dkms install r8168/8.048.03
If it reports a problem, a more detailed log of the build process and any error messages encountered during it can be found at /var/lib/dkms/r8168/8.048.03/$(uname -r)/x86_64/log/make.log.
If you wish to try the default r8169 driver instead, you will need to uninstall the r8168-dkms_8.048.03-1~bpo10+1_all.deb package, or rename the /etc/modprobe.d/r8168-dkms.conf to e.g. /etc/modprobe.d/r8168-dkms.conf.disabled and run sudo update-initramfs -u to propagate the change into your current initramfs file too.
| My ethernet device lost in debian |
1,655,319,444,000 |
I've modified a kernel module (qcaspi) and recompiled it, however my modifications aren't being called (checked dmesg) when the OS boots up.
Instead, the old kernel module is being run.
If I reload the module with rmmod and modprobe then my changes DO get called.
What's going on there? Where is the OS finding the old module if I modified it and now have a new .ko file?
|
Thanks to the comments I was able to find a solution.
update-initramfs -v -u
This updates the archived kernel modules, the -v is for the verbose option.
Takes a few seconds but once done, I can restart my OS and my new driver gets called right away, instead of the older archived version :).
| Custom Kernel module not being loaded |
1,655,319,444,000 |
On my laptop, I often mount the content of my NAS through sshfs, for ease of access. I usually do so with an ethernet cable plugged in, as it makes browsing the files more smooth than with wifi. But sometime, I need to unplug, while still being connected to the same network through wifi. However, this makes sshfs unresponsive ; any attempt to access the content of the nas directory freezes until I either plug the Ethernet cable again, or kill sshfs, in which case I have to unmount, then mount again. The main issue is that unmounting requires me to close the half-dozen terminals that are already in the nas directory.
One solution would be to force sshfs to use the wifi connection even when connected to the ethernet. (ssh has an option for that, so I assume sshfs as well.) However, I would lose the benefit of smooth browsing, and some movies become entirely unwatchable.
So is there any method so that sshfs can use either wifi or ethernet depending on which is available, without having to unmount and remount ? (Or another command entirely that performs a similar function and does what I want.)
|
When you connect, use the -o reconnect flag:
$ sshfs -o reconnect [email protected]:/remote_path /local/path
| Keep sshfs connection when switching from wired to wireless network |
1,655,319,444,000 |
My oldish desktop PC, running stable Debian, won't connect to LAN anymore. Since other computers in the same network don't have this problem (even using the same cable) I strongly suspect a hardware problem with the onboard ethernet port (I recently plugged in another computer using the same cable, maybe i simply broke a pin when plugging the cable back in). Before I rush out and buy an ethernet card, what can I do to diagnose the problem with the software tools my operating system offers
|
Desktop network cards almost always have a LED to indicate connection (and often a second one tracking data I/O).
If there is no LED, then try plugging the cable out and in again, and run dmesg to see whether anything happens, for example:
[248510.165619] e1000: eth0 NIC Link is Down
[248510.168904] e1000 0000:00:03.0 eth0: Reset adapter
[248512.277754] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
If there is a LED and it stays off, and/or no activity is detected by the kernel, then the network card is either broken or seriously borked. I had this happen once, but long ago, because I had installed the wrong driver - I think a 8139A instead of something else or vice versa. But even then, it was apparent in the syslog (it said something like, "eth0: 8139too blah blah: No so-and-so chip was found")
Also check the output of lspci. It should say something apropos an Ethernet controller:
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
This is a newer (still a bit long in the tooth) Dell machine:
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5722 Gigabit Ethernet PCI Express
03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 21)
If you don't see any Ethernet controllers, then the card has been unseated, or is seriously broken. A bent or oxidised pin would result in lspci seeing a card, a lot of complaints in /var/log/syslog and dmesg, and no connection.
| No LAN-connection - how to diagnose possible hardware problem |
1,655,319,444,000 |
I want to set the network speed so I created a script in /etc/network/if-pre-up.d/eth-tool:
#!/bin/sh
ethtool eth0 -s speed 10 duplex full autoneg off
I set the execution permission, but on boot the network still work at 100 Mbps. I have a file inside /etc/systemd/network/20-eth0.network with this content:
[Match]
Name=eth0
[Network]
DNS=192.168.0.1
Address=192.168.0.100/24
Gateway=192.168.0.1
Can I set here the network speed?
|
Create a systemd unit file for setting the speed automatically. The .service file would be something like
[Unit]
Description=Setting Speed
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/bin/ethtool -s eth0 speed 10 duplex full autoneg off
Type=oneshot
[Install]
WantedBy=multi-user.target
if-pre-up.d should also work, bu you mentioned ~/etc which I assume is a typo. It should be /etc/network/if-pre-up.d/ethtool
Also, include the full pathname of your command /sbin/ethtool
Finally, test the ethtool from command line and make sure it switches the speed without any issue before trying it from the script because it might not be a problem with your script but with the driver or card or anything.
| ethtool doesn't change the network speed in pre-up |
1,655,319,444,000 |
I'm running an Ubuntu PC with 2 network cards:
An external USB to ethernet card, eth1
Built in ethernet NIC, eth0
I have eth1 assigned a static IP from the admin and intend to use it as the interface for WAN/internet connectivity. As for eth0, it is a workaround for a server with a fixed IP and ethernet address, configured through /etc/network/interfaces as shown:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 122.128.0.7
netmask 255.255.255.0
hwaddress ether 00:10:13:50:a3:77
The problem with the above is that even though it does bring up the interface, it is inconsistent and fails to get network connectivity every now and then. ifconfig doesn't show any IPv4 address either! The PC requires a reboot, sometimes multiple times, to get an IPv4 address.
How can I fix this so that eth1 is used to get an IPv4 address consistently (as long as the network is not down)?
|
After reading quite a bit on the internet, I came up with the following solution:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet dhcp
auto eth0
iface eth0 inet static
address 122.128.0.7
netmask 255.255.255.0
hwaddress ether 00:10:13:50:a3:77
What this does is essentially forcing the interface eth1 to get an IPv4 address through DHCP explicitly so that the DHCP server knows it is the eth1 that needs to be mapped.
| Use and set a default ethernet card for external network/internet (WAN) access |
1,553,393,811,000 |
I have a Linux box (Debian 9) with 2 NICs (Ethernet & Wifi) and they both connect to different networks. Is it possible to configure the browser to use the Wifi NIC and all the rest of apps to use the Ethernet NIC (or choose which traffic should go through which NIC) ?
|
Based on @dirkt comment, it can be done using namespaces.
If you are not using physical NICs, that can be done with ip netns:
Create a new network namespace : ip netns add net1
Move your NIC to that new namespace : ip link set NIC netns wifi
Start the app inside that new namespace and it will use only the NIC moved inside that namespace : ip netns exec net1 CMD args ...
NOTE: If your NIC is a physical card then a more elaborated process should be used, the following link provides more details: Move physical NIC to a different namespace
| Can i configure the browser to use one network interface and other apps to use the second? |
1,553,393,811,000 |
How to configure the teaming network?
On our redhat machines we configured as the following the teaming network
On each machine we have two links - ens1f5 and ens1f6
And we add the team0 file to control them
My question is- is it enough to create these 3 files?
So in case one of the links will failed then other link will be active ?
Or
We must to enable the teamdctl service in order team will works
For now teamdctl service is disable ( but teamd rpm is installed )
rpm -qa | grep teamd
teamd-1.17-5.el7.x86_64
teamdctl nm-team state
Device "nm-team" does not exist
the files under /etc/sysconfig/network-scripts are:
DEVICE=team0
DEVICETYPE=Team
ONBOOT=yes
BOOTPROTO=none
IPADDR=102.13.16.19
PREFIX=24
GATEWAY=102.13.16.3
TEAM_CONFIG='{"runner": {"name": "activebackup"}, "link_watch": {"name": "ethtool"}}'
DEVICE=ens1f5
HWADDR=28:df:31:30:d7:4a
DEVICETYPE=TeamPort
ONBOOT=yes
TEAM_MASTER=team0
TEAM_PORT_CONFIG='{"prio": 100}'
DEVICE=ens1f6
HWADDR=28:df:31:30:d2:4d
DEVICETYPE=TeamPort
ONBOOT=yes
TEAM_MASTER=team0
TEAM_PORT_CONFIG='{"prio": 100}'
Reference - https://www.rootusers.com/how-to-configure-network-teaming-in-linux/
|
I had to apt install libteam-dev to get the 'nm-team' device to show. Strange but even though Kunbuntu 20.04 has everything else in that startup Reference guide above, I was also following, it didn't have that. I also installed apt install libteam-utils to get the teamdctl command to work.
Nothing 'switch side' was needed. However, /etc/sysconfig/network-scripts, doesnt exist on _buntus. It is under /etc/NetworkManager/system-connections as 'team-slave-enp0s25.nmconnection' for example, because it uses the newer nmcli and network-manager.
| Network teaming configuration |
1,553,393,811,000 |
I'm using ubuntu 16.04. Here is the output of ifconfig:
-> ~$ ifconfig
eth0 Link encap:Ethernet HWaddr 3c:97:0e:e2:27:ea
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1243 errors:0 dropped:0 overruns:0 frame:0
TX packets:1243 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:89000 (89.0 KB) TX bytes:89000 (89.0 KB)
wlan0 Link encap:Ethernet HWaddr 40:f0:2f:3b:22:d2
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b147:93a0:c0e5:7ae6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4132 (4.1 KB) TX bytes:7730 (7.7 KB)
On windows I can connect the ethernet, I have restarted the network-manager, won't work.
-> ~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
After add add iface eth0 inet dhcp to /etc/network/interfaces and executing ifdown -a, command ifup -a gives:
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/3c:97:0e:e2:27:ea
Sending on LPF/eth0/3c:97:0e:e2:27:ea
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0xb3b79015)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0xb3b79015)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Here is my driver infomation:
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Flags: bus master, fast devsel, latency 0, IRQ 27
I/O ports at 2000 [size=256]
Memory at dbc04000 (64-bit, prefetchable) [size=4K]
Memory at dbc00000 (64-bit, prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169
-> ~$ dmesg | grep r8169
[ 1.129765] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.130652] r8169 0000:09:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.143154] r8169 0000:09:00.0 eth0: RTL8168evl/8111evl at 0xffffc9000067a000, 3c:97:0e:e2:27:ea, XID 0c900800 IRQ 27
[ 1.144101] r8169 0000:09:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 25.526338] r8169 0000:09:00.0 eth0: link down
|
Solution on AskUbuntu for Realtek ethernet driver error ubuntu 16.04 suggests you need an updated driver
sudo apt-get install r8168-dkms
| I can't connect to ethernet but can connet to wifi |
1,553,393,811,000 |
I am looking to generate raw Ethernet frames with payload that is preloaded into memory.
The Ethernet frames (10-60 full frames) should be generated at 1 ms intervals with no exception.
What would be my option to do this? My concern is in regards to the real-time requirements of such an application. Interrupts should be minimized and the process should perhaps have a core dedicated to its execution? If Linux/software is not an option the alternative is FPGA.
Looking forward to hear potential solutions.
|
1ms is plenty to generate a few Ethernet frames, but on a typical Linux system, you can't count on not having the occasional pause. Even if you make your process high-priority, I don't think you can expect to always make a 1ms deadline.
RTLinux combines a real-time operating system with Linux. Linux runs as a non-real-time-priority task in the real-time scheduler.
I lack experience with RTLinux, so I can't offer concrete advice, but it does include Ethernet drivers, so it looks suitable for your use case.
| Generate raw Ethernet frames with memory preloaded payloads at < 1 ms intervals |
1,553,393,811,000 |
I have a Centos server and I have a problem with automatic detection of cable connection.
Whenever server is up before router has started i need to restart server to make it detect IP.
For Example:
- I bootup server.
- No network is connected (cable unplugged or router down),
- Start router or plug in cable.
- Connection is not detected. Server needs a restart.
How to configure (console) server to watch for cable plug-in event?
Ifconfig output:
eth0 Link encap:Ethernet HWaddr 00:14:85:EE:7D:D9
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:feee:7dd9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33127 errors:0 dropped:0 overruns:0 frame:0
TX packets:37421 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6348000 (6.0 MiB) TX bytes:33946404 (32.3 MiB)
cat /etc/sysconfig/network-scripts/ifcfg-eth0 output:
# Intel Corporation 82801EB/ER (ICH5/ICH5R) integrated LAN Controller
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
HWADDR=00:14:85:ee:7d:d9
chkconfig (I use level 3):
/sbin/chkconfig --list network
network 0:off 1:off 2:On 3:On 4:On 5:On 6:off
/sbin/chkconfig --list NetworkManager
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
|
This seems to be exactly what NetworkManager was designed for.
Make sure NetworkManager is installed and the service running and stop the old network service.
By the way even with the network service rebooting is not necessary. A restart of that service should trigger a new dhcp request. But NetworkManager should do that automatically when it detects the cable is plugged in.
| How to setup automatic IP assignment after ethernet cable is plugged in |
1,553,393,811,000 |
I completed LFS and it boots but I'm not able to get the networking to work. When I do a ifconfig it list the lo that is the loopback network but doesn't detect eth0 and also says doesn't exist. If i do a ifconfig -a it lists sit0 as well but I don't know whats that for. I also enabled the network drivers for realtex but still not working. Any suggestions guys.
I have a Realtek 8160 Ethernet Controller on a Gigabyte board.
|
This sounds like the most likely culprit is a missing driver for your network card. You could check this by running the command lspci -k and seeing if your Ethernet adapter lists a kernel driver being used (which I suspect it won't).
Providing that this is the cause, you could either tell us here what network card you have installed in your machine (specifically, the line that shows your network card from the output of lspci); or by getting and booting another Linux live OS (such as an install disc for Ubuntu or Fedora - Gentoo has relatively small live environments since it's also a from-source distro, though System Rescue CD, which is Gentoo based, reportedly has better hardware support).
Once booted to another environment, lspci -k should show your network card with the kernel driver it loaded for it. If you can't determine which kernel option provides that driver (some of them can be a little obscure), either a search in menuconfig (using / then typing your search term) or Google should be able to help.
| Realtek 8160 not detected on LFS |
1,553,393,811,000 |
I have an IP phone on my home network that I am trying to call using SIP from outside of my home network. I have port forwarding setup, but the phone is responding with a SIP 404 message. All the documentation I've seen says to look at the incoming traffic for this connection via Wireshark. How do I do this?
My computer and this phone are both plugged directly into the router. Is there any way I can listen to the traffic on my computer with the current setup? I'm not sure if 'switched network' is the correct term, but I remember that on older networks that used hubs instead of switches, all packets were broadcast to all devices and listening to traffic not meant for you was easier.
I appreciate the privacy that switching provides, but what about in this case where I need to do debugging and have control over the network? Do I need to connect both the computer and the phone to a hub and then connect that to my router so the traffic is broadcast to both of their network cards? I don't have a hub at the moment so I have not tried this yet.
What are the other ways to capture packets meant for other devices in this scenario?
|
Monitoring Internet Traffic in Switched Networks
These days, the majority of local networks are switch-based. Unlike a hub, a switch, when it has received a packet from some port, retransmits it only to one port, where the recipient computer is connected to it. Switches maintain a table of MAC addresses and ports associated with each of those addresses (Content Addressable Memory table). When it has received a packet, switch validates the recipient’s MAC address in the table and selects the matching port to route the packet to. Due to this feature, Internet monitoring with LanDetective may be limited – your adapter will accept only packets that are addressed to you explicitly, because the switch would prevent other packets from getting into your network segment. Note that switches were created not for cutting traffic monitoring opportunities but rather for minimizing network load and maximizing its bandwidth. Moreover, there are special managed switches available on the market (and they are widely spread), which on top of their common features have a special one – to simplify the operation of traffic analysis systems and Internet monitoring solutions. Thanks to this capability, a managed switch can be configured in a way that all packets passing through it would be replicated to a certain switch port. Different manufacturers call the function a different name: Port Mirroring, Switched Port Analyzer (SPAN), or Roving Analysis Port (RAP). If you are a happy owner of a managed switch, turn to the specification for your device to find out whether this feature is supported and how you can activate it. In order to start Internet monitoring after the activation of Port Mirroring, you will need to just connect to the specified switch port and use the promiscuous Capture mode in LanDetective.
If you have linksys router then following way you can use Port Mirroring to get traffic on other switch interface. Linksys Router Port Mirrorning
Dirty way to capture traffic
If your switch is unmanageable or you don't have access you can connect your IP Phone directly to your laptop/Desktop and use Wireless Interface of laptop to connect your wireless router, also you need to configure routing in laptop to pass IP phone traffic through laptop that way you can run wireshark on your laptop and capture packets.
| How can I debug traffic on a switched network with Wireshark? |
1,553,393,811,000 |
The aim is to standardize the Ethernet adapter type on all production servers. One of these servers disposes an em1, rather than eth0.
Today, an attempt has been done to change it, without success. Before executing a second attempt, this conversion will be tested first.
A Vagrant box has been created and eth0 is the current adapter.
To mimic the production setting, the eth0 needs to be changed to em1. Biosdevname has been installed (sudo yum install biosdevname -y), 70-persistent-net.rules removed (sudo rm /etc/udev/rules.d/70-persistent-net.rules), biosdevname=1 executed and added to /etc/grub.conf as follows:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Scientific Linux (2.6.32-431.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-431.el6.x86_64 ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
initrd /initramfs-2.6.32-431.el6.x86_64.img
biosdevname=1
However, once the system has been rebooted and ifconfig has been executed the eth0 adapter persists.
How to change eth0 to em1?
|
Changing em* to eth*
NOTE: em0 and em1 are also used by RHEL & CentOS, and therefore Scientific Linux as well. They're typically used for embedded NICs that are built into the system's motherboard.
I found this blog post titled: Solved: Renaming em1 to eth0 on Red Hat Enterprise Linux 6 which suggested adding the following to your /etc/grub.conf, biosdevname=0.
excerpt
I've been burned enough times to do this out of habit: make a backup of /etc/grub.conf, retaining SELinux info:
$ sudo cp --preserve=context /etc/grub.conf /etc/grub.bak
Add biosdevname=0 to the kernel boot arguments in /etc/grub.conf.
Rename /etc/sysconfig/network-scripts/ifcfg-em1 to /etc/sysconfig/network-scripts/ifcfg-eth0, changing the line:
DEVICE="em1"
to
DEVICE="eth0"
Delete /etc/udev/rules.d/70-persistent-net.rules
Reboot.
Changing eth* to em*
If on the other hand you're attempting to change eth0 to em1, then I believe you need to move the biosdevname=1 from that standalonne line in your grub.conf file so that it's an actual parameter to the kernel line above.
For example:
kernel /vmlinuz-2.6.32-431.el6.x86_64 ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet biosdevname=1
References
Migrating from Conventional Device Names to Consistent Device Names for
Ethernet Devices in Red Hat Enterprise Linux v6
Biosdevname - Consistent Network Device Naming
biosdevname man page
9.6. CONSISTENT NETWORK DEVICE NAMING USING BIOSDEVNAME
| Change eth0 to em1 on Scientific Linux |
1,553,393,811,000 |
We are using pf_ring to capture packets. We are able to decipher information like source and destination ip, mac etc from the header information. Now we are moving into payload to decide the type of protocol, url and other information. We see that tcpdump and wireshark have done good parsing. Are those source code just for parsing is available given that we can provide each byte by byte into the function?
|
Look at things like bro-ids, snort, surricata, httpry. bro-ids is probably the closest to what you're looking for.
| Parsing protocol and url from packet payload |
1,553,393,811,000 |
I have recently installed backtrack on a VMWare box on my machine and I am trying to use DHCLIENT command but am having trouble in understanding the interfaces.
I am connected to the internet through wireless internet on my Mac but when I try and list all internet devices through backtrack, a WLAN doesn't show up,
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 08:00:27:cd:c9:cf brd ff:ff:ff:ff:ff:f
I am curious to know why a WLAN isn't showing but an ethernet connection is? Is this because Backtrack think its connected through WLAN through my Mac's wireless? Secondly, what's the first device 'lo'?
|
The WLAN device doesn't show up because VMWare virtualizes the hardware. The hardware you see inside the virtualized OS is not the hardware of the host node. The 'lo' device the loopback device.
| Help understanding interfaces in Backtrack |
1,553,393,811,000 |
please advice - what the meaning of FAILED word from ifconfig command
Dose its mean that network from NIC isn't stable until this moment ?
Not clearly if ifconfig read network status each some mili seconds?, I mean if network is stable so ifconfig should return the FAILED status to OK ?
yael
ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=19000802<BROADCAST,MULTICAST,IPv4,NOFAILOVER,FAILED> mtu 0 index 2
inet 0.0.0.0 netmask 0
groupname Mgmt_ipmp
ether 0:21:28:58:ff:6
e1000g1: flags=11000803<UP,BROADCAST,MULTICAST,IPv4,FAILED> mtu 1500 index 3
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
groupname Mgmt_ipmp
ether 0:21:28:58:ff:7
|
man ifconfig
section called "INTERFACE FLAGS"
FAILED
The interface has failed. New addresses cannot be
created on this interface. If this interface is part of
an IP network multipathing group, a failover will occur
to another interface in the group, if possible
Sometimes IPMP notices a problem with an interface and marks it as FAILED (this means that the test has failed, not that there is a hardware problem). This is because either be "the link is down" or "the ping test failed" (assuming you have test addresses).
| ifconfig + FAILED from ifconfig on solaris machines |
1,553,393,811,000 |
Please forgive my ignorance, as I am still fairly new when it comes to linux under the hood!
Anyways - following up on my previous semi-related post, instead of trying a Debian testing image, I installed Debian stable and installed the latest 3.0.1 kernel via dpkg.
Specifically:
Ran apt-get update on internet enabled computer (computer A)
Transplanted /var/lib/apt/lists and /etc/apt/sources.list from computer A to new laptop with no internet (computer B)
apt-get --print-uris --yes install synaptic | grep ^\' | cut -d\' -f2 > packageuri.htm to get package download URLs
Downloaded the packages from computer A and copied them to computer B
Installed synaptic with dpkg
Ran synaptic and updated the laptop by generating a download script (feature in synaptic)
Ran script from computer A, copied packages to computer B, dpkg -i *.deb
Downloaded the linux-image and all related files (though apt, synaptic didn't let me install linux-image-3.0.1-* for some reason) similarly to step 3
Installed files via dpkg. update-grub was run and new kernel is detected
Boot into new system, still have no internet.
According to this link, installing >= 2.6.38 should allow the card to be used. Am I missing something?
Thanks!
|
There are several things that can go wrong with network interface cards, no kernel support is just one of them.
I'm not currently using any Atheros card, so I don't have specific experience to share, but here goes a generic tip:
Check for messages in the kernel log (doing dmesg | grep eth in a terminal should be enough (although I remember madwifi used ath instead of eth)). (1) suggests dmesg | grep -i net
Several things may happen:
no networking-related messages (or just messages related to other network devices, if you have anything other than that card). This means that there is really some issue with kernel support (of course this may also mean the card is dead, but that's probably not the issue here).
messages related to the card, reporting, e.g., missing firmware (in which case you have to find out which package to install to get said firmware (if there's a package for it)). There may also be other errors, which will at least give you some pointers on what's the issue.
success messages, which means the card is working and the issue is somewhere else, in the network configuration or in the tools used to connect to the network (such as the DHCP client)
Also, note that both this page I link and one of the pages linked above refer atl1c, not atl1e.
| Upgrading to linux kernel 3.0.1 but my ethernet card is still not found? |
1,553,393,811,000 |
My GbNIC (Intel 82579LM, kernel 3.0 module e1000e) only connects with 100mbit although it's connected to a 1000mbit port (Asus GigaX1005) via an short (<3m) CAT6 cable.
flo-nbook ~ # ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000001 (1)
drv
Link detected: yes
Also forcing has no effect:
ethtool -s eth0 speed 1000
Is this a known bug in the kernel module? Am I missing something? Or an interoperability problem with the Asus switch?
|
According to Asus's specs on that switch, its only capable of 100mbit.
http://www.asus.com/Networks/Wired_Routers_Switches/GigaX1005/#specifications
5 RJ-45 for 10/100Mbps Ethernet ports
Also you cant set ports to 1000mbit, it must be auto-negotiated.
| Why do I only get 100mbit on my Asus GigaX1005? |
1,553,393,811,000 |
I have a Dell 710 with Quad Bcom NetExtreme 5709s. In the name of expediency, I'm trying to boot off the Squeeze live CD, but the Broadcom drivers are in non-free, so they don't come up when you boot.
No problem, I think to myself. I will sneaker-net the bnx2-firmware deb and all is good.
I can see the interfaces in lspci, I have unpacked the deb and successfully executed modprobe bnx2; however I still can't see the interfaces in ip link show. What else should I do to bring these interfaces up without a reboot?
EDIT
I have old entries in /var/log/kern.log about the failure to load bnx2 at boot, but the modprobe completes successfully with no other log entries...
$ lsmod | grep bnx
bnx2 57385 0
|
The firmware must be present at the time you load the driver. So be sure to unload the module and reload it:
# <install firmware>
rmmod bnx2
modprobe bnx2
For some drivers (I don't know about this one), you may need to unload auxiliary modules that it's using. lsmod | grep bnx2 will show what modules bnx2 uses. Call rmmod on all of them in reverse dependency order.
Most modules emit some log messages when they're loaded and they find a potential device, sometimes even if they don't find a potential device. These logs would be on /var/log/kern.log, at least on Debian and Ubuntu.
| Debian Live - modprobe failed to bring up Broadcom ethernet interfaces |
1,553,393,811,000 |
I am working on an embedded system that will connect a processor running Linux to an Ethernet switch via a "conduit" Ethernet link (e.g. eth0) using the port-based Ethertype DSA (Marvell) frame tagging protocol, so that the Linux kernel will present the userspace with separate Ethernet links for each of the switch's user ports (e.g. lan1, lan2, lan3).
As I understand it this is usually done via a fixed phy-less conduit (e.g. xMII) and an MDIO link between the processor and the switch so that the processor can configure and control the physical user ports.
I want to do some software development ahead of receiving the hardware, so I want to "fake" the MDIO link, or in some other way configure the kernel, such that it uses port-based EDSA frame tagging over an ordinary (PHY-equipped) Ethernet port, resulting in a frame layout like this:
7 6 5 4 3 2 1 0
. . . . . . . . .
0 +---+---+---+---+---+---+---+---+
| Ether Destination Address |
+6 +---+---+---+---+---+---+---+---+
| Ether Source Address |
+6 +---+---+---+---+---+---+---+---+ --
| Prog. DSA Ether Type [15:8] | |
+1 +---+---+---+---+---+---+---+---+ |
| Prog. DSA Ether Type [7:0] | | EDSA tag
+1 +---+---+---+---+---+---+---+---+ |
| Reserved (0x00 0x00) | |
+2 +---+---+---+---+---+---+---+---+ | --
| Mode |b29| Switch Device | | |
+1 +---+---+---+---+---+---+---+---+ | |
| Switch Port |b18|b17|b16| | |
+1 +---+---+---+---+---+---+---+---+ | | DSA tag
| PRI [2:0] |b12| VID [11:8] | | |
+1 +---+---+---+---+---+---+---+---+ | |
| VID [7:0] | | |
+1 +---+---+---+---+---+---+---+---+ -- --
| Ether Length/Type |
+2 +---+---+---+---+---+---+---+---+
. . . . . . . . .
...where Switch Port corresponds to the switch's user port number.
The documentation of kernel modules dsa_loop and dsa_loop_bdinfo imply that these might be suitable, and the source code seems to link .netdev = "eth0" to some user ports ("lan1".."lan4") but even though I can modprobe dsa_loop into my kernel I don't see any virtual port devices created by the kernel (I am using ifconfig -a to show net devices).
~# lsmod
Module Size Used by
dsa_loop 16384 0
dsa_core 118784 1 dsa_loop
When doing the modprobe dsa_loop I see a call to dsa_loop_init but no call to dsa_loop_drv_probe.
So I guess I have several questions:
Are the dsa_loop and dsa_loop_init modules intended to allow EDSA tagging to be performed on a "normal" Ethernet link?
How are these modules intended to be used?
Are there any other ways of configuring Linux to do this without access to the switch MDIO?
|
OP said:
Are the dsa_loop and dsa_loop_init modules intended to allow EDSA tagging to be performed on a "normal" Ethernet link?
Yes.
The problem I was running into is the result of an ordering problem between these loadable modules and the fixed-phy layer code which was being compiled as a built-in module.
When the kernel configuration was changed to compile them as build-in modules along with the fixed-phy code the problem went away and I could see calls to dsa_loop_drv_probe.
| Is it possible to configure Ethertype DSA VLAN tagging on an Ethernet port that has a real PHY connection to the outside world? |
1,553,393,811,000 |
I think I understand "Automatic" and "Manual", but what is "Ignore"? If I choose "Ignore", then the speed setting becomes unavailable. If the speed is not automatically decided nor manually set, what speed is chosen when "Ignore"d?
|
Since you don't tell what software produces the image you shown, I'll assume it is some interface to networkmanager.
If link negociation is ignored then… no change to the already set connection parameters will be committed by the utility you are currently running.
Now, what does this already set of connection parameters consist in ?
Whatever you would have specifically specified in whatever .conf-like file or forced by whatever other networkmanager-agnostic application running. (But this is unlikely since… why would you be running networkmanager then ?)
Much more likely ; whatever NIC's factory settings or default set by its driver at init time.
While, in your apparent case of a 1 Gbps NIC, this is likely to mean 1 Gbps / Full-Duplex… it could just in fact be 0 Gbps / Half-Duplex or whatever… in between…
| Ethernet "link negotiation", manual vs ignore? |
1,553,393,811,000 |
I already did a bunch of troubleshooting in the last three days regarding this issue. Here are the tests and the observations I made so far:
Internet connection to my server is dropping constantly (see ping below)
Server has static address and the address is out of the DCHP Range of the router
Modem is a Modem/Router used in Bridged mode. (Reset to factory settings 3 times now)
I tried 3 different routers = same results 50% packet loss
I tried two different physical interfaces = same 50% packet loss
I tried 3 different Ethernet cables = same 50% packet loss
I stopped many of my processes on my server simultaneously (see the list below)
I disabled my firewall
My connections from the clients to the server on my LAN is always 100% packet received
Connecting the server directly to the modem showed no packet loss while pinging 8.8.8.8
Got nothing unusual in dmesg or journalctl when the Internet connection failures happen
Connecting the Ethernet cable in my laptop instead of the server results in no packet loss from the laptop while pinging 8.8.8.8
Booting a Arch Linux from a USB drive gives me no problem with the Internet whatsoever.
I figured at that point that this must be a software related issue. But now I'm stuck.
Here's my ping results. It's basically the same every time I run it under the different environments I tried listed below.
➜ ~ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=14.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=14.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=13.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=14.9 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=119 time=14.8 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=119 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=119 time=15.5 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=119 time=2052 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=119 time=1024 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=119 time=16.7 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=119 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=119 time=19.5 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=119 time=23.0 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=119 time=12.6 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=119 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=119 time=26.0 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=119 time=18.8 ms
64 bytes from 8.8.8.8: icmp_seq=31 ttl=119 time=24.8 ms
64 bytes from 8.8.8.8: icmp_seq=32 ttl=119 time=13.9 ms
64 bytes from 8.8.8.8: icmp_seq=33 ttl=119 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=34 ttl=119 time=15.9 ms
64 bytes from 8.8.8.8: icmp_seq=35 ttl=119 time=15.6 ms
64 bytes from 8.8.8.8: icmp_seq=36 ttl=119 time=14.6 ms
64 bytes from 8.8.8.8: icmp_seq=37 ttl=119 time=12.8 ms
64 bytes from 8.8.8.8: icmp_seq=38 ttl=119 time=14.7 ms
64 bytes from 8.8.8.8: icmp_seq=39 ttl=119 time=14.7 ms
64 bytes from 8.8.8.8: icmp_seq=40 ttl=119 time=16.0 ms
64 bytes from 8.8.8.8: icmp_seq=41 ttl=119 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=42 ttl=119 time=15.8 ms
64 bytes from 8.8.8.8: icmp_seq=43 ttl=119 time=33.0 ms
64 bytes from 8.8.8.8: icmp_seq=44 ttl=119 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=45 ttl=119 time=19.4 ms
64 bytes from 8.8.8.8: icmp_seq=46 ttl=119 time=15.0 ms
64 bytes from 8.8.8.8: icmp_seq=47 ttl=119 time=30.3 ms
64 bytes from 8.8.8.8: icmp_seq=48 ttl=119 time=15.8 ms
64 bytes from 8.8.8.8: icmp_seq=49 ttl=119 time=14.0 ms
64 bytes from 8.8.8.8: icmp_seq=50 ttl=119 time=12.9 ms
64 bytes from 8.8.8.8: icmp_seq=51 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=52 ttl=119 time=14.3 ms
64 bytes from 8.8.8.8: icmp_seq=53 ttl=119 time=15.8 ms
64 bytes from 8.8.8.8: icmp_seq=54 ttl=119 time=14.4 ms
64 bytes from 8.8.8.8: icmp_seq=55 ttl=119 time=15.1 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=119 time=20.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=119 time=13.9 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=119 time=15.5 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=119 time=14.5 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=119 time=14.5 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=119 time=13.5 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=119 time=14.9 ms
64 bytes from 8.8.8.8: icmp_seq=64 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=65 ttl=119 time=16.3 ms
64 bytes from 8.8.8.8: icmp_seq=66 ttl=119 time=14.0 ms
64 bytes from 8.8.8.8: icmp_seq=85 ttl=119 time=2080 ms
64 bytes from 8.8.8.8: icmp_seq=86 ttl=119 time=1056 ms
64 bytes from 8.8.8.8: icmp_seq=87 ttl=119 time=32.5 ms
64 bytes from 8.8.8.8: icmp_seq=88 ttl=119 time=22.6 ms
64 bytes from 8.8.8.8: icmp_seq=89 ttl=119 time=15.3 ms
64 bytes from 8.8.8.8: icmp_seq=90 ttl=119 time=12.9 ms
64 bytes from 8.8.8.8: icmp_seq=91 ttl=119 time=14.7 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=119 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=119 time=15.7 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=119 time=17.5 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=119 time=15.1 ms
64 bytes from 8.8.8.8: icmp_seq=117 ttl=119 time=16.6 ms
64 bytes from 8.8.8.8: icmp_seq=118 ttl=119 time=13.0 ms
64 bytes from 8.8.8.8: icmp_seq=119 ttl=119 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=120 ttl=119 time=11.8 ms
64 bytes from 8.8.8.8: icmp_seq=121 ttl=119 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=122 ttl=119 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=123 ttl=119 time=13.5 ms
64 bytes from 8.8.8.8: icmp_seq=124 ttl=119 time=27.5 ms
64 bytes from 8.8.8.8: icmp_seq=149 ttl=119 time=960 ms
64 bytes from 8.8.8.8: icmp_seq=150 ttl=119 time=14.6 ms
64 bytes from 8.8.8.8: icmp_seq=151 ttl=119 time=15.9 ms
64 bytes from 8.8.8.8: icmp_seq=152 ttl=119 time=15.6 ms
64 bytes from 8.8.8.8: icmp_seq=153 ttl=119 time=26.9 ms
64 bytes from 8.8.8.8: icmp_seq=154 ttl=119 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=155 ttl=119 time=15.5 ms
64 bytes from 8.8.8.8: icmp_seq=156 ttl=119 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=157 ttl=119 time=16.0 ms
64 bytes from 8.8.8.8: icmp_seq=164 ttl=119 time=14.1 ms
64 bytes from 8.8.8.8: icmp_seq=165 ttl=119 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=166 ttl=119 time=21.3 ms
64 bytes from 8.8.8.8: icmp_seq=167 ttl=119 time=14.7 ms
64 bytes from 8.8.8.8: icmp_seq=168 ttl=119 time=15.4 ms
64 bytes from 8.8.8.8: icmp_seq=169 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=170 ttl=119 time=14.3 ms
64 bytes from 8.8.8.8: icmp_seq=171 ttl=119 time=15.9 ms
64 bytes from 8.8.8.8: icmp_seq=172 ttl=119 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=173 ttl=119 time=16.8 ms
64 bytes from 8.8.8.8: icmp_seq=174 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=175 ttl=119 time=14.0 ms
64 bytes from 8.8.8.8: icmp_seq=176 ttl=119 time=17.3 ms
64 bytes from 8.8.8.8: icmp_seq=177 ttl=119 time=16.7 ms
64 bytes from 8.8.8.8: icmp_seq=178 ttl=119 time=21.3 ms
64 bytes from 8.8.8.8: icmp_seq=179 ttl=119 time=14.4 ms
64 bytes from 8.8.8.8: icmp_seq=180 ttl=119 time=17.6 ms
64 bytes from 8.8.8.8: icmp_seq=181 ttl=119 time=13.7 ms
64 bytes from 8.8.8.8: icmp_seq=182 ttl=119 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=183 ttl=119 time=15.4 ms
64 bytes from 8.8.8.8: icmp_seq=184 ttl=119 time=14.7 ms
64 bytes from 8.8.8.8: icmp_seq=185 ttl=119 time=20.2 ms
64 bytes from 8.8.8.8: icmp_seq=186 ttl=119 time=14.5 ms
64 bytes from 8.8.8.8: icmp_seq=187 ttl=119 time=12.8 ms
64 bytes from 8.8.8.8: icmp_seq=188 ttl=119 time=15.4 ms
64 bytes from 8.8.8.8: icmp_seq=189 ttl=119 time=14.8 ms
64 bytes from 8.8.8.8: icmp_seq=190 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=191 ttl=119 time=14.1 ms
64 bytes from 8.8.8.8: icmp_seq=195 ttl=119 time=320 ms
64 bytes from 8.8.8.8: icmp_seq=196 ttl=119 time=13.5 ms
64 bytes from 8.8.8.8: icmp_seq=197 ttl=119 time=14.5 ms
64 bytes from 8.8.8.8: icmp_seq=198 ttl=119 time=15.5 ms
64 bytes from 8.8.8.8: icmp_seq=199 ttl=119 time=15.0 ms
64 bytes from 8.8.8.8: icmp_seq=200 ttl=119 time=13.1 ms
64 bytes from 8.8.8.8: icmp_seq=201 ttl=119 time=17.9 ms
64 bytes from 8.8.8.8: icmp_seq=202 ttl=119 time=15.6 ms
64 bytes from 8.8.8.8: icmp_seq=203 ttl=119 time=13.2 ms
64 bytes from 8.8.8.8: icmp_seq=225 ttl=119 time=1056 ms
64 bytes from 8.8.8.8: icmp_seq=226 ttl=119 time=32.5 ms
64 bytes from 8.8.8.8: icmp_seq=227 ttl=119 time=15.5 ms
64 bytes from 8.8.8.8: icmp_seq=228 ttl=119 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=229 ttl=119 time=15.7 ms
64 bytes from 8.8.8.8: icmp_seq=230 ttl=119 time=21.7 ms
64 bytes from 8.8.8.8: icmp_seq=231 ttl=119 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=232 ttl=119 time=13.5 ms
64 bytes from 8.8.8.8: icmp_seq=233 ttl=119 time=14.5 ms
^C
--- 8.8.8.8 ping statistics ---
248 packets transmitted, 128 received, 48.3871% packet loss, time 1216ms
rtt min/avg/max/mdev = 11.806/82.526/2080.231/306.259 ms, pipe 3
Two traceroute executed back to back
➜ ~ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 My WAN IP.mc.videotron.ca (My WAN IP) 19.047 ms 10.699 ms 19.035 ms
3 10.170.183.146 (10.170.183.146) 20.538 ms 21.036 ms 21.203 ms
4 72.14.205.46 (72.14.205.46) 20.269 ms 20.188 ms 20.189 ms
5 108.170.251.17 (108.170.251.17) 20.355 ms 108.170.251.33 (108.170.251.33) 20.149 ms 108.170.251.17 (108.170.251.17) 20.134 ms
6 108.170.231.63 (108.170.231.63) 21.359 ms 108.170.231.61 (108.170.231.61) 16.538 ms 108.170.231.63 (108.170.231.63) 16.186 ms
7 dns.google (8.8.8.8) 16.761 ms 15.483 ms 15.866 ms
➜ ~ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * dns.google (8.8.8.8)
/etc/network/interfaces
➜ ~ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#source /etc/network/interfaces.d/*
# The loopback network interface
#auto lo
#iface lo inet loopback
# The primary network interface
#allow-hotplug enx00e04c6802a2
auto lo br0
iface lo inet loopback
auto enp5s0
iface enp5s0 inet manual
iface br0 inet static
address 192.168.3.104
netmask 255.255.255.0
gateway 192.168.3.1
bridge_ports enp5s0
bridge_stp off
bridge_fd 0
bridge_maxwait 0
post-up iptables-restore < /etc/iptables.up.rules
Thanks for your help
EDIT 1
➜ ~ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000
link/ether 70:85:c2:da:2a:87 brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 70:85:c2:da:2a:87 brd ff:ff:ff:ff:ff:ff
4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/none
➜ ~ ip -br address
lo UNKNOWN 127.0.0.1/8 ::1/128
enp5s0 UP
br0 UP 192.168.3.104/24 fe80::7285:c2ff:feda:2a87/64
wg0 UNKNOWN 192.168.3.1/24
➜ ~ ip route;
default via 192.168.3.1 dev br0 onlink
103.83.20.3 dev wg0 scope link
103.83.20.4 dev wg0 scope link
169.254.0.0/16 dev br0 scope link metric 1000
192.168.3.0/24 dev br0 proto kernel scope link src 192.168.3.104
192.168.3.0/24 dev wg0 proto kernel scope link src 192.168.3.1
➜ ~ ip neigh
192.168.3.126 dev br0 lladdr 04:6c:59:f6:a0:3b REACHABLE
192.168.3.164 dev br0 lladdr be:95:3a:fc:bf:03 STALE
[PUBLIC IP] dev br0 lladdr c4:04:15:10:b1:bd STALE
192.168.3.127 dev br0 lladdr 4c:3b:df:7f:c6:03 STALE
192.168.3.1 dev br0 lladdr c4:04:15:10:b1:bd REACHABLE
192.168.3.125 dev br0 lladdr 0c:c4:13:18:a4:c5 STALE
192.168.3.144 dev br0 lladdr b8:27:eb:28:4a:98 REACHABLE
➜ ~ ip rule
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
EDIT 2
@A.B is right. I forgot to mention I have been running a VPN Server (Wireguard) and it was indeed the problem.
|
I finally disabled my Wireguard server systemctl disable wg-quick@wg0 && systemctl stop wg-quick@wg0 until I take the time to investigate what was wrong with it and it did the trick.
| Debian headless server connected to Ethernet interface ~50% packet loss accessing the Internet |
1,586,612,201,000 |
I'm trying to configure dnsmasq as dhcp server on CentOS 7 minimal installation.
My network consists of wi-fi AP, Ethernet, Bluetooth PAN and bridge called common-bridge which serves as master for all of them.
dnsmasq is listening on common-bridge interface with following config:
domain-needed
bogus-priv
no-resolv
filterwin2k
expand-hosts
listen-address=127.0.0.1
listen-address=192.168.1.1
dhcp-range=192.168.1.5,192.168.1.150
The strange thing is that DHCP is working fine with Wi-Fi and BT, but Ethernet client can't obtain IP address.
Looks like there is no traffic at all because tcpdump shows no traffic on the server side.
|
The problem is related unstable network card driver (r8169) and is not related to network configuration.
Steps to install stable driver are described in Hetzner tutorial (link)
| dnsmasq as dhcp server configuration for Ethernet |
1,586,612,201,000 |
When I use rsync on large files it shows a download speed of 2.7 MB/s, or around 22Mbps. When I run ethtool on the NIC, here is the output
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
I found similar readings on the host machine.
When I look at ethtool -i etho I get the following:
driver: smsc911x
version: 2008-10-21
firmware-version:
expansion-rom-version:
bus-info: smsc911x.0
supports-statistics: no
supports-test: no
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
I double checked the ethernet cables I'm using, and all are at least 5e.
I'm using the LAN9221-ABZJ chip for this project. Is this a firmware issue, too much overhead on the protocols, or is this chip know for not transmitting fast enough?
UPDATE
I checked the speeds with iperf. Going from the server side it was 50Mbps. From the Client side it was 65 Mbps. Also, I had to do this remotely (as in i ssh'd into the one machine to configure it). That seems a little low.
|
Check the Cpu usage through htop while it is transmitting data. If it is maxed out during ethernet events, it is a good sign that your cpu is the bottleneck. The only fixes are to increase the clock of your cpu, or to get a faster one.
| not getting full network speed (or even close) of 100 mbps |
1,437,634,436,000 |
I am having an issue with my smartphone device and packets monitoring: I am trying to find a reason why I cannot establish a VPN connection via PPTP protocol.
I have the following successful scenario:
Device set using IPv4
Connecting to VPN OK
Now a failing scenario:
Device set using IPv6
Connecting to VPN fails (after 30s timeout)
I checked tcpdump result and found out the following: during exchanges for connection establishment, both IPv6 and IPv4 scenario are the same until my device is sending a "PPP LCP Configuration-Request" to server.
Then a Ack comes back from server for IPv4 scenario, and nothing comes back for IPv6 scenario. On server side they affirm that in both scenario the Ack is send back.
Questions
If tcpdump does not show this packet, does that mean it has not been received ?
If this packet have been received but "dropped", how can I find out (tools, methodology) ?
I am not a Linux nor a network expert so I might miss some trivial hints.
Thanks,
Linux version 3.10.40
|
If tcpdump does not show this packet, does that mean it has not been received ?
Yes, that's what it means. Packet capture directly sees what's being received on the wire. If there were a firewall/filter rule dropping the packet, it would still show up in the packet capture and then it would be dropped at a later time.
Most likely something else somewhere along the network path is filtering the ConfAck. You could inquite whether the ConfAck in the IPv6 case is much larger than the ConfAck in the IPv4 case. I don't see why it would be, but if it were much bigger, enough to require fragmentation somewhere along the way due to an MTU issue, I guess that could cause the problem?
| check tcp packets reception below tcpdump level |
1,437,634,436,000 |
I have a PC on a test bench with 2 interfaces, enp2s0 and enp3s0. The IPs are public and obtained with DHCP, based on the interfaces MACs. There is a second computer on my bench, a Raspberry Pi Compute Module 3, which I want to expose on the internet. The RPi and bench sever are connect together through PPP, over a serial connection. On both side the ppp interface is called ppp0.
How can I bridge ppp0 and enp3s0, so that the RPi CM3+ accessible from the public IP? I'm lost among linux's many bridge and tunnel options...
My organization doesn't allow me to do routing or use switches. Any solution that minimize the chance of me wrecking the rest of the network would be awesome.
|
The IPs are public and obtained with DHCP, based on the interfaces MACs.
Which means that when bridged the ppp interface would need to get a third public IP obtained with DHCP. Which won't work with ppp.
bridge ppp0
Even if ppp0 wouldn't need a public IP, it's a point-to-point connection, as the name implies. So you cannot bridge it.
so that the RPi CM3+ accessible from the public IP?
The simplest way is to enable forwarding on the Bench PIC, NAT ppp0 on either of the external NICs, and add port forwarding rules. (Google, there's hundreds of tutorials). This would mean some ports on the RPi will be accessible under the given external IP, potentially under different port numbers. And the Rpi can access all of the internet. Which will work if there's a known number of services running on the Rpi which need to be accessed.
If the Rpi has to have a third public IP, add a VPN that's bridgeable on top of the ppp0 connection (which will cause additional overhead), then bridge the resulting tun/tap interface.
| Bridge PPPoS with ethernet |
1,437,634,436,000 |
I'd like to do some experiments to test the ping and fping commands (see: Equivalent of `ping -o` on Linux), but I need a local virtual Ethernet interface to test this.
I'd like to have a scenario where I can run ping 10.0.0.1 (or any other IP) and have it fail. Then, while ping is still running, I run some commands that bring up the interface and have it pass. In other words, the output of ping will change while it is running, as the virtual device comes "alive". I don't want to have to use physical hardware.
How can I do this?
I've already tried following my own instructions here (How can I create a virtual ethernet interface on a machine without a physical adapter?), but unfortunately even after running sudo ip link set eth10 down, pinging eth10 via ping 10.0.0.1 still succeeds. After running sudo ip link delete eth10 type dummy to delete the dummy virtual device, ping 10.0.0.1 also still succeeds.
Summary of functional answers so far:
(as of 22 Nov. 2021)
3 answers received (my own included), and all 3 answers work!:
by Stephen Harris - use loopback sub-interfaces (probably the best answer so far)
by Hauke Laging - use iptables
my own answer - use virtual interfaces
|
@Hauke Laging is right in his comment under my question:
There may be a different 10.0.0.1 somewhere. Compare the outputs of ip route get 10.0.0.1 in both cases.
ip route get 10.0.0.1 shows this before deleting the dummy interface:
local 10.0.0.1 dev lo src 10.0.0.1 uid 46153590
...indicating that that route is going through the dummy interface I created, and it shows this after deleting the dummy interface by running sudo ip link delete eth10 type dummy:
10.0.0.1 dev wlp0s20f3 src 10.0.0.36 uid 28301632
...indicating that IP is now being routed through my wlp0s20f3 wireless card. I guess that makes sense because my local WiFi is using and assigning 10.0.0.x IP addresses.
The solution, therefore, is to simply choose a different IP which is not pingable before creating the virtual interface to it! Using 10.0.0.100 instead of 10.0.0.1 in my case worked just fine. But, let's just use 254.254.254.254 for the case of this example.
Full Example:
First, ensure the desired IP address you'd like to use is NOT currently responding to ping:
ping -c 1 -W 1 254.254.254.254
Sample output:
PING 254.254.254.254 (254.254.254.254) 56(84) bytes of data.
--- 254.254.254.254 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
Now create a dummy eth99 interface (for a full explanation, see my other answer here: How can I create a virtual ethernet interface on a machine without a physical adapter?):
sudo modprobe dummy \
&& sudo ip link add eth99 type dummy \
&& sudo ip address change dev eth10 254.254.254.254 \
&& ip address
Now it IS pingable. Run ping 254.254.254.254. Sample cmd and output:
$ ping 254.254.254.254
PING 254.254.254.254 (254.254.254.254) 56(84) bytes of data.
64 bytes from 254.254.254.254: icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from 254.254.254.254: icmp_seq=2 ttl=64 time=0.093 ms
64 bytes from 254.254.254.254: icmp_seq=3 ttl=64 time=0.086 ms
64 bytes from 254.254.254.254: icmp_seq=4 ttl=64 time=0.051 ms
^C
--- 254.254.254.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3050ms
rtt min/avg/max/mdev = 0.051/0.079/0.093/0.016 ms
Now, if you run ping 254.254.254.254 in one terminal, and sudo ip link delete eth99 type dummy in another, the ping response will quit incrementing once you delete the interface. sudo modprobe dummy; sudo ip link add eth99 type dummy; sudo ip address change dev eth99 254.254.254.254; ip address again will re-create the interface and make the ping start responding again.
| How to create Ethernet interface at a specific IP address that I can ping and force to sometimes reply and sometimes not? |
1,437,634,436,000 |
When we test the eth card with ethtool -S
we get rx_missed_errors: 4649.
What is the meaning of rx_missed_errors?
Is it a major problem?
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_fifo_errors: 0
rx_missed_errors: 4649
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_csum_offload_errors:
ethtool -g eth847
Ring parameters for eth847:
Pre-set maximums:
RX: 8192
RX Mini: 0
RX Jumbo: 0
TX: 8192
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024
|
The exact meaning of rx_missed_errors depends on the Ethernet driver in use, but it’s supposed to count missed packets on the receiver side, i.e. packets which the NIC received but had to drop because they couldn’t be stored or processed — typically, because the FIFO they would have gone to was full.
Whether it’s a major problem depends on the traffic being dropped. In most cases, dropped packets will end up retransmitted if necessary, by one layer of the stack or another.
If the drops are bursty, you could try increasing the buffers (if your NIC allows you to): check the maximum setting with ethtool -g, and set it with ethtool -G. In your case, you can set the receive and transmit rings to anything up to 8192:
ethtool -G eth847 rx 8192
It’s not necessarily a good idea to set the buffer to the maximum value immediately: larger buffers can result in increased latency. I suggest increasing the buffers progressively, and watching the error rate to see how it evolves.
| What is the meaning of rx_missed_errors? |
1,437,634,436,000 |
lets say I want to ping to some machine as from my machine - moon
ping -c 1 master01
now I want to understand what is the interface name in master01 machine that get the packet from ping
so how we can identify what is the interface name on master01 that packet from moon machine was sent?
|
It's not possible to find out which interface was used on remote machine using ping. You have to login to remote machine and check which interface has assigned IP address you are pinging. You can do it using ifconfig or ip address commands on Linux, and ipconfig command in Windows.
| linux & identify the interface name on remote machine |
1,437,634,436,000 |
Here are my system’ and interface’s details:
After connecting ethernet cable to the laptop, running ping gives me ping: connect: Network is unreachable and with sudo apt update, I het could not resolve <domain name> errors. How do I use ethernet?
|
Add the eno1 to /etc/network/interfaces:
auto eno1
allow-hotplug eno1
iface eno1 inet dhcp
edit your /etc/resolv.conf
echo "nameserver 8.8.8.8" |sudo tee -a /etc/resolv.conf
Then:
sudo dhclient eno1
Or use ifup .
| Can’t use ethernet after removing kde-plasma on debian 12 |
1,437,634,436,000 |
I've used the ethernet interface rarely in the past on my debian 10. Last week I've updated my debian to debian 11. During the installation it failed to connect via ethernet. I've tried 3 different cable some of them are in daily use for my tv. So a faulty cable can be ruled out. It was quite a challenge to get through the installation as I need some non-open firmwire for my wlan interface.
So now I would like to figure out if it is a setup issue or my hardware (ethernet) is broken. I'm not at all a specialist in interfaces / hardware related stuff. So would be great if someone could tell me what's the most likely case.
Running a simple
sudo lshw -class network -short
H/W path Device Class Description
============================================================
/0/100/1c.6/0 wlp3s0 network Wireless 8265 / 8275
/0/100/1f.6 enp0s31f6 network Ethernet Connection (4) I219-V
looks to me that the interface is wokring correctly, no? Does this mean the hardware has most likely a loose contact / is broken?
ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether 8c:16:45:32:c8:b8 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 00:21:6b:ff:ac:d5 brd ff:ff:ff:ff:ff:ff
Edit
/usr/sbin/ethtool enp0s31f6
Settings for enp0s31f6:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
Edit 2
After sample setting
sudo /usr/sbin/ethtool -s enp0s31f6 speed 100 duplex full
[sudo] password for nicolas:
(srv) nicolas@debian:~/phd/src$ sudo /usr/sbin/ethtool enp0s31f6
Settings for enp0s31f6:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
|
As discussed in the comments and based on the test (unsuccessful) to bring up interface with command:
ethtool -s enp0s31f6 speed 100 duplex full
I will say you have broken ethernet adapter. For me "Link detected: no" confirm this hypothesis. You can replace it with USB dongle (wireless or wired).
Also you can consider to send the machine in service center because usually these adapters are replaceable. Or do it by yourself.
| how to check if my ethernet interface is working properly or if it has a loose contact |
1,437,634,436,000 |
I am trying to modify the ethernet device name without modifying grub. I have tried to modify the device name, but when I do, the device stops working.
Things I have tried:
I've tried this
nmcli con edit id "Wired connection 1"
set connection.id testname
save
quit
I've also tried this:
nmcli connection modify ens33 connection.id testname
But neither of those change the device name, which is what I need (so I can access the device with ifconfig or ip addr)
I've also tried this
ifdown ens33
ifconfig ens33 down
ip link set ens33 name testname
mv /etc/sysconfig/network-scripts/ifcfg-ens33 /etc/sysconfig/network-scripts/ifcfg-testname
vi /etc/sysconfig/network-scripts/ifcfg-testname
ifconfig testname up
ifup testname
which appears to work at first glance because i can access the device with ifconfig, but after I bring the interface back up it fails to ping the target device (although it can ping itself).
The answer on this page looks promising, but I can't access it: https://access.redhat.com/solutions/108823
I must be missing a step, does anybody have an idea?
|
Changing the name of my network interface caused my mac address to change, therefore it would fail at the mac layer. By hardcoding the mac address into the /etc/sysconfig/network-scripts/ifcfg-testname file using the HWADDR directive, then the interface name change would work just fine; (It failed when I used the MACADDR directive).
This failed:
vim /etc/sysconfig/network-scripts/ifcfg-testname
MACADDR=xx:xx:xx:xx:xx
This succeeded:
vim /etc/sysconfig/network-scripts/ifcfg-testname
HWADDR=xx:xx:xx:xx:xx
found helpful info here:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking#how-the-network-device-naming-works_consistent-network-interface-device-naming
| RHEL 8 - How can I modify an ethernet device name? |
1,437,634,436,000 |
I bought a laptop this year, not via this website but from a vendor on Amazon.
I cannot connect to the internet via cable
and I'm afraid that my network interface is not working correctly for some unknown to me reason.
My environment: Ubuntu Desktop 20.04 LTS (the problem was present on Windows as well -
the OS that laptop was shipped to me). I can connect through the same cable from another laptop. WiFi works on this laptop but the quality is not good.
I ran ip l to identify the name of the interface in question and got the following output:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 18:c0:4d:0f:14:0d brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group
I've trimmed the last line of the output in order to avoid doxing the details of my wireless interface.
Having identified the name of the interface in question as enp3s0 I then proceeded further with my investigation and ran
sudo ethtool enp3s0
which returned the following output (irrespectively of the cable being plugged in or not).
Settings for enp3s0:
Cannot get device settings: No such device
Supports Wake-on: pumbg
Wake-on: d
Link detected: no
I've tried also sudo ethtool -p enp3s0 15
and got the following output (irrespectively of the cable being plugged in or not):
Cannot identify NIC: Operation not supported
The output of dmesg -t --level=alert,crit,err,warn is:
NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR0 is 0M @ 0x0 (PCI:0000:01:00.0)
nvidia: probe of 0000:01:00.0 failed with error -1
NVRM: The NVIDIA probe routine failed for 1 device(s).
NVRM: None of the NVIDIA devices were initialized.
NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR0 is 0M @ 0x0 (PCI:0000:01:00.0)
[...]
nvidia: probe of 0000:01:00.0 failed with error -1
NVRM: The NVIDIA probe routine failed for 1 device(s).
NVRM: None of the NVIDIA devices were initialized.
Where [...] stands for the first seven lines of the output repeated over 300 times.
My question is do I have a working ethernet interface?
|
Link detected: no
and
the problem was present on Windows as well - the OS that that laptop was shipped to me
Strongly indicate your NIC is not working. The circuitry might be OK, but a pin/some pins could be broken.
You're good to RMA the laptop or replace the NIC/connector.
| How might I diagnose whether I have a working ethernet interface? |
1,437,634,436,000 |
I want to know what actually happens once I turn my ethernet OFF.
What does the OS do on a network layer?
Does it flush the routing table or anything like that.
|
Linux kernel describes every Ethernet adapter(physical device or virtual) by struct net_device (struct net_device). Every struct net_device has a set of struct net_device_ops which should be implemented by device driver. The most important of them:
ndo_open(). Called when you set Ethernet adapter to ON (ip link set up dev <eth_dev>).
ndo_start_xmit(). Called when you start transmit data through the interface.
ndo_stop(). Called when you set Ethernet adapter to OFF(ip link set down dev <eth_dev>).
So, what's really does when device is going DOWN?
There are set of routines which implemented in most drivers:
stop all queues related to specific device.
clear ARP table entries related to specific device.
mark interface status as DOWN (ip link show dev <eth_dev>).
device specific features: clear some structs, buffers, move Ethernet controllers chip to sleep...
| What happens when I turn my ethernet off? What steps does the OS perform once I turn the ethernet OFF? |
1,437,634,436,000 |
My computer is under Debian 10 with this Linux image :
uname -r
4.19.0-16-amd64
and a R8125 Ethernet card.
lspci | egrep -i --color 'network|ethernet'
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8125 (rev 05)
05:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
Today, a new Linux image, 4.19.0.17-amd64 appeared through apt-get update and apt-get dist-upgrade.
These done and the computer rebooted, it doesn't recognize the Ethernet card anymore, and an ifconfig respond : no peripheral found.
So, of course, I'm using the 4.19.0.16 boot to write this question...
Once, the reseller of my computer moaned about the installation he has had to do with a
make install
done from a driver directory, /opt/r8125 it appears he has downloaded from https://github.com/tmacro/r8125.
But I didn't really understood what he did.
I've attempted to use his trick, two months ago, on another Debian partition my computer have (with an image 4.19.0-16-amd64), but :
it seems it didn't worked,
ls -l
-rw-r--r-- 1 root root 2511888 avril 24 13:43 r8125.ko
samedi 24 avril 2021, 13:43:55 (UTC+0200)
make -C src/ clean
make[1] : on entre dans le répertoire « /opt/r8125/src »
make -C /lib/modules/4.19.0-16-amd64/build M=/opt/r8125/src clean
make[2] : on entre dans le répertoire « /usr/src/linux-headers-4.19.0-16-amd64 »
make[2] : on quitte le répertoire « /usr/src/linux-headers-4.19.0-16-amd64 »
make[1] : on quitte le répertoire « /opt/r8125/src »
make -C src/ modules
make[1] : on entre dans le répertoire « /opt/r8125/src »
make -C /lib/modules/4.19.0-16-amd64/build M=/opt/r8125/src modules
make[2] : on entre dans le répertoire « /usr/src/linux-headers-4.19.0-16-amd64 »
CC [M] /opt/r8125/src/r8125_n.o
CC [M] /opt/r8125/src/rtl_eeprom.o
CC [M] /opt/r8125/src/rtltool.o
LD [M] /opt/r8125/src/r8125.o
Building modules, stage 2.
MODPOST 1 modules
CC /opt/r8125/src/r8125.mod.o
LD [M] /opt/r8125/src/r8125.ko
make[2] : on quitte le répertoire « /usr/src/linux-headers-4.19.0-16-amd64 »
make[1] : on quitte le répertoire « /opt/r8125/src »
make -C src/ install
make[1] : on entre dans le répertoire « /opt/r8125/src »
make -C /lib/modules/4.19.0-16-amd64/build M=/opt/r8125/src INSTALL_MOD_DIR=kernel/drivers/net/ethernet/realtek modules_install
make[2] : on entre dans le répertoire « /usr/src/linux-headers-4.19.0-16-amd64 »
INSTALL /opt/r8125/src/r8125.ko
DEPMOD 4.19.0-16-amd64
make[2] : on quitte le répertoire « /usr/src/linux-headers-4.19.0-16-amd64 »
make[1] : on quitte le répertoire « /opt/r8125/src »
or I haven't done something else that was necessary.
It looks strange to me that the network driver isn't able to follow Linux upgrades, and it's boring, but I have to comply with this event.
I don't want to upgrade my Linux image up to a 5.10 image, but to stay using the current one Debian 10 suggests.
|
You know the story : you only have to post/edit your question, and a few minutes later, it works...
So I wrote here the only things I did but (this time) worked, to help who would stumble upon the same problem I've encountered:
Go on the session where Ethernet connection is still available and
download the Git project https://github.com/tmacro/r8125 (for me, reseller put it in /opt), or put its content on an USB key.
Boot on the no-working session (here the 4.19.0.17-amd64 for me) and execute:
cd /opt/r8125/
sudo ./autorun.sh
The image 4.19.0.17-amd64 is updated and network works immediately.
(epilogue: I think I was misled by my reseller who told me to do a make install from /opt/r8125 directory when it was a ./autorun.sh that had to be done? Maybe...)
| My Realtek 8125 Ethernet card isn't reconized anymore after an apt-get update/dist-upgrade bring Debian 10 from 4.19.0.16 to 4.19.0.17 Linux image |
1,437,634,436,000 |
I know this question sounds dumb but lately It's quite hard for my mind to visualize whole packet flow at Layer 2 level.
I'm developing a firewall at Layer 2 and interested at inspecting TCP packets while routing the packets back and forth.
But It's doubtful whether I could inspect the TCP stream as I can't confirm whether the TCP stream involve multiple Ethernet packets between the flow
I made attempts using Wireshark but to be honest, I'm lost at figuring out how to extract the whole stream..........
|
TCP is implemented agnostic of the data link layer. Thus, a TCP packet can span one or more ethernet frames.
If you want filter at the data link layer and inspect higher layers of the network communication as well, you will need to assemble the TCP communication manually from the composite data link frames, and then inspect the layer 3 information.
Ethernet frames have standard sizes, so assembling packets from frames should not be that challenging, and you may find that most of the TCP handshaking steps themselves may fit inside a single ethernet frame, but if you happen to be working with an 802.11 media, this could become much more daunting since layer 2 can be encrypted between Wifi clients and access points.
| Do a TCP stream comprising SYNs and ACKs involve only one-time Ethernet packet? |
1,437,634,436,000 |
BACKGROUND DETAILS:
I've inhereted a QNAP TS-459U-RP.
I currently have it connected to my home router via an ethernet/rj45 cable. My computer is connected to the same router. How do I access the QNAP from my computer?
If I open nautilus and go to + Other Locations, I now see 2 new options under Networks which only become visible if the QNAP is connected to the router and switched on. The 2 options which become avaible in + Other locations are:
NASC3C6BC(FTP)
NASC3C6BC(SAMBA)
THE MESSAGES:
When I click on the 2 options within Nautilus, I get the following messages:
For the FTP option I get Opening "qnap-001.local (ftp) You can stop this operation by clicking cancel."
Nothing happens if I do not click Cancel.
For the SAMBA option I get Unable to access location - Failed to retrieve share list from server: Connection timed out
I then Get an OK button.
THE RESET BUTTON:
I do not know the username and password. I have checked the manual and it says that I should press the reset button at the back for 3 seconds to reset the admin password and that after 3 seconds it will make a beeping sound. When I press the reset button at the back for 3 seconds or longer, it makes no beeping sound.
|
You need to configure the QNAP using its web GUI. There are lots of manuals, tutorials, etc. at https://qnap.com. Default username is admin, possibly with password admin.
To find its IP address you can either use the QNAP Finder tool (Windows, downloadable from QNAP's website), or look at whatever issues DHCP addresses on your network.
| How do I connect to a QNAP [closed] |
1,437,634,436,000 |
I prepared dhcpd configuration in Debian 8 and it successfully worked but then I added bridge and dhcpd failed.
bridge:
root@remote:/home/s# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00224dad5ddf no eth0
eth1
root@remote:/home/s# cat /etc/network/interfaces
auto lo br0
iface lo inet loopback
iface ppp0 inet wvdial
provider orange
iface eth0 inet manual
iface eth1 inet manual
allow-hotplug br0
iface br0 inet static
bridge_ports eth0 eth1
address 192.168.0.1
netmask 255.255.255.0
root@remote:/home/s#
dhcpd:
root@remote:/home/s# systemctl -l status isc-dhcp-server.service
● isc-dhcp-server.service - LSB: DHCP server
Loaded: loaded (/etc/init.d/isc-dhcp-server)
Active: failed (Result: exit-code) since Sun 2018-07-01 21:51:43 CEST; 24min ago
Process: 1037 ExecStart=/etc/init.d/isc-dhcp-server start (code=exited, status=1/FAILURE)
Jul 01 21:51:41 remote dhcpd[1076]: No subnet declaration for eth0 (no IPv4 addresses).
Jul 01 21:51:41 remote dhcpd[1076]: ** Ignoring requests on eth0. If this is not what
Jul 01 21:51:41 remote dhcpd[1076]: you want, please write a subnet declaration
Jul 01 21:51:41 remote dhcpd[1076]: in your dhcpd.conf file for the network segment
Jul 01 21:51:41 remote dhcpd[1076]: to which interface eth0 is attached. **
Jul 01 21:51:43 remote isc-dhcp-server[1037]: Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!
Jul 01 21:51:43 remote isc-dhcp-server[1037]: failed!
Jul 01 21:51:43 remote systemd[1]: isc-dhcp-server.service: control process exited, code=exited status=1
Jul 01 21:51:43 remote systemd[1]: Failed to start LSB: DHCP server.
Jul 01 21:51:43 remote systemd[1]: Unit isc-dhcp-server.service entered failed state.
root@remote:/home/s# cat /etc/dhcp/dhcpd.conf
ddns-update-style none;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.2 192.168.0.6;
option domain-name-servers 8.8.8.8,8.8.4.4;
option routers 192.168.0.1;}
root@remote:/home/s#
How to add this "subnet declaration for eth0" and fix dhcpd service?
|
Your original DHCP server configuration used eth0. You've now replaced that in your network definitions with br0, so you need to update your DHCP server configuration accordingly.
| dhcpd and bridge - No subnet declaration error |
1,437,634,436,000 |
I was looking to move from wifi to ethernet. My computer is a Lenovo Thinkpad Carbon Gen II. This computer does not have an ethernet port. You have to rely on a dongle. I still own the one shipped with the computer
(it looks like this). Since mine is a bit damaged over the time. Today, I bought a new one (a usb to rj45 adapter) on Amazon. I cannot find a way to make it work. Any help is welcome.
end of hostnamectl:
Operating System: Manjaro Linux
Kernel: Linux 4.4.83-1-MANJARO
Architecture: x86-64
output of ifconfig enp0s25:
enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 54:ee:75:96:39:28 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
device interrupt 20 memory 0xf0500000-f0520000
output of lspci:
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-V (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 6 (rev e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
output of lsusb:
Bus 003 Device 003: ID 04ca:7036 Lite-On Technology Corp.
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 006: ID 1058:107c Western Digital Technologies, Inc. Elements Desktop (WDBWLG)
Bus 002 Device 005: ID 0bc2:a0a4 Seagate RSS LLC Backup Plus Desktop Drive
Bus 002 Device 004: ID 0bc2:a0a4 Seagate RSS LLC Backup Plus Desktop Drive
Bus 002 Device 003: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 8087:07dc Intel Corp.
Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 001 Device 003: ID 04d9:0169 Holtek Semiconductor, Inc.
Bus 001 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
In order to test if the connection is working:
ifconfig enp0s25 up (this enables your network interface/the dongle)
dhcpcd (this starts a dhcp client in order to obtain an ip address)
When this works you can move to a more permanent and convenient solution:
For example, you can use netctl in order to automatically connect.
What you have to do:
Create a profile in /etc/netctl/my_dhcp_profile or how you like to name it; you can create multiple ones too. Such as:
Interface=enp0s25
Connection=ethernet
IP=dhcp
or (Static IP):
Interface=enp0s25
Connection=ethernet
IP=static
Address=('10.1.10.2/24')
Gateway=('10.1.10.1')
DNS=('10.1.10.1')
Enable the Profile:
netctl enable my_dhcp_profile
netctl start my_dhcp_profile
After that, it will be automatically activated when available and should not require further interaction.
The start basically is required in order to start it up now and not after a reboot. You can also use stop to manually deactivate it.
| Unable to connect ethernet by dongle |
1,437,634,436,000 |
tcpdump -i mlan0 -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode listening on mlan0, link-type EN10MB (Ethernet), capture size
262144 bytes
Why is this Ethernet here? I am using wifi, not an Ethernet.
decode listening on mlan0, link-type EN10MB (Ethernet), capture size
262144 bytes
I'm not sure how I can research this. I can find man pages on tcpdump usage. But nothing to explain this particular line.
|
Why is this Ethernet here? I am using wifi, not an Ethernet.
Because you're not capturing in monitor mode; on most operating systems, the only way to get 802.11 headers, rather than fake Ethernet headers, on a Wi-Fi capture is to capture in monitor mode. This includes Linux, OS X, and Windows (although WinPcap doesn't currently support monitor mode).
If you only want to see traffic to and from your machine, you can capture without monitor mode. You won't see packets other than data packets.
If you want to see other traffic on your network, or want to see non-data packets, or want to see 802.11 headers, or want to see 802.11 headers and radio information (data rate, signal strength, etc.), you need to capture in monitor mode. However, in monitor mode, packets on a protected network (network using WEP or WPA/WPA2) will not be decrypted; Wireshark can decrypt them if you supply the network's password and, if the network uses WPA/WPA2, if you've captured the initial EAPOL handshakes for each device whose traffic you want to decrypt.
| Itcpdump output - why is it showing an Ethernet status? |
1,437,634,436,000 |
I am using Ubuntu 23.10 and an ethernet connection to my router. However, sometimes during the day, my Internet connection gets "lost" for periods that can reach 1 hour sometimes. I can still access the router admin page, but no any other page on the Internet. The Ethernet icon in my system is still as it is (displaying "Connected"), but I don't really have access to the Internet.
It usually happens every morning at 8:30 AM. Sometimes it happens in the afternoon at 1 PM, and sometimes at 8-10 PM as well.
I have checked with my other devices when this happens, and they can access the Internet just fine. So this is not an issue in my router, but perhaps, my Linux/computer. My ability to access the router admin page proves it is not a physical link issue.
How can I debug such a problem when it happens? I don't even know where to start looking.
user$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 04:(redacted_for_privacy):42:8a brd ff:ff:ff:ff:ff:ff
Another command:
user$ dig google.com
; <<>> DiG 9.18.18-0ubuntu2.1-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 440
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 243 IN A 216.58.212.46
;; Query time: 14 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Feb 22 21:30:10 +03 2024
;; MSG SIZE rcvd: 55
This is ip add output:
myusername$ ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 04:(redacted_for_privacy):8a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.55/24 brd 192.168.1.255 scope global noprefixroute enp8s0
valid_lft forever preferred_lft forever
|
Loopback Address
See: What is the use of a loopback address in IPv4?
A loopback address or 'localhost' is an IPv4 address that is reserved for something called a 'loopback'. For loopback, IP addresses ranging from 127.0. 0.0 to 127.255. 255.255. (i.e. from 0-255).
Class A network number 127 is assigned the “loopback” function.
This means that a data set sent by a higher-level protocol to a network 127 address should be taken back to the host. A data set sent to a network 127 address should never show up on any network. It is the host's address and is both run by and within the operating system or OS. You can find a loopback address on devices, networks, and even routers. The reason people need a loopback IP is that even without having a physical network in place, it gives a dependable way to evaluate the functionality of the Ethernet drivers and software.
With the above quote in mind, remember that by putting your Router in the mix you have now moved one level above the Loopback Address. Your Hosts file, needs to be updated to reflect that like so. I've now commented out the loopback addresses because your Private IP Address is now serving in the loopback address's place (See Also - RFC1918):
# /etc/hosts
## Distribution Specific Comments Here
## IPv4 Section Goes Below
192.168.1.55 myhostname.mydomainnameorISP.com myhostname localhost
## Ubuntu's Entries (IPv4)
# 127.0.1.1 myhostname
# 127.0.0.1 localhost
## IPv6 Section
# Only fill in if you need IPv6. You may need to convert your IPv4
# entries using one of the many online conversion tools
## This excerpt taken from RFC 1918-Section 3-Private Address Spaces
## The Internet Assigned Numbers Authority (IANA) has reserved the
## following three blocks of the IP address space for private internets:
## 10.0.0.0 - 10.255.255.255 (10/8 prefix)
## 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
## 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
## -- EOF --
The above hosts assignment assumes your router's DHCP server is assigning class C addresses. If not Please adjust. While in your router find the section for MAC Address Filtering. Assign your Redacted MAC address to the address now in the hosts file, and make sure the Accepted box is selected(Selecting Deny will lock you out, so be cautious/verify the setting before applying it). This ensures the DHCP server always assigns you the same IP address so that the hosts file only needs one modification. The lo interface at 127.0.0.1 is still usable but only serves as the transport method for data between the Private IP address in the hosts file, and the machine itself.
Need Clarification
Did your ISP give you a modem/router combo?
Are you using your own Router in spite of the combo?
If #2 is True, have you bridged the ISP's device?
Optional: Describe your network, i.e., Outside --> ISP Modem --> etc
Answer via comment here, or Edit your question above and we'll continue.
| Weird Internet disconnection issue on Linux and ethernet |
1,697,206,939,000 |
I have a freebsd which has the network interfaces as follows.
bxe0, bxe1, igd0 and igd1
I want to move them to names like eth0, eth1 and so on. I know that I can do it in the /etc/rc.conf
ifconfig_igb0_name=eth0
but during the boot time the network interfaces are still bxe0, bxe1 etc.
Is there any way I can change interface names I want before the kernel gets loaded ?
Thanks in advance
|
Interfaces are "kernel inventions"; they don't exist outside of the kernel.
So "can I give them different names before the kernel gets loaded" makes no sense – they don't exist before the kernel has initialized them.
| bxe0 and bxe1 to eth0 and eth1 respectively |
1,697,206,939,000 |
I just installed Centos7 on a desktop computer because I need this specific OS for compatibility with CAD software that I am using. The installation went fine but my internet isn't working. I researched things a bit:
Output of ifconfig -a doesn't show network cards and only shows: lo, virbr0 and virbr0-nic.
So I ran lshw -c network, and I can see my network cards with status *-network UNCLAIMED. Specifically, they are:
Intel(R) Ethernet Controller I225V
Realtek RTL8125 2.5 GbE Controller -- I bought this one after failing to get the Intel one to work :(
So I did some more research online, basically I just need to install the driver, right? So I went to elrepo here and I installed the following two packages:
For
Intel, I tried: kmod-ixgbe-5.12.5-2.el7_9.elrepo.x86_64.rpm
For Realtek, I tried: kmod-r8125-9.009.02-1.el7_9.elrepo.x86_64.rpm
I really thought the latter would work, especially when I found threads online with the same problem, and the solution was simply to install this driver. I now have literally no idea what to try next. The network card green light is flashing but I am unable to get it to work? Am I missing something? Is this the wrong driver? Any ideas for debugging are most appreciated.
Note lspci -n gives me the following codes for the two devices:
Intel: 8086:15f3
Realtek: 10ec:8125
|
OK, found the solution.
My machine had "secure boot" turned on which rejects any third-party drivers. I turned it off by using the following command, and as described in this answer.
sudo mokutil --disable-validation
| Can't get ethernet adapter to work on centos 7.9, I tried both Realtek RTL8125 and Intel I225V |
1,697,206,939,000 |
Is it possible to set a max number of clients on an ethernet-interface created with nmcli?
Example: I would like max 2 devices to get a successful connection, even if I add a network-switch and connect 10 devices.
|
That's not how Ethernet works; there's no "connections" in ethernet; that's a concept from two layers higher.
So, you could try to make a firewall behave in a way that limits specific kind of activity, e.g. the ability to send TCP/IP packets, to a certain number of IP addresses. This would probably mean writing a daemon or BPF script beyond my experience in the Linux networking stack, to monitor the number of clients.
But: What is the number of clients?
IP addresses? Do you mean IPv4 or IPv6? Everyone can just pick as many IP addresses as they like for themselves, and matter of fact, a lot of system services rely on temporary or auto-configured or default addresses. This is neither a good protection (I could steal the IP address of someone who currently has "allowance"), nor is it even superficially save against denial of service (2 lines of shell code give me a 10000 IP addresses on my interface, good night, neighbor!).
Ethernet MAC addresses? Same problem as IP, these can be picked arbitrarily, and especially in environment with moving equipment/wireless access, these are often randomized
Established TCP/IP connections to the service: now we're talking. Your service is itself in control of this, and could simply reject connections under circumstances that seem to be clear only to the service itself!
In all honesty, this sounds like an application-level problem you're trying to solve at some deeper layer in the network. But the deeper layers of the network were never meant for access control. Simply don't. Whatever the service is your clients access, make it have authentication and a notion of a session – and simply reject if the maximum number of sessions is exhausted.
| nmcli: limit number of active connections |
1,697,206,939,000 |
I have a TD-LTE wireless terminal which can be used as a external 4G network adapter. It is connected to computer through USB. When I'm using Debian 11, it can provide USB ethernet well. However, when I tried to use it in Arch. I can't access find the USB ethernet.
ip doesn't show the external device
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether f0:76:1c:08:1f:7b brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 48:51:b7:f5:a5:be brd ff:ff:ff:ff:ff:ff
Maybe Arch requires a special firmware or driver for the device. How can I find it?
lspci doesn't show the external device
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
In Arch, the device can provide 4G network well. I can connect to the WLAN it provides.
More details:
OS:Linux 5.17.8-arch1-1
computer:ThinkPad S3-S440
TD-TLE terminal vendor: Huawei
I've turned off USB3.0 mode.
|
Following Stephen Boston's comment, I solved this problem:
First, install 2 software:
pacman --sync usbutils usb_modeswitch
Then, get details about the external USB ethernet device (I found that it had been in Mass Storage mode):
$ lsusb --verbose
and find:
Bus 001 Device 003: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131
Couldn't open device, some information will be missing
Device Descriptor:
idVendor 0x12d1 Huawei Technologies Co., Ltd.
idProduct 0x14db E353/E3131
Change the mode of the device:
# usb_modeswitch --default-vendor 0x12d1 --default-product 0x14db --huawei-new-mode
It may work properly now.
Notes: I haven't study lsusb or usb_modeswitch in details yet. I just found this method worked on my computer.
| How to enable USB ethernet in Arch Linux? |
1,697,206,939,000 |
I recently revived a hp 700/RX x-terminal and I wanted to try and set it up for fun but I don't know how to make a x-Linux server to connect to. I also think I need a bnc connector to connect it. I do have a bnc Ethernet card to link the computers. I just want to know what Linux distro and what version I need how how to set it up.
I found this on Wikipedia https://en.wikipedia.org/wiki/X_terminal
|
Yes, X Terminals get connected to Unix (Linux) hosts via Ethernet.
1) Install the BNC Ethernet card and connect it to the Terminal.
2) Run wireshark on the interface of the BNC Ethernet card.
3) Power up the terminal. See what Wireshark shows you. You'll probably get a BOOTP/DHCP request.
4) If yes, then install a DHCP server on your Linux box. Configure it for a private IP subnet different from other subnets you use.
5) Power up the terminal again, see what happens this time. Some terminals may need firmware via BOOTP. If yours does, then it'll get difficult. If it doesn't and you see some X protocol stuff (XDMCP), then
6) Install a display manager on your Linux box (e.g. xdm), configure it for the remote X terminal (man xdm for details).
If everything works, you should see a login screen on the X terminal, and be able to login from that to your Linux box.
I may have forgotten some steps, but Wireshark will show you what's going on, and give you ideas what's missing and what needs to be fixed.
| How to use a x-terminal |
1,697,206,939,000 |
I'm trying to get a basic ethernet connection with Halibut 8.0.0
sa8155:~# ifconfig eth0 up
sa8155:~# udhcpc
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: sending select for 10.0.0.112
udhcpc: lease of 10.0.0.112 obtained, lease time 604800
/etc/udhcpc.d/50default: Adding DNS 75.75.75.75
/etc/udhcpc.d/50default: Adding DNS 75.75.76.76
It seems to get an ip address assigned via DHCP,
and the DNS address is comcast so it does appear to be hitting my comcast router
sa8155:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:b6:e9:de:7a
inet addr:10.0.0.112 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: 2601:647:4201:a2b0:250:b6ff:fee9:de7a/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128 errors:0 dropped:0 overruns:0 frame:0
TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22180 (21.6 KiB) TX bytes:25954 (25.3 KiB)
but I cannot ping other computers on my network
sa8155:~# ping 10.0.0.196
PING 10.0.0.196 (10.0.0.196): 56 data bytes
ping: sendto: Network is unreachable
sa8155:~#
nor can other computers on my network ping 10.0.0.112
😈 >ping 10.0.0.112
PING 10.0.0.112 (10.0.0.112): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
and my router has no record of device sa8155, so I'm skeptical that DHCP is actually working.
Here's what I see in /etc/resolv.conf:
sa8155:~# cat /etc/resolv.conf
# Generated by Connection Manager
sa8155:~#
It seems that the Connection Manager, known as connman, is controlled via connmanctl.
According to the AGL documentation https://wiki.automotivelinux.org/connman:
But "connmanctl services" returns an empty list for me:
sa8155:~# connmanctl services
sa8155:~# connmanctl technologies
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = True
Connected = False
Tethering = False
sa8155:~#
According to this cheatsheet, the list should look something like this:
I'm not sure how to resolve this.
|
In a default installation, ConnMan will connect to a wired ethernet connection without any additional setup or interaction. It monitors kernel network interface events and brings the interface up automatically, including setting a default gateway and default routes. It also has built into it a dhcp client and dns forwarder. Having said that, it all depends on how AGL Halibut has compiled/configured it. Unfortunately, I am not familiar with that distribution.
For your reference, typically, an installation of ConnMan includes a symlink from /etc/resolv.conf to /var/run/connman/resolv.conf. The contents of the file is
# Generated by Connection Manager
nameserver 127.0.0.1
You can find the status of your network interfaces using the ip address command.
It may also be useful to look in the logs generated by ConnMan. You may want to stop connman (depends on the init system, or just kill the connmand process). Then run it from the command line to see what is happening.
| How do I get an ethernet connection with Automotive Grade Linux (Halibut 8.0.0)? |
1,697,206,939,000 |
Is there any tools to get the information about status of data receiving and sending in Ethernet (Real-time information is better, GUI tools is better)?
The information includes:
sending and receiving rate (Mbps)
total data sending and receiving since start the machine (this is optional)
|
There are several available. A full-fledged network tool is iptraf (http://iptraf.seul.org/).
Otherwise, nload is a tool that just shows network bandwidth usage, in a simple and neat way.
If you want to run network benchmarks, look for netserver/netperf or iperf.
| How to get the information about the status of data receiving and sending in ethernet? |
1,697,206,939,000 |
I want to configure an IP camera which is in my raspberry pi's ethernet port (I connect to it through wifi).
I connected the camera and this is what I see when I run ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:a2:10:08
inet addr:169.254.248.2 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::ce99:232c:964e:7070/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5600 errors:0 dropped:0 overruns:0 frame:0
TX packets:27715 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3219770 (3.0 MiB) TX bytes:10481558 (9.9 MiB)
So it means my raspberry pi has the IP address 169.254.248.2. I tried accessing 169.254.248.1 and scanning with nmap 169.254.0.0/16 but the only host up that I see is the raspberry pi itself.
I then run tcpdump on eth0:
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
03:13:53.963493 IP (tos 0x0, ttl 64, id 13074, offset 0, flags [none], proto UDP (17), length 368)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:a2:10:08 (oui Unknown), length 340, xid 0x252200b7, secs 65535, Flags [none]
Client-Ethernet-Address b8:27:eb:a2:10:08 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Client-ID Option 61, length 7: ether b8:27:eb:a2:10:08
SLP-NA Option 80, length 0""
NOAUTO Option 116, length 1: Y
MSZ Option 57, length 2: 1500
Vendor-Class Option 60, length 44: "dhcpcd-6.7.1:Linux-4.9.48-v7+:armv7l:BCM2835"
Hostname Option 12, length 11: "raspberrypi"
T145 Option 145, length 1: 1
Parameter-Request Option 55, length 14:
Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
Domain-Name-Server, Hostname, Domain-Name, BR
NTP, Lease-Time, Server-ID, RN
RB, Option 119
Which looks like my raspberry pi is trying to find an IP to itself. I didn't hear anything from the camera. Shouldn't I get its broadcast messages trying to get an IP?
Ok, so I continued and installed https://help.ubuntu.com/community/isc-dhcp-server with the following configuration file:
# Sample /etc/dhcpd.conf
# (add your comments here)
default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 169.254.248.255;
option routers 169.254.248.254;
option domain-name "mydomain.example";
subnet 169.254.248.0 netmask 255.255.255.0 {
range 169.254.248.10 169.254.248.100;
}
It should make the dhcp client of the camera request an address and get 169.254.248.10, right?
None of this worked, so I started to remember a few things about this camera:
They come preconfigured to work at 192.168.1.x, and with a fixed IP (which I don't know what is).
Does this mean that the camera will never work at my ethernet port, unless I make the ethernet address be in the 192.168.1.x range?
Shouldn't I receive broadcast messages from the camera, even if I'm on a different subnet and even if its IP is fixed? I think I should received ARP brocadcast messages informing in which IP it is, something like that, right? Yet I don't hear anything coming from the camera when I do tcpdump -i eth0
If the answers to these last two questions are false, then can I make my ethernet port work on the 192.168.1.x range, even though my wlan0 interface is already working on it? (I mean, could I at least do it in a virtual way just to talk with the camera? Since it's raw ethernet, I could fake that eth0 is on 192.168.1.x just to fool the camera). I'm asking this because all I'm doing is remote, I can't mess with the wlan configurations, and can't put it into a different subnet.
|
With no hub or switch you need to use a crossover cable. You can make a cable that is crossed, make a cable with a female RJ45 connector that is crossed, put 2 RJ45 connectors together (a 2 port hub!), etc.
Once that is done the automatic addressing may work, or check the manual for the camera it may have a default static IP set.
If you know the IP is in the 192.168.1.x subnet, set your Pi to something in that range and then port scan or ping scan the subnet.
ifconfig eth0 192.168.1.131 netmask 255.255.255.0
| How to talk with IP camera through ethernet directly (no switch, hub, routers...). Different subnets in camera and ethernet's port |
1,697,206,939,000 |
I have a dedicated server ubuntu 16.04 OS / 8 GB Ram, with over 5000 IPv6 from /48 subnet assigned to using below command
ip -6 addr add IPv6/48 dev eth0
creating massive parllel connections cycling between these different IPs each run for my crawling project,
problem is server provider messaged me about high load on the switch, that affects other users on the device
and the only solution would be create a virtual router/switch on server that we can direct route the entire /48
Any help ?
Edit1:
i assigned ipv6 to lo interface using
ip -6 addr add IPv6/48 dev lo
It's working perfectly, Thanks
|
[...] high load on the switch [...] that we can direct route the entire /48
Reading between the lines, the only thing I can think of that they could possibly have in mind is IPv6 neighbour discovery table overload. If this is what they are thinking about, then they can indeed direct route the whole /48 to you and this will be better and easier for both you and them.
I can't think of any possible reason you would need to create anything resembling a "a virtual router/switch" though. If the /48 were directly routed to you then you could just add all your IP addresses to, say, lo instead of eth0, and everything should work.
ip addr add IPv6/48 dev lo
| how to create virtual router/switch on Ubuntu server |
1,697,206,939,000 |
I have installed Kali on my raspberry pi. I've managed to connect to it through ssh using Putty, but I cannot access the Internet.
To be more specific, I can neither update/upgrade nor can I ping www.google.com but I can however ping 8.8.8.8.
The PI and my desktop are connected to the same router.
I have checked the routes, the gateway, the interface, I have changed the cable thinking that it might be the physical link but nothing works. Any suggestions ?
root@kali:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.105 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2a02:2f09:33ba:d200:ba27:ebff:fe54:38fd prefixlen 64 scopeid 0x0<global>
inet6 fe80::ba27:ebff:fe54:38fd prefixlen 64 scopeid 0x20<link>
inet6 fdf8:b85b:7d29:0:ba27:ebff:fe54:38fd prefixlen 64 scopeid 0x0<global>
ether b8:27:eb:54:38:fd txqueuelen 1000 (Ethernet)
RX packets 561 bytes 39987 (39.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 294 bytes 42374 (41.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@kali:~# ping www.google.com
PING www.google.com(bud02s24-in-x04.1e100.net (2a00:1450:400d:803::2004)) 56 data bytes
^C
--- www.google.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6007ms
root@kali:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=11.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=13.1 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=11.8 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=12.6 ms
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 11.844/12.764/14.216/0.880 ms
P.S. I have connected the same device with the same OS to a different router at a friend of mine and it worked without any adjustments.
|
Your problem is a lack of IPv6 connectivity.
As your Pi is getting an IPv6 address assigned to it, the system will prefer to use IPv6. However, for whatever reason, you can not get an outbound internet connection.
Ideally, you would check your router and other computers, and make sure IPv6 is working on them. But, in the meantime, you can just disable it.
To do this, add the following line to /etc/sysctl.conf and reboot:
net.ipv6.conf.eth0.disable_ipv6 = 1
Upon your system coming back online, IPv6 will be disabled and you should be able to establish a normal connection to any IPv4 website.
| Connecting Kali to the Internet |
1,697,206,939,000 |
What happens when a router does not find the proper destination network from routing table? Can anyone help me with this problem?
|
I'm assuming we're talking about TCP/IP here.
The router will use its default route if one is defined. Otherwise it should drop the packet and send an ICMP 'destination unreachable' message to the originator.
| What happens when a router does not find the gateway? [closed] |
1,697,206,939,000 |
I'm trying to connect two PCs in a local network and I am having difficulties. Some information about my setup:
pc1: OS GNU/Linux Mageia
pc2: OS GNU/Linux Debian
pc1 pings to pc2 with no problem, but pc2 ping to pc1 fails. This is the out console in pc2->
data for pc2:
ping -I eth0 100.10.2.104
PING 100.10.2.104 (100.10.2.104) from 100.10.2.103 eth0: 56(84) bytes of data.
^C
--- 100.10.2.104 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5040ms
other data:
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 100.10.2.1 0.0.0.0 UG 0 0 0 eth0
100.10.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
ifconfig
eth0 Link encap:Ethernet
inet addr:100.10.2.103 Bcast:100.10.2.255 Mask:255.255.255.0
data for pc1:
ping -I eth0 100.10.2.103
ping ok
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 100.10.2.1 0.0.0.0 UG 0 0 0 enp2s0
100.10.2.0 0.0.0.0 255.255.255.0 U 0 0 0 enp2s0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 enp2s0
ifconfig
eth0 Link encap:Ethernet
inet addr:100.10.2.104 Bcast:100.10.2.255 Mask:255.255.255.0
We have done several things including sysctl -w net.apv4.ipforward=1 and sysctl -w net.apv4.ipforward=0 on both computers and nothing all the same
What could be my mistake that causes pc2 not to receive the packages?
thanks for reading and apologize for my bad English
|
That doesn't seem to be the usual local network address - they usually start with 10.0.0.0/8 or 172.16.0.0/16 or 192.168.0.0/16. 100.10.2.103 & 104 goes to some Verizon server in Kansas & New Jersey respectively. Maybe your local network start with 10 instead of 100?
| Error while trying to connect 2 pcs in lan |
1,697,206,939,000 |
Like the headline says: is this possible in Linux at all? How would one implement a completely silent packet sniffer? I would like to take the interface away and give it back to the OS at will, if this is possible. Currently the OS gets in the way because eth0 being the only network interface on the machine in question, Linux tries to ask for connectivity by DHCP.
|
Yes, this is at least partially possible.
First, you need to figure out the "interface name" of the interface. The command ifconfig -a (possibly /sbin/ifconfig -a) shows you all the interfaces. Choose wisely.
Second, you have to identify and stop the process that's using DHCP on that interface. This could be dhcpcd, dhclient or maybe even pump. Run ps -ef to try to identify the process IDs of such processes. Use kill -QUIT to stop them. Bear in mind that your setup may restart the DHCP client at the next reboot.
You should look in /var/run to find "PID files". For instance, my Arch linux laptop has a file /var/run/dhcpcd-wlp12s0-4.pid which contains the process ID of the dhcpcd process that manages the "wlp12s0" interface. That's a wireless card, but the same sort of file will exist for an ethernet card.
If you're hoping to sniff wireless packets, you're better off using [kismet][1] or [airodump-ng][2]. Follow the tutorials - usage isn't exactly easy or obvious.
If you're hoping to sniff ethernet packets without being detected, you should be aware that some controversy exists about whether this is possible or not. Using a "read only" cable would prevent some of the methods of promiscuous-mode interface detection. This method worked for me, some people say it doesn't work all the time. You do need two ethernet interfaces to read traffic going both ways.
| Possible to reserve a network interface for exclusive use? |
1,697,206,939,000 |
Intel Motherboard GA-H61N-D2V
$ pciconf -l -v
re0@pci0:1:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x06 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
class = network
subclass = ethernet
FreeBSD 8.2 RELEASE
# uname -a
FreeBSD qb91.anybots.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 [email protected]:/usr/obj/usr/src/sys/GENERIC i386
Kernel message
re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfbdff000-0xfbdfffff,0xfbdf8000-0xfbdfbfff irq 16 at device 0.0 on pci1
re0: Using 1 MSI messages
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00000000
re0: Unknown H/W revision: 0x2c800000
... when firing ifconfig, re0 doesn't show up.
Unfortunately upgrading FreeBSD is not an option, I must stick to 8.2 RELEASE.
How may I troubleshoot/fix this issue?
UPDATE - COMPILED NEW DRIVER
Followed steps in this thread.
On FreeBSD 8.2 RELEASE Virtual Machine, I recompiled the kernel.
Then I collected if_re.ko and if_re.ko.symbols and copied them onto the machine that has the problem in /boot/kernel/ folder.
After a reboot the problem persists.
UPDATE - LOADER.CONF
Add if_re_load="YES" in /boot/loader.conf
# kldstat
Id Refs Address Size Name
1 43 0xc0400000 bd97b4 kernel
2 1 0xc0fda000 1126c if_run.ko
3 1 0xc0fec000 4be0 umodem.ko
4 1 0xc0ff1000 e618 snd_uaudio.ko
5 3 0xc1000000 56794 sound.ko
6 1 0xc1057000 2c38 coretemp.ko
7 1 0xc105a000 c108 ahci.ko
8 1 0xc1067000 4c04 cuse4bsd.ko
9 1 0xc106c000 3ce0 runfw.ko
10 1 0xc1070000 3c98 uanypkt.ko
11 1 0xc1074000 69d4 usie.ko
12 1 0xc4f0f000 9000 tmpfs.ko
13 1 0xc51b0000 26000 linux.ko
Still no luck.
Also tried loading manually:
# kldload -v /boot/kernel/if_re.ko
kldload: can't load /boot/kernel/if_re.ko: File exists
Not sure what this means, I suppose it means that it was loaded (?)
# kldstat -v | grep ko
2 1 0xc0fda000 1126c if_run.ko (/boot/kernel/if_run.ko)
3 1 0xc0fec000 4be0 umodem.ko (/boot/kernel/umodem.ko)
4 1 0xc0ff1000 e618 snd_uaudio.ko (/boot/kernel/snd_uaudio.ko)
5 3 0xc1000000 56794 sound.ko (/boot/kernel/sound.ko)
6 1 0xc1057000 2c38 coretemp.ko (/boot/kernel/coretemp.ko)
7 1 0xc105a000 c108 ahci.ko (/boot/kernel/ahci.ko)
8 1 0xc1067000 4c04 cuse4bsd.ko (/boot/modules/cuse4bsd.ko)
9 1 0xc106c000 3ce0 runfw.ko (/boot/kernel/runfw.ko)
10 1 0xc1070000 3c98 uanypkt.ko (/boot/modules/uanypkt.ko)
11 1 0xc1074000 69d4 usie.ko (/boot/modules/usie.ko)
12 1 0xc4f0f000 9000 tmpfs.ko (/boot/kernel/tmpfs.ko)
13 1 0xc51b0000 26000 linux.ko (/boot/kernel/linux.ko)
UPDATE - re0 is not UP
Instead of copying only if_re.ko files, I ended up copying the whole kernel directory
Now the adapter is UP and get an address assigned
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
ether 74:d4:35:12:ce:d6
inet 10.10.99.115 netmask 0xffff0000 broadcast 10.10.255.255
media: Ethernet autoselect (none)
status: no carrier
But I still get these messages from the kernel, which bothers me a little. Looks like the re0 is not entirely recognized.
# dmesg | grep re0
re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfbdff000-0xfbdfffff,0xfbdf8000-0xfbdfbfff irq 16 at device 0.0 on pci1
re0: Using 1 MSI messages
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00000000
re0: Unknown H/W revision: 0x2c800000
device_attach: re0 attach returned 6
re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfbdff000-0xfbdfffff,0xfbdf8000-0xfbdfbfff irq 16 at device 0.0 on pci1
re0: Using 1 MSI-X message
re0: turning off MSI enable bit.
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
re0: Ethernet address: 74:d4:35:12:ce:d6
re0: [ITHREAD]
re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfbdff000-0xfbdfffff,0xfbdf8000-0xfbdfbfff irq 16 at device 0.0 on pci1
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
re0: Ethernet address: 74:d4:35:12:ce:d6
re0: [ITHREAD]
re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xee00-0xeeff mem 0xfbdff000-0xfbdfffff,0xfbdf8000-0xfbdfbfff irq 16 at device 0.0 on pci1
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
re0: Ethernet address: 74:d4:35:12:ce:d6
re0: [ITHREAD]
|
I don't think this revision of the chipset is supported by the stock re driver in version 8.2-RELEASE or earlier. You can grab a back-ported version of the driver and rebuild your kernel to include it. A quick search of the FreeBSD mailing list archive turns up this thread, which has links to the updated driver files. If you need pointers on rebuilding your kernel, Chapter 9 in the FreeBSD Handbook is a good starting point.
| FreeBSD Ethernet NIC driver not recognized |
1,688,462,176,000 |
Rocky Linux 8 X86-64 on a PC with two Ethernet interfaces, each connected to isolated switch hub, then connect to router.
LAN1: 192.168.1.2/24 <--> Hub1 <--> 192.168.1.1 (Router port #1)
LAN2: 192.168.2.2/24 <--> Hub2 <--> 192.168.2.1 (Router port #2)
|
+------> Laptop (192.168.2.100/24, GW=192.168.2.1)
(P.S.: I've already stripped out all the other cables so the real world environment is what exactly shown in the picture above. And I don't think there is any Loop)
Both LAN1 and LAN2 have set corresponding Gateway correctly. The router have static route rule (port#1 <--> port#2) setup correctly, too. There is another Laptop connected to Hub2 and set IP to 192.168.2.100/24, GW=192.168.2.1.
The problem is: I can't connect to 192.168.1.2 from the Laptop, unless I disable LAN2 network interface on Rockey Linux. Even PING won't response.
More details:
If I disable LAN2, I'd be able to access 192.168.1.2 from the 192.168.2.0/24 subnet without any problem.
Just unplug the cable from Hub doesn't work. I have to completely disable the network interface with nmcli/nmtui to make LAN1 being able to response.
If I continuously PING from the Laptop, it will stop responding the moment when I re-enable LAN2 again.
All the PC, laptop and router can PING each other on the 192.168.2.0/24 subnet without problem, so it can’t be ARP related issue.
It seems as though the operating system is making an excessive effort to send the response packet via LAN2 (which is not even the default gateway) instead of using the interface that originally received the packet.
The default route table looks like this:
Destination Gateway Genmask Flag Metric Iface
default _gateway 0.0.0.0 UG 102 ens18
192.168.2.0 0.0.0.0 255.255.255.0 U 101 en1sf31
192.168.1.0 0.0.0.0 255.255.255.0 U 102 ens18
I've no idea what's going on.
For some reason I'd need to access 192.168.1.2 from 192.168.2.0/24 subnet while keeping both network interface alive.
Please help.
|
Short answer:
sysctl -w net.ipv4.conf.all.rp_filter=2
To make this change persistent across reboots, add it to /etc/sysctl.conf .
Full answer: https://access.redhat.com/solutions/53031
Simply put, the packet is dropped by Rocky Linux, due to "Strict Reverse Path Forwarding filtering" recommended in RFC 3704. Disabling it or set it to loose solve the problem.
See also: https://serverfault.com/questions/967863/routing-from-one-server-to-another-with-different-interfaces
| Can't have two network interface enabled at the same time? |
1,688,462,176,000 |
I am configuring a PC network with netplan and the following configuration:
only one ethernet device with MAC address 48:b0:2d:d3:d1:c4, and an USB-to-ethernet adapter.
I need the ethernet device (eth0) to have a static IP 192.168.0.50, and the usb-to-eth adapter (ethX) to have a static IP 192.168.1.50.
My netplan configuration is the following:
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: false
dhcp6: false
match:
macaddress: 48:b0:2d:d3:d1:c4
set-name: eth0
optional: false
addresses:
- 192.168.0.50/24
routes:
- to: default
via: 192.168.0.1
on-link: true
eth1:
dhcp4: false
dhcp6: false
optional: false
addresses:
- 192.168.1.50/24
However, after rebooting the system, the following configuration is set:
$ ip addr
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:4c:68:00:2a brd ff:ff:ff:ff:ff:ff
5: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 48:b0:2d:d3:d1:c4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.50/24 brd 192.168.1.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::4ab0:2dff:fed3:d1c4/64 scope link
valid_lft forever preferred_lft forever
networkd is setting to the device with mac address 48:b0:2d:d3:d1:c4 the eth1 name and the wrong IP, when it should be eth0 and IP 192.168.0.50.
I tried using also NetworkManager, but the result is the same.. That's why I changed to networkd in the first place.
I have checked also that NetworkManager service is off, and, indeed, it is disabled and off. Also, I have checked there are no rules on /etc/systemd/network.
What makes me wonder is why the eth0 seems to be DOWN.. Do you know what I am missing?
Thanks in advance!
|
You assert that eth0 has MAC address 48:b0:2d:d3:d1:c4 in your configuration - but when your machine is rebooted it is seeing that the first NIC (eth0) has mac address 00:e0:4c:68:00:2a and hence is not using the address 192.168.0.50/24
If you really want eth0 to have that IP address, change the MAC address in your config. OTOH of you want the MAC address to match the IP address, swap the names eth0 and eth1 about in your config.
| netplan does not assign static ip to the eth0 |
1,688,462,176,000 |
System Specs: i7-12700k, RTX 3060, 80 (2X32, 2X8) GB DDR4-3200 RAM, 1 TB M2 NVME SSD
OS: Ubuntu 20.04 LTS, kernel version 5.2.21-050221-generic
Context:
My Motherboard doesn't have WiFi, so I use TP-Link Archer T9UH USB WiFi adapter for WiFi. Unfortunaly, 5.2.21 is the latest kernel version supported by the open source driver for the WiFi adapter. I had installed the 510.60 version of the Nvidia Driver a few months ago. I did not see any issues for a few months. Yesterday, I noticed that the Nvidia Driver is not working.
When I entered: nvidia-smi in the terminal, I got this error:
Failed to initialize NVML: Driver/library version mismatch
I then tried to reinstall the Nvidia Driver 515.76, it broke and when I rebooted, I got a blank screen. Then I tried again, The installation seemed sucessful and when I rebooted, both my Wifi and the ethernet drivers were broken? Then I noticed that the Files was showing Filesystem root and efi as mounted drives, and the GUI was very buggy and slow. It froze and took 10 minutes to move small files when using the GUI.
I am in a but of a pickle. I don't even know where to start. How do I even diagnose the problems here?
I will add any command output in a Edit if needed.
EDIT:
I downloaded the Nvidia Driver 520.56.06 as mentioned by Artem, directly form the Nvidia website , and Installed it.
But Immediately after the installation, My screen went completely black except for a underscore cursor in top left side of the screen.
EDIT_1:
After force Rebooting, The Nvidia Drivers seem to be working. But, the WiFi and ethernet problems are persisting.
|
I have solved the Issue. All these problems occuring together is not a coincidence. I think the kernel version I was using, 5.2.21, was simply too old.
I downloaded the 5.4.x kernel, installed it and booted into it.
This was where I found the files: https://kernel.ubuntu.com/~kernel-ppa/mainline/
You would need 4 .deb packages with the correct cpu architecture (amd64 for Intel/AMD):
linux_headers-5.4.x-xxx_all.deb
linux_headers-5.4.x-xxx-generic/lowlatency_xxx.deb
linux_modules-5.4.x-xxx-generic/lowlatency_xxx.deb
linux-image-unsigned-5.4.x-xxx-generic/lowlatency_xxx.deb
download these manually if you have to and put all of these packages in a signle folder on the target system.
Then install the kernel packages by running the command:
sudo dpkg -i *.deb
Reboot and while rebooting, choose the correct kernel version.
check this by the following command:
uname -r
| Wifi, Ethernet, Graphics Drivers, file system are all buggy. Are these issues related? |
1,688,462,176,000 |
I know Linux pretty well, and I know how to use Kali Linux. But when I boot it, it can't connect to my wifi AC.
Apparently, to fix this there's some stuff about ethernet cables and access the wifi and run installation commands...
While I know security research and Linux, I don't know a thing about using ethernet. I've tried to connect it to another computer and whatnot and it doesn't work. All other distros I've tried connect to my wifi adapter just fine.
Ultimately, is there a way I can fix this without fidgeting with ethernet?
Note: It has a message in the installer boot where it asks for the driver files. 1: I don't know where to find them and 2: I don't know how to give them.
My wifi AC is:
Intel(R) Dual Band Wireless-AC 7265
Please help me.
|
Solve: Plug the computer into ethernet while running the installer drive. It does the rest on it's own.
| Installing Kali Linux wifi AC driver without ethernet |
1,688,462,176,000 |
Linux noob here (starting out). I had a couple successful install trials before and now I am settling on with one configuration. I have now failed to get my network card to work.
Desktop PC, very old system -
AMD Phenom II 955,
Gigabyte GA-MA790XT-UD4P
The driver I am interested in is this:
GBE Ethernet LINUX driver r8168 for kernel up to 5.17
for a background: I had used USB-Ethernet dongle to try out some of the r8168 install tutorials and dnf upgrade had updated my kernel from fresh install's 5.17 to 5.18. -> I thus suspect kernel inconsistencies but how to rework this ?
The kernel is using r8169 drivers (lspci -v), which I know doesn't work for my system! Using the driver's included autorun.sh did work for fedora 35 (I believe like half a year ago) and I have also successfully been able to install the r8168 drivers previously on Ubuntu.
Doing "$ sudo ./autorun.sh" from the folder gets me this output:
Check old driver and unload it
Build the module and install
make[2]: *** /lib/modules/5.18.5-200.fc36.x86_64/build: No such file or directory. Stop.
make[1]: *** [Makefile:158: clean] Error 2
make: *** [Makefile:48: clean] Error 2
Thus I somehow need to force the Fedora to use r8168 instead, but I can't figure out how - WITHOUT having internet access (duh, because the GBE Ethernet card is not working). AND I want this solution to work afterwards with no USB-Ethernet dongle.
I checked the that location and it lists the build file, but opening 'build' pops-up a dialog:
The link "build" is broken.
This link cannot be used because its target "usr/src/kernels/5.18.5-200.fc36.x86_64" doesn't exist
EDIT:
Managed to install kernel-devel for 5.18.6-200* and all dependencies.
Now when running driver's autorun.sh I get this output:
Check old driver and unload it.
Build the module and install
/home/am/Documents/r8168-8.050.03/src/r8168_n.c: In function ‘rtl8168_mac_loopback_test’:
/home/am/Documents/r8168-8.050.03/src/r8168_n.c:3717:17: error: implicit declaration of function ‘pci_dma_sync_single_for_device’; did you mean ‘dma_sync_single_for_device’? [-Werror=implicit-function-declaration]
3717 | pci_dma_sync_single_for_device(tp->pci_dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| dma_sync_single_for_device
/home/am/Documents/r8168-8.050.03/src/r8168_n.c: In function ‘rtl8168_init_board’:
/home/am/Documents/r8168-8.050.03/src/r8168_n.c:26448:14: error: implicit declaration of function ‘pci_set_dma_mask’ [-Werror=implicit-function-declaration]
26448 | !pci_set_dma_mask(pdev, DMA_BIT_MASK(64)) &&
| ^~~~~~~~~~~~~~~~
/home/am/Documents/r8168-8.050.03/src/r8168_n.c:26449:14: error: implicit declaration of function ‘pci_set_consistent_dma_mask’ [-Werror=implicit-function-declaration]
26449 | !pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(64))) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:288: /home/am/Documents/r8168-8.050.03/src/r8168_n.o] Error 1
make[2]: *** [Makefile:1842: /home/am/Documents/r8168-8.050.03/src] Error 2
make[1]: *** [Makefile:154: modules] Error 2
make: *** [Makefile:41: modules] Error 2
Any great ideas to try out ?
The closest topics covering this I found were:
How to build "akmod-r8168" driver kernel module package for fedora?
This doesn't state how the install was actually done, thus I have no idea how to apply this.
https://tutorialforlinux.com/2021/05/04/step-by-step-fedora-34-realtek-rtl81168-driver/2/
This ASSUMES I can access internet to do dnf upgrade's and stuff - no-go.
|
As I can't approve comments as answers...
Posting that booting/reverting back to at least 5.17.5 kernel version made the (latest at this time) Realtek driver work.
Seems I have a bug to report.
Thanks @Artem for suggestions and help in the comments.
| Installing realtek r8168 on Fedora 36 (5.18.5)? |
1,688,462,176,000 |
So let me preface this question by stating that I am not so well versed in the linux ways hence simple explanations are appreciated. On to the question at hand.
Question
I am currently running an Arch Linux server (selected the server option in the archinstall script) its mostly to run docker containers, its connected to the internet using WiFi. I recently decided to connect some of the devices to the server via a network switch (it's an unmanaged/plug-and-play switch). Since the network switch is unmanaged I know that I need to manually assign ip address to the devices connected to it. The problem is that I can, at any given point, only get one of the 2 networks working fine on the system.
If I configure the Ethernet then the WiFi network no longer has access to the internet (still connected to the WiFi network, just no internet access). If I disable the Ethernet then then I have internet access but no access to the devices connected in the wired LAN. How do I solve this so that both networks are connected and still have access to the internet?
What I tried:
I followed the guide found here. I tried both the netctl method and the systemd method. I would like to say that I had more luck with the netctl method for a static IP for the Ethernet network, but that's just because it's easier to do.
Since netctl can also be used to connect to a WiFi network I tried to use that to connect to the WiFi instead of iwctl, I figured maybe its not working cause its 2 different scripts/programs managing them. But that didn't work as netctl just didn't connect to the WiFi network. I used the examples provided by them, "wireless-wpa", and tweaked the contents to match what I had. At first it didn't work cause the passkey was getting rejected, so I got the encrypted passkey using "wpa_passphrase" and used that, but that didn't work either. It just said 'wpa authentication failed' (might not be exactly that, I did revert everything before typing the question, so the details are a bit off in error messages)
I did think maybe I was changing too much of what the netctl ethernet example had so here's an example of what it looked like after my changes
Description='A basic static ethernet connection'
Interface=enp0s26
Connection=ethernet
IP=static
Address=('192.168.1.102/24')
Gateway=('192.168.1.1')
DNS=('8.8.8.8' '8.8.4.4')
+ whatever was there after DNS (I didn't touch those)
Yes, all I did was change the interface name but I figured I should show what the config I used was.
How Did I Check the Connections:
I used ping.
Check for internet access was ping www.google.com.
Check for ethernet connection was ping 192.168.1.22 (IP I set for my windows machine)
Misc.
the netctl example for static IP ethernet has a different IP for DNS. I did try that as well. But no dice there, I'm pretty sure it looked like this:
Description='A basic static ethernet connection'
Interface=enp0s26
Connection=ethernet
IP=static
Address=('192.168.1.102/24')
Gateway='192.168.1.1'
DNS=('192.168.1.1')
+ whatever was there after DNS (I didn't touch those)
As I started typing in the Title for the question I did run across this Stack Exchange question, but I have no idea whats going on there.
|
So I have, since posting the question, figured out the reason I wasn't able to use netctl to set up both connections, it was a routing problem. I used the instructions here to change the routing scheme the system used and it works.
Well not 100% working, but that's just an issue with netctl not being able to autostart with system cause the interfaces are already up but that's a different question.
| Connecting To a WiFi with dynamic IP and Ethernet Cable with Static IP in Arch Linux and Maintaining Internet |
1,688,462,176,000 |
I want to permanently change the device name of a network interface using a portable script.
The interface gets the ugly name of enp02fghjkl1. I want to give a pretty name of netface1. I have tried using ip link and nmcli and so many other things to change the device name permanently, and I can change it, but I cannot get it to persist through a reboot.
Here is the command set that works to temporarily change it:
sudo ip link set enp02fghjkl1 down
sudo ip link set enp02fghjkl1 name netface1
sudo nmcli connection modify Wired\ connection\ 1 con-name netface1
sudo nmcli device connect netface1
sudo nmcli con up netface1
sudo nmcli con reload
However, after a reboot, the command nmcli c shows netface1 but the command nmcli d shows enp02fghjkl1
Note: I have also created a network-script called ifcfg-netface1 and placed the uuid in it, but it just gets ignored after a reboot.
|
Step 1.
The robust solution that worked for me:
These four lines that must exist in the network-script file:
/etc/sysconfig/network-scripts/ifcfg-somename1
NAME=somename1
DEVICE=somename1
HWADDR=FE:FF:GG:11:00:10
UUID=b623cbaa-ffe2-3456-7890-1a23b465cd67
Caveat: The file cannot have HWADDR and MACADDR at the same time, it can only have one or the other. You can get the UUID from the command nmcli c.
Step 2.
add net.ifnames=0 somewhere after nomodeset and before rhgb in this file:
/etc/default/grub
then run the command sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Step 3.
Match the MAC address to the nic name in this file:
/etc/systemd/network/70-custom-ifnames.link
[Match]
MACAddress=FE:FF:GG:11:00:10
[Link]
Name=somename1
Step 4.
Add these lines to the custom rules file:
/etc/udev/rules.d/70-custom-ifnames.rules
SUBSYSTEM=="net",ACTION=="add",ATTR{address}=="FE:FF:GG:11:00:10",ATTR{type}=="1",NAME="somename1"
More details here:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking
| How can I permanently change a network device name in CentOS8? |
1,688,462,176,000 |
I am relatively new to Linux, and I am using Mint 20.2, on an HP Elitebook 840 G7.
I have bought a TP-Link USB-to-Ethernet adapter, based on the ASIX AX88179 chipset:
USB 3.0 to Gigabit Ethernet Network Adapter
I have been able to (compile and) install the driver, and the device is correctly listed in the system report.
However, the adapter does not work.
I am aware that I need to create a new Network Interface for the device, but I don't know how.
Among other things, I don't know how to read the MAC address of the device, to follow the instructions of this post:
How to set up an usb/ethernet interface in Linux?
This page seems also useful, but it is too much for me:
Adding new, undocumented features into a kernel driver
Thanks in advance for any help!
|
The problem has been solved by updating the system to Linux Mint 20.3!
| Using USB to Ethernet adapter (ASIX AX88179 driver) on Linux Mint 20.2 |
1,688,462,176,000 |
I installed CentOS 7 minimal on a server. It has two NICs.
However, one of them doesn't appear to be working. It also appears as UNCLAIMED.
Its not showing when i use commands to list network devices, like ifconfig and ip -a
The other nic installed is a PCI Express card. I cant get it to work...
Please, can someone help me?
ip link:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:23:ae:b6:65:cd brd ff:ff:ff:ff:ff:ff
lshw -class network:
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 02
serial: 00:23:ae:b6:65:cd
size: 100Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full ip=192.168.17.12 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
resources: irq:18 ioport:d800(size=256) memory:feaff000-feafffff memory:fdff0000-fdffffff memory:feac0000-feadffff
*-network UNCLAIMED
description: Ethernet controller
product: VT6120/VT6121/VT6122 Gigabit Ethernet Adapter
vendor: VIA Technologies, Inc.
physical id: 0
bus info: pci@0000:03:00.0
version: 82
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list
configuration: latency=0
resources: ioport:e800(size=256) memory:febffc00-febffcff
|
i just want everyone that is reading this that the solution for me was switching the network card.
It was a problem with the NIC itself. I tested in another OS just to be sure. Tested on Windows to be more assertive, since Linux do have some problems with drivers in some ocassions, and i got to the conclusion that the problem was with the network card itself since even with a Windows OS + With drivers it wasnt working.
After changing the NIC to a newer one everything worked fine.
| CentOS 7 is not detecting my network card, listing as UNCLAIMED |
1,688,462,176,000 |
About 2 weeks ago I installed an antivirus (ESET nod32) on my Mint 20.1 server. However, after discovering that it is not at all optimized for Linux (blocked basically all my ports + connections and provided no firewall manager), I uninstalled it and my connections began working again. Recently, after toying around with setting up a Squid proxy server, my ethernet connection has stopped working again. Some diagnostics have shown that the server is detecting the connection, my driver is working just fine, and other devices connected to that router are having no issues; so I suspect it's a configuration issue. It's also worth noting that at the moment I am able to get a temporary connection with a USB wifi adapter.
Here's my output of inxi -Fxz:
System:
Kernel: 5.4.0-66-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa
base: Ubuntu 20.04 focal
Machine:
Type: Server System: Dell product: PowerEdge T320 v: N/A serial: <filter>
Mobo: Dell model: 0W7H8C v: A03 serial: <filter> BIOS: Dell v: 1.5.1
date: 03/08/2013
Battery:
Device-1: hidpp_battery_1 model: Logitech Wireless Mouse Dell WM514
charge: 55% (should be ignored) status: Discharging
CPU:
Topology: Quad Core model: Intel Xeon E5-2407 0 bits: 64 type: MCP
arch: Sandy Bridge rev: 7 L2 cache: 10.0 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17600
Speed: 1200 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 1200 2: 1200
3: 1200 4: 1200
Graphics:
Device-1: Matrox Systems G200eR2 vendor: Dell driver: mgag200 v: kernel
bus ID: 06:00.0
Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6
direct render: Yes
Audio:
Message: No Device data found.
Network:
Device-1: Broadcom and subsidiaries NetXtreme BCM5720 2-port Gigabit
Ethernet PCIe
vendor: Dell driver: tg3 v: 3.137 port: ecc0 bus ID: 01:00.0
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Broadcom and subsidiaries NetXtreme BCM5720 2-port Gigabit
Ethernet PCIe
vendor: Dell driver: tg3 v: 3.137 port: ecc0 bus ID: 01:00.1
IF: eno2 state: down mac: <filter>
Device-3: NetGear type: USB driver: mt76x2u bus ID: 1-1.2:6
IF: wlx3894edc5d6e1 state: up mac: <filter>
Drives:
Local Storage: total: 1.46 TiB used: 12.68 GiB (0.9%)
ID-1: /dev/sda vendor: Dell PowerEdge RAID Card model: PERC H710
size: 278.88 GiB
ID-2: /dev/sdb vendor: Dell PowerEdge RAID Card model: PERC H710
size: 278.88 GiB
ID-3: /dev/sdc vendor: Dell PowerEdge RAID Card model: PERC H710
size: 931.00 GiB
ID-4: /dev/sdd type: USB vendor: Dell model: Internal Dual SD
size: 1.90 GiB
RAID:
Hardware-1: Broadcom / LSI MegaRAID SAS 2208 [Thunderbolt]
driver: megaraid_sas v: 07.713.01.00-rc1 bus ID: 08:00.0
Partition:
ID-1: / size: 273.00 GiB used: 12.68 GiB (4.6%) fs: ext4 dev: /dev/sda5
Sensors:
System Temperatures: cpu: 31.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 229 Uptime: 1h 24m Memory: 15.59 GiB used: 1.46 GiB (9.4%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38
As well as the output for ethtool eno1:
Settings for eno1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: yes
Any ideas?
|
After examining the output of of sudo journalctl -b 0 -u NetworkManager as suggested by @waltinator, resulting in:
<info> [...] device (eno1): carrier: link connected
<warn> [...] dhcp4 (eno1): request timed out
I finally realized that it may be helpful to check the wifi extender that my server is connected to via ethernet (gross, I know, but it works for the layout of my computers). After a quick WPS reset everything was back in working order again.
| Ethernet Not Connecting on Linux Mint |
1,612,847,195,000 |
While installing Kali Linux there was an option to choose a primary network between Ethernet and Wireless network. But since my device has a problem with wireless I opted for Ethernet. Now, I have bought a new wifi adapter from TP-link, I still cannot access it to use the internet. It shows up when I plug but there is a message like this...
Wifi Network(Ralink)
Wifi is disabled
Furthermore, I can use this adapter in monitor mode and it works fine with wifite tool but I cannot run it normally for the internet.
So please help me run the internet using this external wifi adapter. How do I proceed?
|
Make sure the wifi adapter is correctly installed
Then use this command:
sudo nmtui
to activate a wifi connection and set the DHCP or static IP
Note:
In Linux for all distributions, there is no primary or secondary ethernet.
But you can use the default route (to 0.0.0.0) to ethernet or wifi connection.it is simply added gateway to your connection.
For example:
if you set the default route or gateway in a wifi connection, All traffic is passed through the wifi.
| How do I enable the Wi-Fi as a primary network tool in Kali Linux? |
1,612,847,195,000 |
This mainly happens when I upgrade my Jetson AGX boxes. I want to run
sudo apt-get update
and after a few downloads, the network stops working. It will eventually restart, after the download failed. It can take a minute.
When that happens, the entire network is down for that period of time. All the computers function as normal otherwise (continue to play video, can continue to compile, etc.)
On an idea from @Gilles who posted a comment on this post, I ran tcpdump to see what is happening. The problem happened whenever the network received an STP message on the network.
09:00:26.118679 IP _gateway.42102 > panelve.ssh: Flags [.], ack 37541, win 1944, options [nop,nop,TS val 3025122625 ecr 604916587], length 0
09:00:26.118726 IP _gateway.42102 > panelve.ssh: Flags [.], ack 40093, win 1944, options [nop,nop,TS val 3025122625 ecr 604916587], length 0
09:00:26.124774 IP panelve.ssh > _gateway.42102: Flags [P.], seq 40093:40241, ack 512, win 1446, options [nop,nop,TS val 604916589 ecr 3025122625], length 148
09:00:26.166140 IP _gateway.42102 > panelve.ssh: Flags [.], ack 40241, win 1944, options [nop,nop,TS val 3025122673 ecr 604916589], length 0
09:00:27.738519 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.a4:b2:39:95:9c:47.800c, length 35
09:00:29.738117 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.a4:b2:39:95:9c:47.800c, length 35
09:00:30.193762 IP 192.168.1.2.39763 > 239.255.255.250.1900: UDP, length 146
As we can see, the TCP packets flow as expected until 09:00:26.166140. Then there is a pause and we get an STP 802.1d event. In this specific case, it is too long and ends up failing. Right now, on that network, I see many STP events, every few seconds. There was an outage at that office and all the computers went down. I tried to restart the network switch, but it continues to generate the STP messages.
What else can be done to fix this issue? Is that a hardware problem or would I need to try to reset the switch again? Would I need to turn off everything with a clean shutdown then restart everything? I've never seen such an error before so I'm not too sure what the solution to this one could be...
P.S. note that the network functions just fine as long as I don't try to download large files (i.e. tenth of Mb). So I know that the firewall and connections are all still there as expected. Beside, it worked just fine (and fast) before the outage.
|
So I don't really have a good answer for why the STP message was generated, but I found the culprit: I had a full managed Cisco switch and it was the one generating those messages on the entire network. Once I replaced that switch with a non-managed switch, everything started working properly and really fast as expected.
There may be a way to setup the switch so as to avoid these messages, if you know of such, I'd be glad to listen, although I probably won't take the time to test. But it could be useful for someone else who runs in the same issue. Note that I tested with two such switches so I'm pretty sure that the STP messages are part of the scheme of these switches. It probably requires each system to properly answer to show queries or something of the sort to properly consolidate the network.
So if you see these messages, you may want to replace your switch with a simpler one.
To see whether the problem was fixed, I used the following command:
sudo tcpdump -n | grep ' STP '
While I had the Cisco switch, that would happen at least once every other second. Without the Cisco switch, it never happens.
| LAN network blocks or stops working when downloading "large" files from Internet, what could do that? (I see STP messages in tcpdump output) |
1,612,847,195,000 |
Just installed CentOS 8 (with GUI) on a clean machine.
When accessing Settings>Wi-Fi I get the question mark with:
No Wi-Fi Adapter Found
Make sure you have a Wi-Fi adapter plugged and turned on
There's nothing wrong with the Bluetooth though.
In this machine, I don't have access to Ethernet connection, however I can plug a USB.
I have sudo access with this user.
Edit 1
Just came across this answer.
I have accessed here to download the following packages to a USB stick:
• NetworkManager-1.22.8-5.el8_2.x86_64.rpm
• NetworkManager-tui-1.22.8-5.el8_2.x86_64.rpm
• NetworkManager-libnm-1.22.8-5.el8_2.i686.rpm
• NetworkManager-libnm-1.22.8-5.el8_2.x86_64.rpm
• NetworkManager-wifi-1.22.8-5.el8_2.x86_64.rpm
Changed the directory to the USB stick and when trying to install one of the packages by using
rpm -Uhv $PackageName
I am always incurring in Failed dependencies errors.
Eg. When installing NetworkManager-tui-1.22.8-5.el8_2.x86_64.rpm, I get that I need the following dependencies:
NetworkManager
NetworkManager-libnm
If I try to install either one of the above, there's also dependencies and can't complete the installation.
Edit 2
lsusb
Bus 002 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 002 Device 003: ID 0a5c:21e1 Broadcom Corp. HP Portable SoftSailing
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05c8:0341 Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0951:1665 Kingston Technology Digital DataTraveler SE9 64GB
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
23:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30)
23:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30)
24:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43228 802.11a/b/g/n
Edit 3
From Edit 1, after reading this answer, I have tried using
rpm -ihv $PackageName
Instead of -Uhv. And when running
rpm -ihv NetworkManager-libnm-1.22.8-5.el8_2.x86_64.rpm
I am getting the following
warning: NetworkManager-libnm-1.22.8-5.el8_2.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 8483c65d: NOKEY
Verifying... ################################# [100%]
Preparing... ################################# [100%]
file /usr/lib64/libnm.so.0.1.0 from install of NetworkManager-libnm-1:1.22.8-5.el8_2.x86_64 conflicts with file from package NetworkManager-libnm-1:1.22.8-4.el8.x86_64
Edit 4
As per Artem S. Tashkinov's suggestion, I have reenabled cache, went to my machine that is connected with the Internet (it uses Windows), downloaded the packages kmod-wl-6.30.223.271-32.el8.x86_64.rpm and rpmfusion-nonfree-release-8.noarch.rpm, added them to a USB stick and plugged it to the CentOS machine.
Over there I have changed the directory to the USB stick and ran
rpm -ihv rpmfusion-nonfree-release-8.noarch.rpm
Which got me the following
warning: rpmfusion-nonfree-release-8.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID bdda8475: NOKEY
error: Failed dependencies:
epel-release >= 8 is needed by rpmfusion-nonfree-release-8-0.1.noarch
rpmfusion-free-release >= 8 is needed by rpmfusion-nonfree-release-8-0.1.noarch
And ran
rpm -ihv kmod-wl-6.30.223.271-32.el8.x86_64.rpm
Which retrieved the following
warning: kmod-wl-6.30.223.271-32.el8.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID bdda8475: NOKEY
error: Failed dependencies:
kmod-wl-4.18.0-147.el8.x86_64 >= 6.30.223.271-32.el8 is needed by kmod-wl-6.30.223.271-32.el8.x86_64
|
Just followed @RuiFRibeiro's suggestion and got an Ethernet cable. With it, the process was way faster as it required a variety of packages with various dependencies.
Apart from Artem S. Tashkinov's suggestions, that didn't solve my issue (dnf install kmod-wl this one was giving me dependencies errors), I ran
sudo dnf install kernel
Then
sudo yum install NetworkManager-tui
chkconfig NetworkManager on
service NetworkManager start
Then
sudo yum update
And finally
sudo yum install akmod-wl
Some of the threads I have followed:
. How to connect to wifi in CentOS 7(CLI)(no GUI)?
. Wireless Adapter (WiFi) not working and not showing up in settings
. BROADCOM wireless drivers
| CentOS 8 No Wi-Fi Adapter Found |
1,612,847,195,000 |
Is it possible to create a tap (or taps, if two are required?) between two physical interfaces so that all traffic (ethernet frames) between the two interfaces is passed through the application connected to the tap?
If this is possible, how can this be achieved from a configuration standpoint?
I am familiar with reading and writing to a tap interface from an application, I am just looking for how to set this up so that the application can read and write the traffic going in both directions. The linux device basically becoming a invisible ethernet bridge.
My goal is to be able to have the application in between do two things:
In one direction: Filter certain frames based on destination MAC - for example all packets from eth0 to eth1 that are not to dest 01:01:01:01:01:01 or ff:ff:ff:ff:ff:ff are discarded
In the other direction: delay some frames - for example all packets from eth1 to eth0 are buffered and then only sent every X ticks for Y ticks
If this isn't possible or even if it is - is there a better approach to achieve this?
Edit:
With the approach @dirkt mentions in his answer:
Yes. Create an application that has two tuntap interfaces tap0 and tap1, then >bridge tap0 with eth0 and tap1 with eth1.
would this be the appropriate pseudo code/right idea for how to implement the bridge between the two (eth0/tap0 and eth1/tap1) in the application layer?
counter = 0
//eth0 is bridged to tap0
tap0 = open ("tap0")
//eth1 is bridged to tap1
tap1 = open ("tap1")
forever {
//buffer all packets received by eth1 (tap1) - do I need to buffer them constantly or will they wait at the file pointer until I read them (within reason)
packet_buffer[] = read(tap1)
//every 100 cycles (for simplicity)
if (counter == 100) {
//reset counter
counter = 0
//write all buffered packets from eth1 (tap1) to eth0 (tap0)
foreach (packet_buffer as packet){
write(tap0, packet)
}
//empty packet buffer so we can start filling it again (yes very simplified - would likely use a ring buffer)
packet_buffer = []
}
//if eth0 (tap0) gets a packet
if ( packet = read(tap0) ) {
//forward to eth1 (tap1) if the destination is 01:01:01:01:01:01 or ff:ff:ff:ff:ff:ff
if(packet.dest == 01:01:01:01:01:01 OR packet.dest == ff:ff:ff:ff:ff:ff ){
write(tap1, packet)
}
}
//increment counter
counter++
}
|
Is it possible to create a tap (or taps, if two are required?) between two physical interfaces so that all traffic (ethernet frames) between the two interfaces is passed through the application connected to the tap?
Yes. Create an application that has two tuntap interfaces tap0 and tap1, then bridge tap0 with eth0 and tap1 with eth1.
tap between two bridged physical interfaces
If eth0 and eth1 are already bridged, then this doesn't work. You have to use ebtables to "steal" packets between those interfaces inside the bridge, and direct them somewhere else.
In one direction: Filter certain frames based on destination MAC
You can do this directly with ebtables.
In the other direction: delay some frames
You can use something like
tc qdisc add dev tap0 root netem delay 100ms
to add delay to an interface, but to do it for "some frames" and in one direction and so on is probably indeed easier to do in an application.
| tap between two bridged physical interfaces |
1,612,847,195,000 |
I'm building a system image with v4.19.106 kernel and BusyBox for BeagleBone Black using buildroot 2020.02. If I boot the board from the resulting SD card, I see a strange behaviour: system load stays between 0.60 and 0.75 while CPU usage is below 1%, with no services running, when there's no Ethernet cable connected. As soon as I plug in a cable, the load goes down to 0.00-0.01.
With the cable unplugged I see this line in top -H:
PID USER TIME+ S WCHAN COMMAND
42 root 0:03.03 D msleep [kworker/0:3+events_power_efficient]
Snippet from ip link output:
4: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 4c:3f:d3:91:f2:66 brd ff:ff:ff:ff:ff:ff
Snippet from ifconfig output:
eth0 Link encap:Ethernet HWaddr 4C:3F:D3:91:F2:66
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:49
When I plug in the cable, I see this message:
# [ 3811.689083] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
After that there's no process with Process Status D in top -H, and the load goes down.
Snippet from ip link output with the cable plugged in:
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 4c:3f:d3:91:f2:66 brd ff:ff:ff:ff:ff:ff
Snippet from ifconfig output the cable plugged in:
eth0 Link encap:Ethernet HWaddr 4C:3F:D3:91:F2:66
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7605 (7.4 KiB) TX bytes:0 (0.0 B)
Interrupt:49
Unplugging the cable brings back the high load.
My eth0 config in /etc/network/interfaces:
auto eth0
iface eth0 inet dhcp
If I use allow-hotplug eth0, the interface stays down when the cable is unplugged at boot (and the load stays normal), but it doesn't come up afterwards when I connect a cable, just when I run ifup eth0.
How can I prevent the high load when a cable is unplugged, and get a working connection when it gets plugged in? Are there any kernel configs or device tree entries I should check?
Update:
The issue is present on an image built with the default configuration for the board (beaglebone_defconfig). It uses v4.19.79-ti-r30 kernel from the beagleboard repo (with omap2plus_defconfig).
Another confusing bit is that the issue does not appear after every boot. Power cycling the board usually makes it appear if it was not present, while reboot not necessarily. (I'm not sure if it really makes a difference which method I use, or it just appeared so in my limited number of trials.)
|
The problem is caused by the SMSC LAN8710A PHY chip on BeagleBone Black. When it is put into power saving mode, it fails to detect if a cable has been connected. To work around this issue, the kernel driver regularly wakes the PHY chip to test for connection, and the details of this workaround have changed between v3.8.13-bone80 (used in Debian 7.11) and the v4.4.9 (used in Debian 8.4). The new method is still in use in Linux kernel v5.6.4.
The msleep function visible in top -H is called from lan87xx_read_status() in drivers/net/phy/smsc.c.
I resolved the issue by adding a node for the PHY chip to the device tree with a flag that disables the power saving mode:
&davinci_mdio {
ethernetphy0: ethernet-phy@0 {
reg = <0>;
smsc,disable-energy-detect;
};
};
(The CONFIG_PM kernel config option is ignored by the driver, this is the only way to disable this behaviour.)
| High load when Ethernet cable is unplugged |
1,612,847,195,000 |
Recently I began to observe the following scenario:
After the Kubuntu has booted the icon for wired ethernet is red.
And there is not "Connect" menu for the corresponding connection in network manager.
However after unplugging the cable and plugging it again the icon becomes white and ethernet starts to function.
The problem doesn't happen after each PC start and I'm sure that the cable is ok. There must be some unhappy timing at OS level that causes it. And I also think that it all started after I renamed the connection from "Wired connection 1" which was the default after Kubuntu installation to just "Wired connection".
I can try to use another ethernet cable in the meanwhile but I'm 99% sure that the problem is caused by this "unhappy timing" in OS. I tried to bend the cable when it was plugged but the connection functioned.
I tried to restart the services networking and network-manager but it didn't help
P.S. I used another cable but it didn't resolve the problem
|
Adding:
auto eth0
iface eth0 inet dhcp
to /etc/network/interfaces solved the problem.
The contents of the above file after the operation:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Since changing the file the network interface functions properly after each PC boot. However the icon has changed from white to white and blue. The blue part is most probably the cable.
| Red icon for wired ethernet in Ubuntu |
1,612,847,195,000 |
Please excuse the long description here, but I think it's worth explaining the setup before asking the question:
I have 2 usb Ethernet devices connected to my machine (debian) which configure themselves through avahi with 169.254.x.x addresses.
Connected to the other side of each usb ethernet device is a ssh host (host1 and host2)
When either host1 or host2 is connected via its device I can ssh to to host1.local or host2.local fine.
When both are connected I can only connect to host1.local OR host2.local (I get host unknown/unreachable and similar messages)
If I run
ifconfig
I see that both interfaces are up and have IP addresses
If I run
ip route show
I see that there are two matching routes setup as follows
169.254.0.0/16 dev eth0 scope link src 169.254.3.232 metric 212
169.254.0.0/16 dev eth1 scope link src 169.254.79.120 metric 213
So I think what's happening here is that one of these routes is picking up all traffic in the zeroconf range and sending it to one of the devices, meaning that when both are plugged in only one responds as the traffic is only right for host at the end of that device.
To test this I try deleting the route to the device that is working to allow the other route to take over and send traffic to the other device BUT all variants of the route delete command I've tried seem to do nothing, the route stays in place.
Instead, if I run this the route to eth0 (which host1 is connected to) does go (get deleted) along with all other settings for the device (such as ip, which is expected). host1.local stops responding and host2.local starts responding where it wasn't before proving the theory.
ip addr flush dev eth0
So my solution is then to try and delete these auto-created generic routes that are trumping everything, and to put in more specific routes to the devices (I should add each host does have a fixed IP).
So something like
ip route add 169.254.102.0/24 dev eth0
ip route add 169.254.116.0/24 dev eth1
or even
ip route add 169.254.102.23/32 dev eth0
ip route add 169.254.116.74/32 dev eth1
BUT this doesn't quite work as doing ip addr flush as a way of forcing the route to be removed is too harsh - the routes go in but the interfaces are very much down due to being flushed.
So my question(s) are:
Why might all variants of ip route del NOT remove the bad routes?
Is there another way of removing routes other than using the ip
command?
How else might I solve this problem:
Would bridging the interfaces so they work somewhat like a loadbalancer make more sense as a solution?
Have I totally missed something else I should try in order to make routing more specific (maybe in terms of how zeroconf/avahi sets up these connections)?
|
It is not recommendable changing the network of those routes; they will also will be refresh again by avahi, and at best will return to the latter masks, at worst, there will be a mess of routes/masks.
Also, I would advise stopping to obsess about routing zeroconf/Automatic Private addresses. They are local to a network, and are not routable by definition.
I would advise doing it by the book, and using private RFC 1918 IP addresses.
| Routing zeroconf interfaces |
1,612,847,195,000 |
I am following a tutorial to setup OpenVPN:
To find and note down your IP address use this command ip a show
eth0 and get result
inet 172.26.6.74/20 brd 172.26.15.255 scope global eth0
however I am getting error Device "eth0" does not exist.
I tried command ip addr and get this result
inet 192.168.43.288/24 brd 192.168.43.255 scope global dynamic noprefixrote wio1
This is the correct and required result?
|
The command ip a show eth0 can also be written as ip addr show dev eth0, which means "show me the addressing for network device eth0". When you get the error, Device "eth0" does not exist. it means that eth0 is the wrong device name for your system.
You then tried ip addr, which can also be written as ip addr show, and will have listed the addressing for all devices on your system. I assume that in the result you showed us you had ignored the loopback device lo0 and included just the one remaining device entry for wio1.
inet 192.168.43.288/24 brd 192.168.43.255 scope global dynamic noprefixrote wio1
So everywhere in your tutorial that references eth0 you can probably substitute wio1. And everywhere in the tutorial that uses 172.26.6.74 you should use 192.168.43.288.
If you were to edit your question to include a link to the tutorial it would be possible to check that there's nothing unexpected in it.
| ip address validation for setting up open vps |
1,612,847,195,000 |
I have an issue with my wired ethernet :
After i plug it, the internet connection seem to be ok (ping at google.com --> OK), **but when i go to a website, after loading the first page, the connection is broken.
Config : Linux mint 18.2
sudo lshw -C network
*-network
description: Ethernet interface
produit: AR8161 Gigabit Ethernet
fabriquant: Qualcomm Atheros
identifiant matériel: 0
information bus: pci@0000:04:00.0
nom logique: eth0
version: 08
numéro de série: 10:bf:48:28:20:4a
taille: 1Gbit/s
capacité: 1Gbit/s
bits: 64 bits
horloge: 33MHz
fonctionnalités: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=alx duplex=full ip=192.168.1.11 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
ressources: irq:30 mémoire:f7800000-f783ffff portE/S:d000(taille=128)
ifconfig show increasing number of erros in packet, and ping doesn't respond anyway.
eth0 Link encap:Ethernet HWaddr 10:bf:48:28:20:4a
inet adr:192.168.1.11 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::443a:ead3:32f:d0f7/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:3450 erreurs:2036 :0 overruns:2036 frame:0
TX packets:862 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:1067220 (1.0 MB) Octets transmis:138864 (138.8 KB)
Interruption:19
On the same laptop, I have a Windows boot and the wired ethernet works fine. Wifi connection is okay on both Windows and Linux Mint.
|
Solved thanks to : https://forums.linuxmint.com/viewtopic.php?f=150&t=226626&p=1196004&hilit=AR8161#p1196004
Set MTU to 8192 with
sudo ifconfig eth0 mtu 8192
| Wired ethernet disconnect after first webpage |
1,612,847,195,000 |
On our home LAN, after rebooting the router, I cannot ssh from laptop A to laptop B except via the router. However, after doing a ping from laptop B to laptop A, I can connect normally from A to B. I can reproduce this issue by rebooting the router. Both laptops are connected to the router via WiFi and there are no other APs or routers connected. There are other devices on the LAN and I am not aware of any other ARP issues.
Demonstrating the problem after the router was rebooted:
scott@laptopa:~$ ip addr show dev wlp58s0 |grep 'inet '
inet 192.168.8.194/24 brd 192.168.8.255 scope global dynamic noprefixroute wlp58s0
scott@laptopa:~$ ssh 192.168.8.131 echo okay
ssh: connect to host 192.168.8.131 port 443: No route to host
scott@laptopa:~$ ssh 192.168.8.131 echo okay
ssh: connect to host 192.168.8.131 port 443: No route to host
scott@laptopa:~$ ssh 192.168.8.131 echo okay
ssh: connect to host 192.168.8.131 port 443: No route to host
scott@laptopa:~$ arp |grep 9c:b6:d0:44:18:09
scott@laptopa:~$
The awkward work-around:
scott@laptopa:~$ ssh -o 'ProxyCommand ssh -q -W %h:%p [email protected]' 192.168.8.131 'ping -c 10 192.168.8.194'
PING 192.168.8.194 (192.168.8.194) 56(84) bytes of data.
64 bytes from 192.168.8.194: icmp_seq=1 ttl=64 time=66.3 ms
64 bytes from 192.168.8.194: icmp_seq=2 ttl=64 time=22.9 ms
64 bytes from 192.168.8.194: icmp_seq=3 ttl=64 time=106 ms
64 bytes from 192.168.8.194: icmp_seq=4 ttl=64 time=230 ms
64 bytes from 192.168.8.194: icmp_seq=5 ttl=64 time=252 ms
64 bytes from 192.168.8.194: icmp_seq=6 ttl=64 time=275 ms
64 bytes from 192.168.8.194: icmp_seq=7 ttl=64 time=298 ms
64 bytes from 192.168.8.194: icmp_seq=8 ttl=64 time=321 ms
64 bytes from 192.168.8.194: icmp_seq=9 ttl=64 time=38.3 ms
64 bytes from 192.168.8.194: icmp_seq=10 ttl=64 time=60.3 ms
--- 192.168.8.194 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 22.950/167.478/321.937/112.761 ms
Demonstrating that it now works properly:
scott@laptopa:~$ ssh 192.168.8.131 echo okay
okay
scott@laptopa:~$ arp |grep 9c:b6:d0:44:18:09
laptopb.lan ether 9c:b6:d0:44:18:09 C wlp58s0
Laptops A and B are both running Ubuntu 18.04, and the router is Lede (OpenWRT) 17.01.4.
|
As @roaima suggested, I deleted all of my iptables rules and tested again. I had zero problems, even after rebooting the router several times. Then I added my iptables rules back in and tested further. I still had zero problems.
In short, I can no longer reproduce the problem, so maybe it's random as @dirkt has experienced. Maybe it's some other device on the network.
| How can I track down the source of an Ethernet ARP table issue between Linux laptops? |
1,499,206,383,000 |
I have a server that has two ethernet ports, each one running on a separate NIC (eth0 and eth1). I would like to connect eth0 to a separate machine that streams video over UDP (and no other traffic) while the other interface (eth1) is connected to the network gateway/router.
I don't care if the udp traffic port does not connect to the wider network.
Thank you!
EDIT: Since this question was put on hold, I would like to further clarify my system as per the comments below. My system consists of a machine, running linux, with two ethernet NIC's. I am receiving a UDP stream on one of those ports from a direct LAN-LAN connection to a security camera, and even though I've been able to read the packets coming in from the camera using tcpdump I have yet to be seeing anything coming through via gstreamer which I plan on using to display the video.
Both ports have a static IP address, configured as seen below:
eth0 Link encap:Ethernet HWaddr 5C:F8:21:34:80:F6
inet addr:192.168.1.233 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::5ef8:21ff:fe34:80f6%132688/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1237 errors:0 dropped:0 overruns:0 frame:0
TX packets:90 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:113089 (110.4 KiB) TX bytes:14016 (13.6 KiB)
Interrupt:99
eth1 Link encap:Ethernet HWaddr 5C:F8:21:34:80:F7
inet addr:192.168.1.234 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%132688/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:330 errors:0 dropped:0 overruns:0 frame:0
TX packets:330 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:277171 (270.6 KiB) TX bytes:277171 (270.6 KiB)
And the internal routing table:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
The camera is on address 192.168.1.239, and broadcasts to my server directly over UDP. (the destination MAC is hardcoded into the packets) It is broadcasting an MJPEG stream, and when I take the packets saved by tcpdump I can rebuild it into the MJPEG.
however, when I use gstreamer using the following command:
gst-launch-1.0 udpsrc multicast-iface=eth0, port=1234 ! filesink location=foo
foo does not save any data. I've used this machine to save udp streams using gstreamer in the past, but not when both ports were in use. IE, the video was coming from another machine, through the router, to this server in question.
So, why can't these packets, which the server clearly sees and understands (it's not dropping them at least) not get to my gstreamer program?
|
Typically you'd assign your cross-connect its own /30 subnet, from another bit of RFC1918 (private) space. So you'd do something like this:
192.168.1.234/24 is your LAN on eth1
192.168.255.1/30 is this machine, on eth0 (the cross-connect)
192.168.255.2/30 is the video source, on its end of the cross-connect
If you then 192.168.255.1 and 192.168.255.2 as the IP addresses for your UDP connection, it'll flow over eth0.
It is possible to do this using the same subnet as the LAN (using /32 routes, policy routing, or bridge tricks), but all of those are more complicated and more likely to have issues with confusing random programs.
(Quick explanation of /x notation: It's a short way of specifying the netmask, by counting the number of 1s [binary!] from the left/most significant bit. So /30 means a netmask of 255.255.255.252.)
| UDP internal routing issue when using multiple NIC's |
1,499,206,383,000 |
I'm not seeing this question asked any where else that I've looked. Long story short, NetworkManager brings down eth0 1 minute and 1 second after every hour for the reason of 'connection-removed'. Most of the time, the connection comes back up--although it obviously disconnects everything--within that same second. In some few and far between cases, it does not recover and despite being set with a static IPv4 address, will not recover until the network service is restarted.
The server is a virtual machine running in KVM by a remote hosting provider and takes place precisely within the first second of the first minute every hour. This is a recently installed stock, minimal install of CentOS 7 (trying it out for the first time since CentOS 4) with only one additional application installed: Cockpit.
Here are the logs of that second:
journalctl
http://pastebin.com/sAGEEkrx
/var/log/cron
Feb 3 08:01:01 hyaena CROND[1094]: (root) CMD (run-parts /etc/cron.hourly)
Feb 3 08:01:01 hyaena run-parts(/etc/cron.hourly)[1094]: starting 0anacron
Feb 3 08:01:01 hyaena run-parts(/etc/cron.hourly)[1103]: finished 0anacron
Feb 3 08:01:01 hyaena run-parts(/etc/cron.hourly)[1094]: starting docker-cleanup
Feb 3 08:01:01 hyaena run-parts(/etc/cron.hourly)[1111]: finished docker-cleanup
/etc/cron.hourly
/0anacron
#!/bin/sh
# Check whether 0anacron was run today already
if test -r /var/spool/anacron/cron.daily; then
day=`cat /var/spool/anacron/cron.daily`
fi
if [ `date +%Y%m%d` = "$day" ]; then
exit 0;
fi
# Do not run jobs when on battery power
if test -x /usr/bin/on_ac_power; then
/usr/bin/on_ac_power >/dev/null 2>&1
if test $? -eq 1; then
exit 0
fi
fi
/usr/sbin/anacron -s
/docker-cleanup
#!/bin/bash
# Do nothing if neither docker nor docker-latest service is running
if ! systemctl --quiet is-active docker-latest && ! systemctl --quiet is-active docker; then
exit 0
fi
# If there are no dead containers, exit.
DEAD_CONTAINERS=`docker ps -aq -f status=dead`
[ -z "$DEAD_CONTAINERS" ] && exit 0
# Try to cleanup dead containers
docker rm $DEAD_CONTAINERS
|
I wiped out the ifcfg files created by the CentOS installation media and used nmcli to create them from scratch. The old an new ifcfg files ended up being almost exactly the same. The differences are the order of the content, a new UID automatically generated, and I gave the connection a custom name of ext0 rather than being generated. And now it works perfectly fine.
So, in the end, who the hell knows. The flip desk emoticon would be useful here.
From what I've found, NetworkManager fully separates the device and the connection. In my case, every hour for some reason NetworkManager determined that eth0 was not configured despite it being so and would generate a temporary new connection which would then fail. Therefore, dropping the current connection entirely, failing the temporary one, and repeat.
Perhaps either of those two items are references elsewhere that I'm not aware of, therefore informing NetworkManager it is indeed in use and controlled by NetworkManager (NM_CONTROLLED=yes did nothing, for the record).
In the end, this is my ifcfg-ext0:
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=yes
NAME=ext0 # Arbitrary name given
UUID=<UUID generated by NetworkManager>
DEVICE=eth0
ONBOOT=yes
ZONE=drop
DNS1=<IPv4 DNS server>
DNS2=<IPv4 DNS server>
IPADDR=<static IPv4address>
PREFIX=24
GATEWAY=<static IPv4 gateway>
DOMAIN=<my domain>
DNS3=<IPv6 DNS server>
DNS4=<IPv6 DNS server>
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_PRIVACY=no
| CentOS 7: NetworkManager Connection Restart |
1,499,206,383,000 |
So I have two nics, but I can't get the second to load, here is the output from
lspci -vvv
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Super Micro Computer Inc Unknown device 0000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 169
Region 0: Memory at fb900000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at e000 [size=32]
Region 3: Memory at fb920000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <512ns, L1 <64us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <128ns, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [a0] MSI-X: Enable+ Mask- TabSize=5
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00002000
I found out to use Intels e1000e drivers but when I use make install, I get the following:
[root@lan3 src]# make install
Makefile:67: *** Kernel header files not in any of the expected locations.
Makefile:68: *** Install the appropriate kernel development package, e.g.
Makefile:69: *** kernel-devel, for building kernel modules and try again. Stop.
[root@lan3 src]#
[root@lan3 src]# yum install kernel-devel
Loaded plugins: fastestmirror, kmod
Loading mirror speeds from cached hostfile * addons: centos.mirror.nac.net
* base: centos.chi.host-engine.com
* extras: mirror.metrocast.net
* updates: mirror.trouble-free.net
Setting up Install Process
Package kernel-devel-2.6.18-409.el5.x86_64 already installed and latest version
Nothing to do
[root@lan3 src]#
Changing OS's is not an Option, I realize its old, but its a standard Intel Gigabit Nic. Any help is appreciated!
UPDATES:
# uname -r
2.6.18-194.11.1.el5
ifconfig doesn't show the NIC at all.
|
The solution!
Install elrepo repository. && install kernel independant e1000e drivers from elrepo && tell kernel to use new drivers && reboot.
rpm -Uvh http://www.elrepo.org/elrepo-release-5-5.el5.elrepo.noarch.rpm && yum install kmod-e1000e && sudo nano /etc/modprobe.conf && reboot
Replace
#alias eth0 e100e
alias eth0 kmod-e1000e
| Missing NIC in CentOS 5 - AsteriskNow 1.7.1 |
1,499,206,383,000 |
I'm trying to finish the installation of elementaryOS (an Ubuntu-based distribution) on a Thinkpad E460. However, I can't neither have Ethernet nor Wifi.
In fact, lshw -c network -sanitize shows both devices as UNCLAIMED.
I explain this by the version of the distribution which is based on Ubuntu 14.04 in April 2015 and the laptop seems quite recent. So, I think the kernel doesn't have drivers for this recent material.
The material is the following according to Ubuntu's certifed hardware page:
Intel Ethernet Connection I219-V
Intel Wireless 8260
How can I get these devices to work without an Internet connection on the laptop?
I did not use elementaryOS version from December 2015 because I encountered UEFI issues so I couldn't even install it.
|
Well, I finally tried again to install elementaryOS with the iso of December 2015 and it worked after I've changed UEFI boot to legacy. After installation, the Ethernet port worked but still not the Wifi.
To make the Wifi work, I have upgraded the kernel from 3.19 to 4.3.0.
Now Ethernet and Wifi seem to work fine.
| Wifi and Ethernet unclaimed on ubuntu-based linux |
1,499,206,383,000 |
Since a few days I am experiencing a flapping Ethernet connection on my Fedora 23 laptop: the network connection goes down for several seconds every minute.
The machine is up-to-date with the latest kernel (4.4.6) and packages.
UPDATE: The problem persists in different environments (different cables and switches) and regardless of static or DHCP addressing; the connection with an USB-Eth adapter worked for one hour or so, then started behaving the same way.
Booting on an older kernel (4.4.3) did not solve the problem. However, when booting on a Live CD with Fedora 21, the wired network seems to work.
Anyone has experienced this issue? Here's some troubleshooting output (concerning the eth device enp0s25):
[root@linuxbox ~]# ip address
(...)
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether ec:b1:d7:97:9d:f2 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.13/24 brd 10.10.10.255 scope global enp0s25
valid_lft forever preferred_lft forever
inet6 fe80::eeb1:d7ff:fe97:9df2/64 scope link
valid_lft forever preferred_lft forever
(...)
[root@linuxbox ~]# dmesg
(...)
[ 1403.944457] ax88179_178a 4-5:1.0 enp0s20u5: ax88179 - Link status is: 0
[ 1409.490222] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 1409.490232] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
[root@linuxbox ~]# ping www.google.com
PING www.google.com (172.217.16.132) 56(84) bytes of data.
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=1 ttl=54 time=4.79 ms
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=2 ttl=54 time=4.48 ms
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=3 ttl=54 time=4.57 ms
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=50 ttl=54 time=4.62 ms
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=51 ttl=54 time=4.50 ms
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=52 ttl=54 time=4.81 ms
64 bytes from zrh04s06-in-f4.1e100.net (172.217.16.132): icmp_seq=53 ttl=54 time=6.16 ms
(...)
^C
--- www.google.com ping statistics ---
65 packets transmitted, 11 received, 83% packet loss, time 64018ms
rtt min/avg/max/mdev = 4.486/4.803/6.164/0.469 ms
[root@linuxbox ~]# ethtool enp0s25
Settings for enp0s25:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[root@linuxbox ~]# ethtool -S enp0s25
NIC statistics:
rx_packets: 10222
tx_packets: 1774
rx_bytes: 1146761
tx_bytes: 250438
rx_broadcast: 9287
tx_broadcast: 37
rx_multicast: 84
tx_multicast: 102
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 84
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 9429
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
tx_hwtstamp_timeouts: 0
[root@linuxbox ~]# uname -a
Linux linuxbox 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@linuxbox ~]# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
Related question.
|
I think the problem is solved in one environment. Apparently someone else set his IP address (statically) the same as mine (static too). The conflict of IP addresses caused this behaviour.
The problem presents itself also in another environment where everybody uses (or is supposed to use) DHCP addressing. I'll check this and update this answer if I find out that this was the cause of the problem.
| Flapping Ethernet connection of Fedora 23 |
1,499,206,383,000 |
This is going to seem like an odd request, but it's necessary. I have a wireless router that is not to be used for internet access. The current router that I have is a DLink DIR-626L and I use it to connect to a few embedded devices for an application that I am working on.
For internet, I am hardwired by ethernet into the network. The problem that I am having is that if I connect to my DLink WiFi router, internet traffic wants to go through the DLink router instead over the ethernet port and the DLink router has no internet connection. I know this is going on because if I try to pull up a webpage I get a D-Link error page saying that I am not connected to the internet.
Looking at some other questions, it seems like my router might be advertising itself as a "gateway" and I can't seem to find a way to turn that off by digging through the settings.
Is there a way to tell Linux that all internet traffic should go over the ethernet port?
A few specifications:
-All of the devices that are broadcasting to the router are doing so over UDP.
They are just spitting out data to a static IP over a dedicated port.
-I am using Linux Mint 17.2.
-I had this setup working with a small battery powered TP-Link router (TL-MR3040). I didn't do anything special for this, it just "worked."
|
What you can do is configure your dhcp client to ignore the router attribute that comes in the DHCP reply.
Edit your /etc/dhcp/dhclient.conf that defines which atributes you receive via dhcp, and take out from the line that starts with request the word routers.
request subnet-mask, broadcast-address, time-offset; # routers;
After editing, do
sudo service networking restart
| Force internet traffic over LAN, but connect to router over WiFi |
1,499,206,383,000 |
When I connect to my wired network using netctl, the connection drops automatically after a few seconds. It happens both with DHCP and static configuration, but the wifi connection on the same network works perfectly.
What really bothers me is that there is absolutely nothing in the logs, the output of journalctl is absolutely normal during network start-up, and nothing happens when the network disconnects.
Aug 22 18:34:37 dimension polkitd[5127]: Registered Authentication Agent for unix-process:7050:2995548 (system bus name :1.66 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug 22 18:34:37 dimension systemd[1]: Starting Networking for netctl profile static...
Aug 22 18:34:37 dimension network[7055]: Starting network profile 'static'...
Aug 22 18:34:37 dimension kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
Aug 22 18:34:37 dimension kernel: alx 0000:04:00.0 enp4s0: NIC Up: 1 Gbps Full
Aug 22 18:34:37 dimension kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Aug 22 18:34:37 dimension avahi-daemon[558]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.43.
Aug 22 18:34:37 dimension avahi-daemon[558]: New relevant interface enp4s0.IPv4 for mDNS.
Aug 22 18:34:37 dimension avahi-daemon[558]: Registering new address record for 192.168.0.43 on enp4s0.IPv4.
Aug 22 18:34:37 dimension avahi-daemon[558]: Registering new address record for 192.168.0.175 on enp4s0.IPv4.
Aug 22 18:34:37 dimension network[7055]: Started network profile 'static'
Aug 22 18:34:37 dimension systemd[1]: Started Networking for netctl profile static.
Aug 22 18:34:37 dimension polkitd[5127]: Unregistered Authentication Agent for unix-process:7050:2995548 (system bus name :1.66, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
I have tried connecting directly to the router, I have changed the IP addresses, and I have tried with wicd instead of netctl, with always the same issue.
I'm using an up-to-date Arch Linux.
|
For those still looking for an answer, I asked about the same issue on the Arch Linux forums and I got a (temporary) fix of the bug:
https://bbs.archlinux.org/viewtopic.php?id=201459
| Wired connection drops after a few seconds |
1,499,206,383,000 |
I wrote a small php application on a SBC. I created a disk image from the CF card. When I write the image to a new CF and install on a new SBC the interface index numbers (I hope I am stating that correctly) change. For instance - the interface numbers on the original board are eth0, eth1, etc. When I move the disk image to a new board the interfaces are added as eth5, eth6, etc.
My real question is, is there a way to maintain the original indexing?
There is probably a better way to articulate my question so feel free to point out my ignorance.
|
This can be accomplished by deleting the network interface definitions in \etc\udev\rules.d\70-persistent-net.rules
Generally these definitions start with:
# PCI device
| I wish to move SBC flash image to new board and maintain network interface indexing |
1,499,206,383,000 |
I have been trying to set up a DHCP server on CentOS 6 running on an Intel NUC i7. I have installed dhcpd and am using the example dhcpd.conf
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.254;
option subnet-mask 255.255.255.0;
option domain-name "xtreemfs.org";
option domain-name-servers 192.168.1.1;
option time-offset -25200; # GMT - 7
range 192.168.1.2 192.168.1.64;
}
What I have tried:
1. Making sure that there is a file in /var/lib/dhcpd/ called dhcpd.leases
2. Making sure that my dhcpd.conf file is not missing any terminators (;)
3. Editing the /etc/sysconfig/dhcpd file to use eth0
4. Rebooting the system
When I try to start the server (sudo service dhcpd restart) it says:
Starting dhcpd: [FAILED]
Here are my questions:
1. Is there a way to find out what is causing the failure (looking at some log)?
2. What can I do to solve the issue?
(If anyone is wondering my setup consists of 3 Intel NUC i7 computers connected to a 1000/T eth switch and none of the computers are connected to my local network. My goal is to setup one of the computers as a DHCP server for the other two.)
|
I solved the problem after reading the messages file in /var/log:
less /var/log/messages
This showed me that the issue was that there was no configured listen device. To solve this problem I added eth0 to my /etc/sysconfig/dhcp/dhcpd.conf file and everything worked fine.
| Problems Setting Up DHCP Server On CentOS 6 |
1,499,206,383,000 |
I've installed Debian with xfce and did some configuring by installing themes, configuring xfce, installing and uninstalling software; the usual. Anyway, after a reboot I can't connect to the internet. I can't connect with chrome and ping doesn't return anything with DNS or IP. This happened with a previous installation and I assumed it was an installation error so I re-installed and configured my system again and the same thing happened. The system does not have wireless, the ethernet is the only networking resource. I've tested the line on my laptop and it works, the internet is also fine. THis wasn't an issue until I recently rebooted. I've also had a problem with xorg. It doens't start when I boot, I have to type "startx" to get a gui. All signs that I can observe point toward this being a machine-problem
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mod DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ehter 44:8a:5b:9f:bd:cb brd ff:ff:ff:ff:ff:ff
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
"
$ auto eth0
$ allow-hotplug eth0
$ iface eth0 inet dhcp
"
All return "bash: *: command not found"
$ ping -c 3 www.google.com
ping: unknown host www.google.com
$ ping -c 3 8.8.8.8
connect: Network is unreachable
|
You need to add the following two lines to /etc/network/interfaces:
allow-hotplug eth0
iface eth0 inet dhcp
Then, as root, run
ifup eth0
You can probably fix your X.org problem by installing lightdm; that will start a desktop manager when the system boots.
| Debian wired connection static IP wont connect |
1,499,206,383,000 |
On my Fedora 21 64bit Gnome 3.14.3 install, I have noticed that the NeworkManager always connects to the wired connection, even if the cable is not connected:
However, the driver (or something) does know whether or not it is connected - I can see this with watch "dmesg | tail -10":
[ 7349.552202] atl1c 0000:07:00.0: atl1c: enp7s0 NIC Link is Down
[ 7373.496359] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
[ 7376.271449] atl1c 0000:07:00.0: atl1c: enp7s0 NIC Link is Up<100 Mbps Full Duplex>
[ 7376.271482] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
[ 7553.088393] atl1c 0000:07:00.0: atl1c: enp7s0 NIC Link is Down
[ 7597.096174] atl1c 0000:07:00.0: atl1c: enp7s0 NIC Link is Up<100 Mbps Full Duplex>
[ 7620.983378] atl1c 0000:07:00.0: atl1c: enp7s0 NIC Link is Down
[ 7622.556874] atl1c 0000:07:00.0: atl1c: enp7s0 NIC Link is Up<100 Mbps Full Duplex>
This causes issues when the cable has unplugged, but it still thinks it is connected to the internet, and trys to sync or connect and fails.
lspci -v
07:00.0 Ethernet controller: Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1)
Subsystem: Lenovo Device 3979
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at e0500000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 2000 [size=128]
Capabilities: <access denied>
Kernel driver in use: atl1c
Kernel modules: atl1c
ifconfig:
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.22 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::de0e:a1ff:fed1:d12b prefixlen 64 scopeid 0x20<link>
ether dc:0e:a1:d1:d1:2b txqueuelen 1000 (Ethernet)
RX packets 111875 bytes 67103677 (63.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 87152 bytes 7793021 (7.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 13 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 0 (Local Loopback)
RX packets 3669 bytes 880913 (860.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3669 bytes 880913 (860.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sudo yum list installed NetworkManager*
Installed Packages
NetworkManager.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-adsl.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-bluetooth.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-config-connectivity-fedora.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-config-server.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-devel.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-glib.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-glib-devel.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-iodine.x86_64 0.0.4-4.fc21 @fedora
NetworkManager-iodine-gnome.x86_64 0.0.4-4.fc21 @fedora
NetworkManager-l2tp.x86_64 0.9.8.7-3.fc21 @fedora
NetworkManager-openconnect.x86_64 0.9.8.6-2.fc21 @updates
NetworkManager-openswan.x86_64 0.9.8.4-4.fc21 @fedora
NetworkManager-openswan-gnome.x86_64 0.9.8.4-4.fc21 @fedora
NetworkManager-openvpn.x86_64 1:0.9.9.0-3.git20140128.fc21 @koji-override-0/$releasever
NetworkManager-openvpn-gnome.x86_64 1:0.9.9.0-3.git20140128.fc21 @koji-override-0/$releasever
NetworkManager-pptp.x86_64 1:0.9.8.2-6.fc21 @koji-override-0/$releasever
NetworkManager-pptp-gnome.x86_64 1:0.9.8.2-6.fc21 @koji-override-0/$releasever
NetworkManager-ssh.x86_64 0.9.3-0.3.20140601git9d834f2.fc21 @fedora
NetworkManager-ssh-gnome.x86_64 0.9.3-0.3.20140601git9d834f2.fc21 @fedora
NetworkManager-tui.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-vpnc.x86_64 1:0.9.9.0-6.git20140428.fc21 @koji-override-0/$releasever
NetworkManager-vpnc-gnome.x86_64 1:0.9.9.0-6.git20140428.fc21 @koji-override-0/$releasever
NetworkManager-wifi.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
NetworkManager-wwan.x86_64 1:0.9.10.1-1.4.20150115git.fc21 @updates
modinfo atl1c
filename: /lib/modules/3.17.8-300.fc21.x86_64/kernel/drivers/net/ethernet/atheros/atl1c/atl1c.ko.xz
version: 1.0.1.1-NAPI
license: GPL
description: Qualcom Atheros 100/1000M Ethernet Network Driver
author: Qualcomm Atheros Inc., <[email protected]>
author: Jie Yang
srcversion: 4333D8ADEE755DD5ABDF0B8
alias: pci:v00001969d00001083sv*sd*bc*sc*i*
alias: pci:v00001969d00001073sv*sd*bc*sc*i*
alias: pci:v00001969d00002062sv*sd*bc*sc*i*
alias: pci:v00001969d00002060sv*sd*bc*sc*i*
alias: pci:v00001969d00001062sv*sd*bc*sc*i*
alias: pci:v00001969d00001063sv*sd*bc*sc*i*
depends:
intree: Y
vermagic: 3.17.8-300.fc21.x86_64 SMP mod_unload
signer: Fedora kernel signing key
sig_key: F4:8F:FC:A3:C9:62:D6:47:0F:1A:63:E0:32:D1:F5:F1:93:2A:03:6A
sig_hashalgo: sha256
If this is a bug, is it NetworkManager or something else? I had no issues with this under Fedora 19 with the same driver (which seems to be the same version in the latest kernel in its backup).
|
I eventually got around to putting together a bug report, and was told that removing the NetworkManager-config-server package would solve it - so I did:
sudo yum autoremove NetworkManager-config-server
Then I rebooted, and it worked :)
| NetworkManager does not detect when cable is connected or disconnected |
1,499,206,383,000 |
I have setup a small home server / NAS running Debian 7. The server is connected directly to the router with a static IP set in the router's control panel. There are no port forwarding rules set for the server machine.
The server has been running fine for over two weeks, providing a samba share and a Plex service to the home network. Last week I wanted to use it to wake other devices in the house, so I installed the ethtool and ethwreake packages to do so. After those installs, when the server is attached to the router (or indirectly via a switch), it makes the internet connection drop randomly, for about 1-2 minutes. After this time, the connections returns and I can ping google.com for about 20-30 seconds, and that keeps repeating forever.
I have absolutely no idea what could be causing this. How can a machine make the internet connection drop for the entire network? The only thing I could think of is some king of packet flooding, and the router can't keep up with the requests and reboots itself or something like that.
This has happened before on another Debian install, and I had to reinstall the OS entirely since I couldn't find a solution.
When I disconnect the server to the network, the connection returns after about 1 minute.
Is there some kind of test I could do to find the cause, or do I have to clean install Debian again?
|
It sounds like what happens when two devices on the same network have been given the same IP address. Check both devices and ensure that they have different IP addresses.
| Debian server makes internet connection drop |
1,499,206,383,000 |
Let's say we are happy with our typical wireless router.
But one day we notice it has four LAN ports. We connect an Ethernet
cable from one of them to our computer. On our computer do we use:
dhclient and the same SSID and password as we used for wireless?
pppoe and the same userid and password our ISP gave us?
One of the above, with no username or password?
|
In most typical consumer-grade "Ethernet Router with WiFi Network Access Point" (i. e. "router") equipment, you can simply connect the Ethernet cable, and use the standard DHCP client on that interface (assuming a typical default configuration). SSIDs and WPA passwords and only used for the wireless connection protocol and are not part of the basic TCP/IP connection itself.
That said, it is possible the configuration of the router may have been hardened somewhat (for example to only issue DHCP leases to known MAC addresses), in which case you may have to noodle around in the router's administrative interface-- which is beyond the scope of this question and this Stack.
| How to connect to the four Ethernet ports on a wireless router? |
1,499,206,383,000 |
I was trying to ping my machine from a photon OS IP but wasn't able to do so. So I followed a post and changed the /etc/systemd/network/10-eth0.network to the following:
[Match]
Name=eth0
[Network]
Domains=HOSTNAME domain.local
Gateway=1xxx.xxx.x.x
Address=1xx.xxx.x.xxx
DHCP=no
[DHCP]
UseDomains=false
Now I can't even login. Is there anything that can be done?
|
You do not appear to have configured a NETMASK or PREFIX value for your interface. While not clearly explained often, a proper address actually requires this information.
If you can no longer remotely connect via SSH, Telnet, etc. to the VM, you will need to logon to the console of the system:
physical computer will require access to the monitor, keyboard, mouse, etc.
virtual machine will require access to the 'virtual console', which can vary greatly depending on the virtualization technology in use
Once on the console, you need to login and modify the network configuration file to include all necessary parameters. Please refer to the PhotonOS documentation (man pages is probably sufficient) to be sure, but at the minimum I believe a NETMASK value is required.
| 10-eth0.network |
1,499,206,383,000 |
Issuing this:
ethtool -S <network device> | egrep "err|fail"
I get the following errors:
tx_lost_interrupt: 225
rx_alloc_fail: 36297
What is, tx_lost_interrupt and rx_alloc_fail ?
Do these errors indicate a real network problem?
|
Those are NIC- or driver-specific extended statistics, so it would be important to know the type of the network interface used and/or the name of the driver module used with it.
However, at least in kernel version 4.14.85, it looks like the string tx_lost_interrupt appears only in the Intel i40e NIC driver. This seems to be the patch that originally added that statistic to the driver.
It looks like it counts the times a software workaround was applied to a case of a lost hardware interrupt. I could not find any further description, but it looks like a workaround for a NIC hardware bug to me...
rx_alloc_fail, on the other hand, looks like it indicates the number of times the driver failed to allocate a memory buffer for received packet(s). That might indicate that your system is under some amount of memory pressure, and could use more RAM.
| Network capture using ethtool points to problem? |
1,499,206,383,000 |
suddenly my ethernet stopped working when I type
sudo lshw -C network
This is the result
*-network UNCLAIMED
description: Ethernet controller
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
version: 07
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd cap_list
configuration: latency=0
resources: ioport:3000(size=256) memory:a2200000-a2200fff memory:a2000000-a2003fff
But I am able to connect to WiFi.
My kernel version is 5.4.0-24-generic
|
I fixed this issue by reinstalling this driver from GitHub user ghostrider-reborn.
| Network Unclaimed for ethernet |
1,499,206,383,000 |
Does someone has any script that can "CAM attack" a switch/router, so that it will act as a HUB? Are there any tools for it in the repositories?
|
The application you are looking for is macof which is part of the dsniff toolkit. You'll find that ettercap is also quite useful when doing any sort of network auditing on a switched network.
Warning: I'm a firm believer that you need to understand the threat to defend against it, but you best be using these tools in your own lab on your own equipment. If that is not the case, I guarantee someone much smarter than the both of us will bring down a righteous hammer on you. Play nice!
| How Can I "CAM attack" a switch/router? |
1,605,634,827,000 |
I have a host who can be connected by wifi or by ethernet.
According to the link I want to make actions.
How to detect that with a script ?
|
The interface used for each type of link is different. Say, the ethernet interface could be eth0 and the WLAN interface could be wlan0. Knowing the names you could find which is active and act accordingly.
To list all interface and show their status use the command ip link show. This command works in the modern flavors of Linux, and so the rest of the utils and Bash shell. I suppose you could adapt it to any OS (In Windows, I suggest using cygwin and awk or Python to parse the ipconfig or netsh output, or PowerShell Get-NetAdapter module).
Example output:
user@host$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:50:56:9b:90:7d brd ff:ff:ff:ff:ff:ff
You could then filter the interface name/status using grep looking for lines starting with a number:
user@host$ ip link show | grep "^[0-9]"
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
The active interfaces have the word UP, so to get the active one filter out the local interface localhost (lo:):
user@host$ ip link show | grep "^[0-9]" | grep -v "lo: " | grep "UP"
2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
We need only the interface name, the second word:
user@host$ ip link show | grep "^[0-9]" | grep -v "lo: " | grep "UP" | cut -d ':' -f 2
ens32
You could store this result in some variable (in Bash):
ACTIVEIF=$(ip link show | grep "^[0-9]" | grep -v "lo: " | grep "UP" | cut -d ':' -f 2)
Of course, if you have more than one active interface store the list in an array of names adding parenthesis and spaces around the result. For example (from now on, I won't filter lo:, as I only have one physical interface):
ACTIVEIFACES=( $(ip link show | grep "^[0-9]" | grep "UP" | cut -d ':' -f 2) )
To check the array variable contents:
user@host$ set | grep ^ACTIVEIFACES
ACTIVEIFACES=([0]="lo" [1]="ens32")
and to list them in a script:
ACTIVEIFACES=( $(ip link show | grep "^[0-9]" | grep "UP" | cut -d ':' -f 2) )
NIFACES=${#ACTIVEIFACES[@]}
if [ $NIFACES -ne 0 ] ; then
echo "There exist $NIFACES active interfaces:"
for ((i=0; i<NIFACES; i++)) ; do
echo "${ACTIVEIFACES[$i]}"
done
else
echo "There is no active interfaces detected"
fi
(As the for command uses numeric expressions, you could omit the $ in $i and $NIFACES between the double parentheses).
The script output in my case is:
There exist 2 active interfaces:
lo
ens32
I hope this method is useful to you. Good luck!
| script "By wifi or by Ethernet" [closed] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.