hello
i've update old routerOS on x86 machines to 3.28.

e1000 is recognized but not work. i've changed e1000, cable ecc.. but not work. i've try to use and old rtl and RTL work.

anyone with same problem?


regards giuseppe

did it work on previous version?..

3.23 work.

similar problem on RTL8139, some RX/TX error and after ping delay is huge, after eth freeze.

log by console, disable/enable ethernet and work...

on 3.23 works fine. with 90Mbit/s traffic without problem.
cable checked. switch changed, cable changed,
eth changed with new.

any ideaa??

make supout.rif and send to support@mikrotik.com with description of problem

i've doit!

but i think most mikrotik guy is on holliday...

of course. anyway, they can fix it / add a support of this card only in next version, it's not fast process...

yes..

but works fine on 2.9.. :S

I have same problem when testing in VirtualBox with any e1000 (Intet) card, and have to use PCNet (AMD) instead. If memory serves correct, it was last working in 3.17 x86.

Removing NIC drivers I gotta say is a CRITICAL thing you DO NOT want to mess with in a router software.

yup.

i've do some tests:

kvm:
- pcnet/rtl after huge traffic ( 70mbit ) in 20seconds ethernet freezed, link ok but not reciving
- e1000 recognized but not reciving anytime

vmware
- pcnet works fine, (300mbit full duplex TCP ) between 2 vms works good for 4 hours..
- e1000 recognized but not work

phisical
- e 1000 recognized but not work

mikrotik? where are you??

they are on weekend - it's sunday in Europe =)

ahaha

today, sunday, at 8.00AM i'm at office to work

Mikrotik,

Any fix yet on the e1000 driver? Is there a driver package we can download? I'm using v3.28 x86.

Please fix in v3.29. Thank You.

I saw a similar problem in Virtual Vmware with e1000 . Nics stop sending or receiving traffic after upgrade to 3.23 . I had to switch to a physical box with realtek nics. Fortunately this box was only for testing.

did anyone ever send a supout.rif file from such machine ?

did anyone ever send a supout.rif file from such machine ?

you cant do a supout because you cant connect to the machine using the e1000 !

serial cable, other NIC

I sended today a email with supout.rif file with a problematic E1000 adapter.

Please fix it asap.

no answer...

Come on Mikrotik's atleast answer anything here...

can't you use something other than e1000 in your VM? it's VM for a reason, you should be able to emulate something else. We don't remove anything, apparently the kernel we use has problems with this driver, and until next kernel upgrade we can't do much

atm i can use only AMD PCnet32 driver, which is not enough .

In MT i can see in interfaces list an ether1, ether2 (e1000's) but in status i see running but as some1 mentioned b4 cable seems to be unplugged. I tried with 3.23, 3.30, 4.0 and this bug is the same.

On this Esxi i use CentOS, Debian and so on with 2.4 and 2.6 kernels, and there is no problems with e1000.

we will add support in v4.2

we will add support in v4.2

Please hurry! (are you sure it's 4.2, so we have to wait 2 more releases for this fix?)

yes i'm sure, it's not as easy as you might think

which kernel version will be in 4.2?

we will add support in v4.2

Wrong again! It doesn't work. It just doesn't work. e1000 DOES NOT WORK IN 4.2. IT DOESN"T WORK.

Hello? Can you hear me? e1000 IS BROKE.

Some things to note:
e1000 was working in v3.22. It broke sometime after that (reported v3.23. Since then it's been broke. In v4.2 IT STILL DOESN'T WORK.

Mikrotik, I KNOW HOW THIS GOES. I BUILT EMBEDDED SYSTEMS with Buildroot, uClibc, and also tried OpenEmbedded. I've gotten the e1000 package from sourceforge integrated into my system using the SAME KERNEL VERSION as you do on RouterOS. PLEASE LISTEN.... WE NEED THIS FIXED. PLEASE LET ME HELP GET THIS INTO ROUTEROS.

Please people, we need to push Mikrotik real hard. This is very unacceptable. I'm very frustrated with various issues and Mikrotik simply ignores them. Mikrotik is a very stubbern company and soon gonna be alot of unhappy people.

Please respond and increase this thread. Also send many emails to Mikrotik. They need to fix this very soon. It's been way way too long...

we will add support in v4.2

Wrong again! It doesn't work. It just doesn't work. e1000 DOES NOT WORK IN 4.2. IT DOESN"T WORK.

Hello? Can you hear me? e1000 IS BROKE.

Some things to note:
e1000 was working in v3.22. It broke sometime after that (reported v3.23. Since then it's been broke. In v4.2 IT STILL DOESN'T WORK.

Mikrotik, I KNOW HOW THIS GOES. I BUILT EMBEDDED SYSTEMS with Buildroot, uClibc, and also tried OpenEmbedded. I've gotten the e1000 package from sourceforge integrated into my system using the SAME KERNEL VERSION as you do on RouterOS. PLEASE LISTEN.... WE NEED THIS FIXED. PLEASE LET ME HELP GET THIS INTO ROUTEROS.

Please people, we need to push Mikrotik real hard. This is very unacceptable. I'm very frustrated with various issues and Mikrotik simply ignores them. Mikrotik is a very stubbern company and soon gonna be alot of unhappy people.

Please respond and increase this thread. Also send many emails to Mikrotik. They need to fix this very soon. It's been way way too long...

I totally agree....

new driver is needed, we couldn't add it in v4.2. We will try to add it later

new driver is needed, we couldn't add it in v4.2. We will try to add it later

I just have to say this:

A router that doesn't support e1000 (that's been out for at least a few years). All other routers I've tried support this card.

Some things to think about as you continue to use Mikrotik RouterOS.

I have this issue with VMware.
The workaround was: after the mikrotik boot, I have changed the virtual NIC's "Network Label". Just choose something else (like Host-only network) and go back to the option that you wish to use.
The NIC will work ok until the next reboot.

I have this issue with VMware.
The workaround was: after the mikrotik boot, I have changed the virtual NIC's "Network Label". Just choose something else (like Host-only network) and go back to the option that you wish to use.
The NIC will work ok until the next reboot.

but this is not a solution in long terms....

Is anyone still having issues with e1000 drivers (Intel PRO/1000 NICs) on physical machines?

Something broke in after version 3.22 x86 and the e1000 driver no longer works with virtual machines it appears. I've tested e1000 on physical machine in v3 without success, but atm I won't have the machine to test for a few weeks. I assumed that since something broke with all VM's e1000 driver this must mean the driver in general (both physical and virtual).

Please report here if the driver still doesn't work on physical hardware, as Mikrotik may not be so worried about VM's.

I will report back on my test as soon as I have the hardware back in to test.

e1000 is fixed in v4.3

Just downloaded and tested v4.3 on VirtualBox using e1000 driver (any of them) and it works!

Thank you Mikrotik for fixing this issue.