| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20190607172242.6b6836b1@hermes.lan>
Date: Fri, 7 Jun 2019 17:22:42 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Ronak Doshi <doshir@...are.com>
Cc: netdev@...r.kernel.org
Subject: Fw: [Bug 203847] New: VMware e1000 adapter doesn't get an IP
address assigned. Manually assigning one does not solve the issue
Begin forwarded message:
Date: Fri, 07 Jun 2019 23:53:00 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 203847] New: VMware e1000 adapter doesn't get an IP address assigned. Manually assigning one does not solve the issue
https://bugzilla.kernel.org/show_bug.cgi?id=203847
Bug ID: 203847
Summary: VMware e1000 adapter doesn't get an IP address
assigned. Manually assigning one does not solve the
issue
Product: Networking
Version: 2.5
Kernel Version: 5.2-rc3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
Assignee: stephen@...workplumber.org
Reporter: www.anuprita804@...il.com
Regression: No
Created attachment 283149
--> https://bugzilla.kernel.org/attachment.cgi?id=283149&action=edit
Dmesg for 5.2-rc3
When booting 5.2-rc3 on an arubacloud VPS (running VMware and using the e1000
driver for internet access) no IP address is assigned to eth0
The last working kernel was 5.2-rc2
Systemd-networkd is being used for network setup. Tried networkmanager too.
With systemd-networkd no IP address is assigned to eth0. Networkmanager does
assign an address to eth0 but there is no internet access
Booting 5.2-rc2 or 5.1.7 works with both systemd-networkd and networkmanager
without any issues
The dmesg for 5.2-rc3 has been attached
The kernel configuration can be found here
https://emptyclouds.net/anupri/dot.config
This is an output of ip addr on 5.2-rc3
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: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 00:50:56:9f:92:d8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 00:50:56:9f:e4:53 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 00:50:56:9f:31:a5 brd ff:ff:ff:ff:ff:ff
Same thing but with 5.2-rc2 (or 5.1.7 as the output is the same for both)
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc cake state UP group
default qlen 1000
link/ether 00:50:56:9f:92:d8 brd ff:ff:ff:ff:ff:ff
inet 217.61.104.90/24 brd 217.61.104.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2a03:a140:10:2c5a::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe9f:92d8/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 00:50:56:9f:e4:53 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 00:50:56:9f:31:a5 brd ff:ff:ff:ff:ff:ff
ip link on 5.2-rc3
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> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 00:50:56:9f:92:d8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 00:50:56:9f:e4:53 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 00:50:56:9f:31:a5 brd ff:ff:ff:ff:ff:ff
[root@...hlinux ~]# 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 cake state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:9f:92:d8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 00:50:56:9f:e4:53 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
ip link on 5.2-rc2
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 cake state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:9f:92:d8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 00:50:56:9f:e4:53 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 00:50:56:9f:31:a5 brd ff:ff:ff:ff:ff:ff
--
You are receiving this mail because:
You are the assignee for the bug.
Powered by blists - more mailing lists