Thank you for your quick answer ! Allow me some days for this test :
1 - I am at work these days
2 - it has been a while since I have dealt with custom kernels, I am a
bit rusty, it will be good to review this topic
--
Robert Grasso
@home
---
UNIX was not designed to stop you from doing stupid things, because
that would also stop you from doing clever things. -- Doug Gwyn
On 27/12/2016 01:12, Francois Romieu wrote:
Robert Grasso <robert.gra...@modulonet.fr> :
[dhcp snafu]
First of all, can you confirm that I am doing right in posting to you
(addresses found in README.Debian) ?
It isn't completely wrong.
If I do, can you help ? I am not very proficient with Ethernet, and I am not
able to figure out what my provider changed : their hotline is
underqualified, they are just able to tell that "the signal on the line is
ok".
You're spoiled. It is more than decent for a company whose core business
used to sell cable TV.
But if you want me to run various tests, try new versions, I would be
glad to do so : I would appreciate if I could salvage this Shuttle.
Please try a recent stable vanilla kernel and send a complete dmesg
from boot. I need to identify the specific 816x chipset.
Then record some traffic:
# touch gonzo.pcap && tshark -w gonzo.pcap -i eth1
It should only exhibit small outgoing packets but, well, one never knows.
Check the leds activity to be sure that the network interfaces have not
been renumbered.
Use ethtool to check that tso is disabled. If it isn't, disable it.
