Doing more test, I used this command to configure network manually settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a a.b.c.d -g e.f.g.h -m i.j.k.l
With this, the interface up, but without Internet connection. After reboot, the interface feels to up correctly, but continues without connection. El jue., 4 jul. 2019 a las 23:40, Almudena Garcia (< liberamenso10...@gmail.com>) escribió: > > I didn't check It, but now I'll check > ps -e doesn't return any netdde process. > > > Did you try rtl8139 instead for instance? > > Now I'm trying It, but It shows the same problem. > > El jue., 4 jul. 2019 a las 23:32, Almudena Garcia (< > liberamenso10...@gmail.com>) escribió: > >> > After boot, before running the settrans command, is a netdde >> > process still running? You could also make sure no one is running before >> > running the settrans command by killing any that would still be running. >> >> I didn't check It, but now I'll check >> >> > Did you try rtl8139 instead for instance? >> >> Nope, I didn't try It, Only e1000 and pcnet, >> Btw, In my SMP kernel, I need a model which driver is inside Mach, >> because netdde drivers use to crash in It. >> >> El jue., 4 jul. 2019 a las 23:28, Samuel Thibault (< >> samuel.thiba...@gnu.org>) escribió: >> >>> Almudena Garcia, le jeu. 04 juil. 2019 23:18:21 +0200, a ecrit: >>> > I attach the full output of the command >>> >>> So the e1000 driver doesn't find the card, that's where the issue would >>> be. Possibly the boot-time netdde crashes and leaves the card in a very >>> odd state. After boot, before running the settrans command, is a netdde >>> process still running? You could also make sure no one is running before >>> running the settrans command by killing any that would still be running. >>> >>> Did you try rtl8139 instead for instance? >>> >>> Samuel >>> >>
