2.4.35-pre1: new e1000 driver breaks old hardware

2007-06-15 Thread Wolfgang Nothdurft
Hi, with the new e1000 driver version 7.3.20 the onboard gigabit nic 82547EI (8086:1019) doesn't work correctly. After transferring about 100 megabytes over a gigabit link the transfer stopped and I have to reinit the link either by doing a ifconfig down/up or unplugging the network cable. The RxI

Re: 2.4.35-pre1: new e1000 driver breaks old hardware

2007-06-19 Thread Wolfgang Nothdurft
Kok, Auke wrote: > Wolfgang Nothdurft wrote: >> Hi, >> >> with the new e1000 driver version 7.3.20 the onboard gigabit nic 82547EI >> (8086:1019) doesn't work correctly. >> After transferring about 100 megabytes over a gigabit link the transfer >> sto

Re: 2.4.35-pre1: new e1000 driver breaks old hardware

2007-08-14 Thread Wolfgang Nothdurft
Kok, Auke wrote: Wolfgang Nothdurft wrote: Hi, with the new e1000 driver version 7.3.20 the onboard gigabit nic 82547EI (8086:1019) doesn't work correctly. After transferring about 100 megabytes over a gigabit link the transfer stopped and I have to reinit the link either by doing a ifc

Forcing the output interface using ip6_route_output doesn't work

2015-09-25 Thread Wolfgang Nothdurft
It seems that the ip6_route_output(net, sk, fl6) kernel function ignores the fl6.flowi6_oif parameter for the routing decision. Is this intended? Should it possible to force the output device for ipv6 routing just as for ipv4? Here the example shown with the ip command: With ipv4, I'm able t

Re: Forcing the output interface using ip6_route_output doesn't work

2015-09-26 Thread Wolfgang Nothdurft
Am 25.09.2015 um 23:13 schrieb David Ahern: On 9/25/15 7:56 AM, Wolfgang Nothdurft wrote: It seems that the ip6_route_output(net, sk, fl6) kernel function ignores the fl6.flowi6_oif parameter for the routing decision. It is considered, but a mismatch is not considered fatal. I think the