lost IP address

[ehn29]

Hi

Do you have any idea why when loading Shredos via an IPXE boot, I lose the network connection.
My client station responds to the ping as long as I am on the Ipxe boot menu.
This problem appears when my client is connected via a network adapter on a USB-C port.
If I use the internal network port, no loss of network.
And therefore at the end of the deletion, no more network to operate the LFTP transfer.

if I manually reconfigure an IP address from the console with ifconfig -a eth0 xxx.xxx.xxx.xxx, I can transfer the log to my server via FTP

thanks

[PartialVolume]

If you plug a FAT formatted USB stick into the system & boot via IPXE, when ShredOS boots it will write the dmesg.txt file to the root of the USB stick. It also writes it again when you Control C to exit nwipe which will probably show more information. Maybe dmesg.txt will show why the USB network fails.

However, having said that, ShredOS will automatically attempt to get a DHCP IP address whenever the network lead is plugged in or out.

When the USB network is connected what's the output of ifconfig? The reason I ask is that ShredOS will only work with certain network device names, if I remember correctly. ethx being one and maybe enpxxxx being another device name. If your USB network has a name that differs from ethx or enpxx then the network scripts will fail to obtain a dynamic address from the DHCP server. If this is the case it is a fairly easy fix. I just need to know the first few characters of the network device name.

I've only tested ShredOS networking with DHCP so I've no idea how it will work with static IPs as the networking scripts will presumably still try to obtain a dynamic IP address.

[ehn29]

hi

I only have the loopback card in the ifconfig output

the network card seems to be seen in eth0 in the dmesg file.
Here is the complete dmesg.txt file.
this may be more telling for you

thanks
dmesg.txt

[PartialVolume]

Can you post the output of a file called nohup.out. You will find it in the / directory in virtual memory not on the USB stick. This file is a log produced by the networking script which shows DHCP requests and network port status.

A system with a working network will have a log that looks something like this:

[OK] eth0 is down
[OK] eth1 is down
[OK] eth2 is down
more: read error: Invalid argument
udhcpc: started, v1.36.1
udhcpc: broadcasting discover
udhcpc: no lease, forking to background
[OK] eth0 is up

if you run the command tail -f nohup.out then pull the ethernet lead out and plug it back in, you should see the status reflected in this file. This might give us a clue as to what's going on.

[ehn29]

I have these messages but right after I have this one

[OK] eth0 is down

result of tail -f nohup.out

nohup.out.log

[PartialVolume]

Have you got a working DHCP router or server on your network or is everything static?

[PartialVolume]

I think you said it worked ok from the internal ethernet port it's just the USB ethernet adapter that's the problem so I'm guessing your DHCP server/router is fine.

[PartialVolume]

According to nohub it looks like it's broadcasting a DHCP request but not getting a response, it then initialises the network port and trys again and again.

What's the make/model of the USB adapter?

[ehn29]

I have a dhcp server and it works.I tried with DA200, DA310, WD15 and WD19 adapters from Dell. The problem occurs for these 4 adapters and on several computer modelsLe 11 déc. 2024 à 22:07, PartialVolume ***@***.***> a écrit : According to nohub it looks like it's broadcasting a DHCP request but not getting a response, it then initialises the network port and trys again and again. What's the make/model of the USB adapter? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[PartialVolume]

I'll order up a DA200 and get back to you.

[PartialVolume]

Received the DA200 today and I can see the issue. Basically the network is initialised prior to the DA200 being available which is causing the USB ethernet to be missing from /etc/network/interfaces.

I'll work out the best way to resolve this while taking into account the USB ethernet interface could be unplugged and plugged back in while ShredOS is running so needs to cope with such a scenario.