dhclient or network problem
Hi, i have a problem with dhclient: for example interface name eno52 (tg3, Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) : root@:~# dhclient eno52 -v Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno52/3c:a8:2a:e7:87:bf Sending on LPF/eno52/3c:a8:2a:e7:87:bf Sending on Socket/fallback DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received. No working leases in persistent database - sleeping. tcpdump during dhclient doesn't show anything?!? root@*:~# tcpdump -i eno52 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes root@***:~# ip addr show eno52 9: eno52: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff if i use the same ethernet cable on my laptop all works fine... i don't know if is a module problem...or? Can you help me? BR
Debain 9 dhclient or network problem
Hi, i have a problem with dhclient: for example interface name eno52 (tg3, Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) : root@:~# dhclient eno52 -v Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno52/3c:a8:2a:e7:87:bf Sending on LPF/eno52/3c:a8:2a:e7:87:bf Sending on Socket/fallback DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received. No working leases in persistent database - sleeping. tcpdump during dhclient doesn't show anything?!? root@*:~# tcpdump -i eno52 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes root@***:~# ip addr show eno52 9: eno52: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff interface eno52 seems to be disconnected but cable is plugged and working (i tried with other pc) obviously ethernet cable is connected... Debian 8 works fine with this hw Debian 9 doesn't work Server is ProLiant DL380 Gen9 (719064-B21) root@***:~# lspci -v | grep -A10 Ethernet 02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0 Memory at 92c9 (64-bit, prefetchable) [size=64K] Memory at 92ca (64-bit, prefetchable) [size=64K] Memory at 92cb (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at 9310 [disabled] [size=256K] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [a0] MSI-X: Enable+ Count=17 Masked- Capabilities: [ac] Express Endpoint, MSI 00 -- 02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0 Memory at 92c6 (64-bit, prefetchable) [size=64K] Memory at 92c7 (64-bit, prefetchable) [size=64K] Memory at 92c8 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at 9314 [disabled] [size=256K] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [a0] MSI-X: Enable- Count=17 Masked- Capabilities: [ac] Express Endpoint, MSI 00 -- 02:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0 Memory at 92c3 (64-bit, prefetchable) [size=64K] Memory at 92c4 (64-bit, prefetchable) [size=64K] Memory at 92c5 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at 9318 [disabled] [size=256K] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [a0] MSI-X: Enable- Count=17 Masked- Capabilities: [ac] Express Endpoint, MSI 00 -- 02:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0 Memory at 92c0 (64-bit, prefetchable) [size=64K] Memory at 92c1 (64-bit, prefetchable) [size=64K] Memory at 92c2 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at 931c [disabled] [size=256K] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [a0] MSI-X: Enable- Count=17 Masked- Capabilities: [ac] Express Endpoint, MSI 00 -- 04:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331FLR Adapter Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0 Memory at 92b9 (64-bit, prefetchable) [size=64K] Memory at 92ba (64-bit, prefetchable) [size=64K] Memory at 92bb (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at 9300 [disabled] [size=256K] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [a0] MSI-X: Enable- Count=17 Masked- Capabilities: [ac] Express Endpoi
Re: Debain 9 dhclient or network problem
Hi, i tried every other interface butt it's the same i tried also to disable interface renaming but doesn't work. 2017-07-11 8:02 GMT+02:00 Johann Spies : > On 11 July 2017 at 07:48, Franz Angeli wrote: >> Hi, >> >> i have a problem with dhclient: >> >> for example interface name eno52 (tg3, Broadcom Limited NetXtreme >> BCM5719 Gigabit Ethernet PCIe (rev 01) : >> >> root@:~# dhclient eno52 -v >> Internet Systems Consortium DHCP Client 4.3.5 >> Copyright 2004-2016 Internet Systems Consortium. >> All rights reserved. >> For info, please visit https://www.isc.org/software/dhcp/ >> > ... >> if i use the same ethernet cable on my laptop all works fine... (DHCP >> lease and so on) > > My first guess would be that the order of the network interfaces > differ between Debian 8 and 9 and that you should try the cable on the > other interfaces. > > In the past (many years ago) it was a known problem that eth0 on the > new system used for another interface. I don't know whether this is > still the case. It had been some time that I had to build a server. > > Regards > Johann > -- > Because experiencing your loyal love is better than life itself, > my lips will praise you. (Psalm 63:3) >
Re: Debain 9 dhclient or network problem
nothing usefull... one strange thing is that during debian installation all works fine because i use net-install with a iso. 2017-07-11 9:27 GMT+02:00 Johann Spies : > On 11 July 2017 at 08:29, Franz Angeli wrote: > >> i tried every other interface butt it's the same >> >> i tried also to disable interface renaming but doesn't work. > > What information do you get from /var/log/messages, /var/log/syslog > and dmesg about your interfaces? > > Regards > Johann >
Diskless Debian stretch ISCSI boot (uefi) and shutdown hanging problem
Hi, i have one diskless server able to boot with ISCSI, uefi is configures to reach iscsi target and volume correctly; i installed Debian 9 with debian installer ad all works fine, at the end of installation process i remount root filesystem with (chroot /target) and edit initaramfs.conf with: IP=10.10.200.150::10.10.200.1:255.255.255.0:ti**1.mk***.it:eno1 and after i update initramfs with: update-initramfs -u system boot correctly and works fine. Problem is during shutdown, system hanging with: a stop job is running for ifup for eno1 a stop job is running for Raise network interfaces and i have to reset the server... I know i can do the same with: "ISCSI_AUTO=true" on /etc/iscsi/iscsi.initramfs but i need a static IP configured as i do. Some suggestion? Thanks in advance
Re: Diskless Debian stretch ISCSI boot (uefi) and shutdown hanging problem
Hi, you are correct, in /etc/network/interfaces i have interface eno1 configured with DHCP and after removing configuration system shutdown correctly. Thank you! BR 2017-07-19 20:50 GMT+02:00 Christian Seiler : > Hi, > > (I'm one of the maintainers of the open-iscsi package in Debian.) > > On 07/19/2017 07:40 AM, Franz Angeli wrote: >> i have one diskless server able to boot with ISCSI, uefi is configures >> to reach iscsi target and volume correctly; >> >> i installed Debian 9 with debian installer ad all works fine, at the >> end of installation process i remount root filesystem with (chroot >> /target) and edit initaramfs.conf with: >> >> IP=10.10.200.150::10.10.200.1:255.255.255.0:ti**1.mk***.it:eno1 >> >> and after i update initramfs with: >> >> update-initramfs -u >> >> system boot correctly and works fine. >> >> Problem is during shutdown, system hanging with: >> >> a stop job is running for ifup for eno1 >> >> a stop job is running for Raise network interfaces >> >> and i have to reset the server... >> >> I know i can do the same with: >> >> "ISCSI_AUTO=true" on /etc/iscsi/iscsi.initramfs >> >> but i need a static IP configured as i do. > > Do you perhaps also have something in /etc/network/interfaces or > /etc/network/interfaces.d, perhaps even DHCP configured? Because > if that takes over IP configuration and systemd kills the DHCP > client (which in turn removes the IP of the interface at > shutdown), then you'll see a hang because the network is gone > even though you still need it. > > (ifupdown _should_ detect rootfs on iSCSI and not try to down > the interface by script, but the SIGTERM from systemd might > cause the dhcp client to drop the IP anyway.) > > (Also note that you'd need to reboot twice after changing this > to test if that works.) > > Regards, > Christian
