Hi there, how are you?

We're trying to get the max possible performance (throughput) out of our servers. Here are some context followed by the main changes we did and then a lot of questions in regard of Intel 82599 and linux parameters, please let us know if we miss any part or ask if you need any further clarification. (like buffer/queue sizes, ring buffer, qdisc or rcv/send buffer)

Context:

• Goal: to get the max throughput through packet locality (latency isn't to bother under 0.5s)
• Load: mostly video (streaming) chunks, ranging from 170KB to 2.3MB
• App (user land): nginx (multi process pined by each core)
• OS (kernel): RHEL 7.4 (3.10)
• NIC (driver): Intel(R) 82599 10 Gigabit Dual Port Network Connection (rev 01) (ixgbe - 5.3.7)
• Bonding: Bonding Mode: IEEE 802.3ad Dynamic link aggregation (it's a single card with two inputs 10Gbps each giving us 20Gbps)
• HW: CPU=Intel(R) Xeon(R) CPU E5-2630L 0 @ 2.00GHz, Hyper Thread=off, CPU's socket=2, CPU's core: 12, 64GB RAM
• NUMA layout:

available: 2 nodes (0-1)

node 0 cpus: 0 1 2 3 4 5

node 0 size: 32605 MB

node 0 free: 30680 MB

node 1 cpus: 6 7 8 9 10 11

node 1 size: 32767 MB

node 1 free: 30952 MB

node distances:

node   0   1

  0:  10  20

  1:  20  10

What we did:

• Install the latest driver (ixgbe - 5.3.7)
• Run set_irq_affinity -x local ethX with `x` option (enabling RSS and XPS)  and for local NUMA
• Enabled Flow director: ntuple-filters on
• Set affinity for our user land application (nginx's worker_cpu_affinity auto)
• XPS seems to be enabled (cat /sys/class/net/eth0/queues/tx-0/xps_cpus)
• RSS seems to be working (cat /proc/interrupts | grep eth)
• RFS seems to be disabled (cat /proc/sys/net/core/rps_sock_flow_entries; shows 0)
• RPS seems to be disabled (cat /sys/class/net/eth3/queues/rx-10/rps_cpus ; show 00000,00000 for all queues)

Questions:

1. Do we need to enable RPS for the (HW acc) RSS to work? (when we check /sys/class/net/eth0/queues/rx-0/rps_cpus it does has 00000000,00000000 for all the queues)
2. Do we need to enable RFS for the Flow Director to work? (cat /proc/sys/net/core/rps_sock_flow_entries; shows 0)
3. Do we need to add any rule for Flow Director to work? (on TCP4 case, since we can't see any explicit rule we supposed it uses the perfect hash (src and dst ip and port))
4. How can we be sure that RSS and flow director are working properly?
5. Why can't we use the most modern QDisc for this multiple queue driver/NIC? (like fq or fq_codel we tried to set up with sysctl net.core.default_qdisc, is it because of multiple queues?)
6. Does a single NIC  only connects directly to a single NUMA node? (when we run set_irq_affinity -x local ethX it set all the queues to the first NUMA node)
7. If 6) is true then what's better for throughput: to pin the NIC to a single NUMA node or to spread the multiple queues into all the nodes?
8. Still if 6) is true then if we buy a second NIC card are we able to make it connected to the second NUMA node?
9. We tried to set coalescence for the TX ring buffer (ethtool -C eth3 tx-usecs 84) it just ignored our value, isn't possible to set coalescence for TX ring buffer?
10. Should we enable HT but use as few queues as real cpus/cores?

If you read until here, thank you very much

References:

• How to Set Up Intel® Ethernet Flow Director | Intel® Software
• https://www.kernel.org/doc/Documentation/networking/scaling.txt
• https://www.intel.com/content/dam/www/public/us/en/documents/reference-guides/xl710-x710-performance-tuning-linux-guide.…
• https://access.redhat.com/sites/default/files/attachments/20150325_network_performance_tuning.pdf
• https://blog.cloudflare.com/how-to-achieve-low-latency/

hello,

I have a HP ZBook 15 laptop, where the "Intel(R) Ethernet Connection I217-LM" device is used for wired Ethernet. I also have two GO-SW-8G Dlink Gigabit switch (https://eu.dlink.com/se/sv/products/go-sw-8g-8-port-gigabit-dlinkgo-switch ). Below, I will call these SW1 and SW2, for better understanding. Also from the Internet Service Provider, we have 1 Gigabit/sec bandwidth (T-Home Magenta1 pack).

There are two scenarios what I setup and the 1Gbps speed was not able to work (?) in the laptop in one case.

The scenario-1, when the 1G speed was working:

The internet modem is connected with a standard LAN cable to the PORT-1 in of the SW1. The Ethernet interface in my laptop is connected to the PORT-2 in SW1 with a standard LAN cable. In this case the Ethernet interface LinkSpeed was Gigabit. It was possible to see both in the indicator LED of the PORT-2 in SW1 -this was green-, and also in the Windows when checking the LinkSpeed of the Ethernet interface, please refer to this link, Google Photos

So, in Gigabit speed point of view there is no any issue in this scenario.

The scenario-2, when the 1G speed was not working, and the LinkSpeed down set to 100Mbps:

Just similar to scenario-1, the internet modem is connected with a standard LAN cable to the PORT-1 in of the SW1. Now SW2 comes to the path, thus PORT-2 in SW1 is connected to PORT-1 in SW2 with a standard LAN cable. The Ethernet interface in my laptop is connected to the PORT-2 in SW2 with a standard LAN cable. In this scenario, the indicator LEDs on the Dlink switches are green, meaning 1G speed in all used ports, except the PORT-2 in SW2 which goes to the laptop. The indicator LED was orange of this port, also checking the LinkSpeed in the Windows side, that shows 100Mbps speed, please refer to this link, Google Photos

I have tried set manually the LinkSpeed in the Windows for the Ethernet interface to 1G, but in this case the interface was "disconnected", so the wired Ethernet was gone in the list of  connections in Windows and the laptop has started to use my WIFI NW.

When I changed back the interface LinkSpeed to "Auto", that come back to 100Mbps, and the "internet connection" returned to use the wired connection.

I did other test by using another Gigabit device, what was a Gigabit router from Dlink, and when I was connect one of the LAN interface of the router to the PORT-2 (or 3, or so) in SW2, the indicator LED was green, meaning the speed was 1Gbps.

Last week, I was issued a support ticket to Dlink, but finally they have not seen any issue with my setup in their pint of view, and also got the info from them, the scenario-2 was working very well with 1G in their LAB.

Thus now, I think the problem is not with the Dlink switches, but with the Windows and/or I217-LM device, and I would like to get some instructions, hints, ect from you, about doing some kind of troubleshooting to identify the root of the issue I have.

This morning I just refreshed the driver of the I217-LM to "Intel ® Network Connections Version:"22.9.6.0"", but I got the same result, so the expected 1Gbps LinkSpeed is not seen when both Dlink switches are in the path.

For more detail info about the drivers on my laptop, please refer to the attached text file.

Please try help me.

Thanks for your help,

/Robi

I had a pair of I210 NICs (a dual-NIC motherboard) teamed via Static Link Aggregation and all was working fine until today when Windows 10 x64 decided to apply the April 2018 cumulative update. The page providing the respective drivers with ANS support (https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=64399) states that the latest version is 23.1 (dated 2018-02-21). Even with this latest driver, however, I can re-create the team, but it cannot be enabled. The only way to keep things in a sort of working state is to disable one of the NICs as well as the virtual team interface and keep only the other NIC active (i.e., not an ideal scenario).

Is there any chance that a new version of the driver will be available soon?

Thanks.

nvx

My Environment:

Server: Fujitsu PRIMERGY RX2530 M4

Ethernet Adapters: Intel Ethernet Connection X722 LOM (Two SFP+ ports)

Ethernet Adapters Firmware: 3.51

--

ESXi: 6.5 U2

i40en driver version: 1.5.8

--

Both ethernet ports are connected to Juniper EX4550 Virtual Chassis (Junos version 12.3R9.4).

Switch ports are in trunk mode with native vlan.

--

After server boot up ESXi show only one X722 port which is online and port pass traffic. When I assign vlan tag to this interface (also changing ip addresses) then port is online but no traffic.

By default dcbx protocol is enabled on all switch ports:

set protocols dcbx interface all

I disabled dcbx protocol on ports where ESXi server is connected:

set protocols dcbx interface xe-0/0/15.0 disable

set protocols dcbx interface xe-1/0/15.0 disable

After server reboot ESXi show two X722 ports which are online and vlan tag assignment is working.

Is this the i40en driver problem?

Hi

I want to run Ethernet Compliance Tests 10/100Mbps with I210-AT.

Are there any information available? I can not find anything in the datasheet.

E.g. create 100Mbps MLT-3 Random Test Pattern.

I can only find Test Mode Register Bits (15:13) in 1000Base-T Control Register (Page 0, Register 9) for Gigabit.

What is the purpose of 100 MB test select bits 3:2 of Copper Specific Control Register 3 - Page 0, Register 23 ?

What can I do with the PRBS Control - Page 26, Register 23 ?

Thanks for your help

Andrija

Hi Sharon and Ninwardspiral,

We are having similar problems with the exact same NIC, and by coincidence with the same breakout cable (although we tested many).

Driver and firmware are updated to the latest versions available (2.4.3 and 6.01 respectively):

version: 2.4.3

firmware-version: 6.01 0x800034af 1.1853.0

First cable that does not work: ( QSFP to 4x10G SFP+, amphenol, 2m)

From the manufacturer website: Each QSFP-SFP+ splitter cable features a single QSFP+ connector (SFF-8436) rated for 40-Gbps on one end and (4) SFP+ connectors (SFF-8431), each rated for 10-Gbps, on the other.

SF-QSFP4SFPPS-002 Amphenol Commercial Products | Cable Assemblies | DigiKey (exact cable we bought)

ethtool -m output:

Identifier : 0x03 (SFP)

Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)

Connector : 0x21 (Copper pigtail)

Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00

Transceiver type : FC: Copper Passive

Encoding : 0x00 (unspecified)

BR, Nominal : 10300MBd

Rate identifier : 0x00 (unspecified)

Length (SMF,km) : 0km

Length (SMF) : 0m

Length (50um) : 0m

Length (62.5um) : 0m

Length (Copper) : 2m

Length (OM3) : 0m

Passive Cu cmplnce. : 0x01 (SFF-8431 appendix E) [SFF-8472 rev10.4 only]

Vendor name : Amphenol

Vendor OUI : 78:a7:14

Vendor PN : 624400002

Vendor rev : A

Option values : 0x00 0x00

BR margin, max : 0%

BR margin, min : 0%

Vendor SN : APF1718002044N

Date code : 170513

ethtool <intf> output (after bringing interfaces up):

Supported ports: [ ]

Supported link modes: Not reported

Supported pause frame use: Symmetric

Supports auto-negotiation: No

Advertised link modes: Not reported

Advertised pause frame use: No

Advertised auto-negotiation: No

Speed: Unknown!

Duplex: Unknown! (255)

Port: Other

PHYAD: 0

Transceiver: internal

Auto-negotiation: off

Supports Wake-on: d

Wake-on: d

Current message level: 0x0000000f (15)

drv probe link timer

Link detected: no

Second cable that does not work: ( QSFP to 4x10G SFP+, generic brand):

2m(6.6ft) 40G QSFP+ to 4SFP+ Passive Breakout DAC Cable | FS.COM

ethtool -m <intf> output:

Identifier : 0x03 (SFP)

Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)

Connector : 0x21 (Copper pigtail)

Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00

Transceiver type : FC: Copper Passive

Encoding : 0x00 (unspecified)

BR, Nominal : 10300MBd

Rate identifier : 0x00 (unspecified)

Length (SMF,km) : 0km

Length (SMF) : 0m

Length (50um) : 0m

Length (62.5um) : 0m

Length (Copper) : 2m

Length (OM3) : 0m

Passive Cu cmplnce. : 0x03 (unknown) [SFF-8472 rev10.4 only]

Vendor name : FIBERSTORE

Vendor OUI : 00:00:00

Vendor PN : QSFP-4SFP10G-DAC

Vendor rev :

Third Cable, it does work but its not what we need:

https://www.brack.ch/delock-direct-attach-kabel-330520

As a way to see if the NICs work, we also bought a SFP+ to SFP+ cable that is supposed to support SFP MSA and SFF-8431, but not SFF-8472. What is impressive is that this cable is detected and allows us to bring the link up

and even exchange some data at 10gbps. However, that is not what we need.

Encoding : 0x00 (unspecified)

BR, Nominal : 10300MBd

Rate identifier : 0x00 (unspecified)

Length (SMF,km) : 0km

Length (SMF) : 0m

Length (50um) : 0m

Length (62.5um) : 0m

Length (Copper) : 1m

Length (OM3) : 0m

Active Cu cmplnce. : 0x0c (unknown) [SFF-8472 rev10.4 only]

Vendor name : CISCO-TYCO

Vendor OUI : 00:40:20

Vendor PN : 2127493-1

Vendor rev : A

Option values : 0x00 0x12

Option : RX_LOS implemented

Option : TX_DISABLE implemented

BR margin, max : 0%

BR margin, min : 0%

Vendor SN : 164800277_______

Settings for ens787f3:

Supported ports: [ FIBRE ]

Supported link modes: Not reported

Supported pause frame use: Symmetric

Supports auto-negotiation: No

Advertised link modes: Not reported

Advertised pause frame use: No

Advertised auto-negotiation: No

Speed: 10000Mb/s

Duplex: Full

Port: Direct Attach Copper

PHYAD: 0

Transceiver: internal

Auto-negotiation: off

Supports Wake-on: d

Wake-on: d

Current message level: 0x0000000f (15)

drv probe link timer

Link detected: yes

Fourth Cable (to be delivered):

Intel X4DACBL3 40G QSFP+ Breakout DAC Cable | FS.COM

We are waiting for a fourth cable (this time is supposed to be intel compatible, but we dont know if it will be compatible with our switch...).

Why is the amphenol cable not working if the output of ethernet says: (SFF-8431 appendix E) [SFF-8472 rev10.4 only] which as stated in : Compatible SFP+ Modules, SFP Modules, and Cables for Intel® Ethernet...  should be enough to be compatible. Why

only SFP+ to SFP+ cables work? What should we do? We spent to many resources and time buying different cables.

And to finish, would this NIC Intel® Ethernet Network Adapter XXV710-DA2 Product Specifications  give us better results?

Thanks.

Edgar

Hello, I've been having trouble with this NIC not booting off of PXE.  I've already set the 10Gbe interface as a booting interface in the BIOS.  During PXE, I get the error message: PXE structure was not found in the UNDI driver code segment.  When it first didn't work, I used nvmupdate64e to update the NIC firmware.  nvmupdate now tells me my firmware is up to date (at version 6.01).  However, I still get the same exact error message at PXE boot.  I have also tried enabling PXE flash firmware for the interfaces.  But I still get the same error after all these driver installs and configuration enables. 

lspci -vv | grep -i 'Intel Corporation Ethernet Controller X710'

81:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

81:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

./bootutil64e

Port     Network Address     Location     Series     WOL     Flash Firmware          Version

3          6805CA385DF0      129:00.0     40GbE    N/A       UEFI,PXE Enabled     1.0.66

4          6805CA385DF1      129:00.1     40GbE    N/A       UEFI,PXE Enabled     1.0.66

ethtool -i eth2

driver: i40e

version: 1.5.10-k

firmware-version: 6.01 0x80003483 1.1747.0

bus-info: 0000:81:00.0

./nvmupdate64e

Num      Description                                                       Ver.      DevId     S:B          Status

01          Intel (R) I350 Gigabit Network Connection      1.99      1521      00:0001   Update not available

02          Intel(R) Ethernet Converged Network             6.01      1572      00:129     Up to date

              Adapter X710-2

Any idea what I need to do to get this interface to PXEboot?  eth2 is the interface that I am using.

Hi，all！

We're planning a product with a 10 GBE Interface.

We want to use X550-AT2 as the controller.  

The CPU in the system is a Q-Seven module.

The link between X550-AT2 and CPU is PCI-E Gen3。

In the datasheet of X550, the PCI-E width is described as x1, x4 or x8。But in our system, we can only use a x2 width。

I wonder whether the x2 width can be supported by X550-AT2? Or it can only be recognized as a x1 width?

thanks sincerely.

I have a Windows 10 system on Z370 chipset with INTEL® ETHERNET CONNECTION I219-V.

Latest drivers is installed.

When I'm trying to use "cast to" option, it falls with error "can't connect to device".

But when I insert additional USB Ethernet adapter, connect it to the same ethernet patch cord, option "cast to" works fine.

So, problem is in I219-V.

How ti fix this problem with DLNA casting?

I've installed the driver PRO2K3XP_32 on HP Proliant ML350 Win 2003 Server, but the Intellan tree 1.3.6.1.4.1.343 is empty. How may I show the SNMP Lan Status?

Hi,

We are trying to integrate the I350-F2 Ethernet card to our products, and we are facing to this problem: The I350-F2 is detected but the 2 Ethernet Ports are not recognised. It seems that there is a conflict between the 2 Ethernet ports of the motherboard and the 2 Ethernet port of the I350-F2.

Here is the output  ifconfig:

__tmp370698911 Link encap:Ethernet  HWaddr A0:36:9F:67:D3:C9

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

__tmp1412522235 Link encap:Ethernet  HWaddr A0:36:9F:67:D3:C8

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:1535 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1535 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1856694 (1.7 MiB)  TX bytes:1856694 (1.7 MiB)

eth0      Link encap:Ethernet  HWaddr 0C:C4:7A:72:2E:9A

          inet addr:192.168.3.200  Bcast:192.168.31.255  Mask:255.255.224.0

          inet6 addr: fe80::ec4:7aff:fe72:2e9a/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:106167 errors:0 dropped:0 overruns:0 frame:0

          TX packets:903 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:8426155 (8.0 MiB)  TX bytes:81922 (80.0 KiB)

eth1      Link encap:Ethernet  HWaddr 0C:C4:7A:72:2E:9B

          inet addr:192.168.3.195  Bcast:192.168.31.255  Mask:255.255.224.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Here is the dmesg log:

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: eth0: (PCIe:5.0GT/s:Width x4) <6>igb 0000:02:00.0: eth0: MAC: a0:36:9f:67:d3:c8

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: eth0: PBA No: G15813-004

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: PCI INT B -> GSI 36 (level, low) -> IRQ 36

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: eth1: (PCIe:5.0GT/s:Width x4) <6>igb 0000:02:00.1: eth1: MAC: a0:36:9f:67:d3:c9

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: eth1: PBA No: G15813-004

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: eth2: (PCIe:2.5GT/s:Width x1) <6>igb 0000:07:00.0: eth2: MAC: 0c:c4:7a:72:2e:9a

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: eth2: PBA No: 013A00-000

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: eth2: (PCIe:2.5GT/s:Width x1) <6>igb 0000:08:00.0: eth2: MAC: 0c:c4:7a:72:2e:9b

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: eth2: PBA No: 011000-000

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

Kernel: 2.6.29.6

igb driver : 5.0.6

Is there a solution for this issue ?

If you need more info, don't hesitate to ask me.

Thank in advance.

When I try to install the newest NIC driver 23.2 on my Windows 1803 X64 system the system freezes just after the installation start. What goes wrong ?

I had a pair of I210 NICs (a dual-NIC motherboard) teamed via Static Link Aggregation and all was working fine until today when Windows 10 x64 decided to apply the April 2018 cumulative update. The page providing the respective drivers with ANS support (https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=64399) states that the latest version is 23.1 (dated 2018-02-21). Even with this latest driver, however, I can re-create the team, but it cannot be enabled. The only way to keep things in a sort of working state is to disable one of the NICs as well as the virtual team interface and keep only the other NIC active (i.e., not an ideal scenario).

Is there any chance that a new version of the driver will be available soon?

Thanks.

nvx

hi intel corp  I will give you some ideas to help

why you don't make a new gaming modem you can see that netgear and other corps that make gaming modem but the gaming modem they make are not strong for real gaming always there problems always

I think is time intel that you can compete in gaming modem the true is that gaming modem technology is very weak for real time gaming networking for online multiplayer game that use heavy traffic network use

is time that you make something very power for gaming cable modem for that support all providers

here ideas of the gaming cable modems

make the modem support real speed for download and upload 10,000mb download and 10,000 upload

make something that can use a super fast memory of 1gb  ram or more

make a extreme super fast  cpu dedidcate it 6 or 8 core for the gaming modem  2.0ghz or higther

dedicate it 10 gigabit ports that support 10,000mbs

64 extreme  download  channels and 64  extreme upload channels

support all dosics up to 3.1 in download and upload too

make to select any channels download and upload to first star or change it

extreme next gen  wapa 3 wirless security and extreme speed

extreme turner modulation 10,000ghz that remove static,noise,and clean the signal ,and voltage protection

new futuristic desing for gamers

dedicate it motherboard and hardware for gaming

full firmware gaming software

internal speed test software too

…………………………………………..

next gen turbo custom firewall  so you can play with the firewall and be secure or disable and don't slowdown the network performance and speed

firewall ids ips  (https encription or highter security level )

next gen anti exploit tech

anti scrips attack protections

login modem https or highter to prevent hackers by pass the modem login

next gen ddos and dos attacks protections

turbo pakage deep inpection so the network don't slowdown

port scan protection

anti ramsomeware protection

web anti exploit protection

next gen network monitor to see all program and device and ect running  and see the speed of any device using and ect

make real time detections for applications and ect

make to enable or disable any device  or only the device you what to allow in lan network and wirless to be secure in both sides

make to detect ip conflict and fix it automatic

make next gen nat that have nat aceleration this will improve the network performance and security and that don't have conflict with other modems so you can open it and don't have problem in games

improve next gen comunication

improve next gen vpn  make turbo vpn and solid security

improve mac security to prevent hackers clone your mac address  and ip from your modem and devices

make a modem test this test is to detect if any part of the modem is not working or is damage by voltage or any part

make support for ip4 and ip6 in all the areas

make a new technology that the modem can scan multiple ip  and process the ip super fast this can reduce ping time when you will enter a website and gaming

make a new tech for network boost acceleration

improve 500% network stavility in all areas

prevent hakers enter remotely to the modem only the provider with a secure login

make the next gen firmware so you can update the modem with a secure firmware update  that don't infect with malware /and don't forget to always make update for the modem and improve ect

next gen turbo qos

make to change the modem ip login  incase you don't whant to be for example 192.168.0.1 you can change it to 192.200.01 this is example so you can change it to ect you whant

make to disable or enable any uknow ip or any ip

you can add a antivirus if you whant

add full 4k and 8k support for real speed

ect  this is your opportunity intel to start selling for the first time in history real solid gaming cable modems that support all providers

this will allow gamers have better connection and better stavility and security...…….. most gaming modem right now sucks

I am just helping think this is a good idea

add more features and ect

10-4 out

Hi.

So my problems is that with latest version of windows VLANS dont activate they stay disabled state, reinstalling drivers does nothing and they are newest version from intels website.

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Ou snap

Message was edited by: Tiit Talts

Hi Team,

Few nic ports are unable to initialize, please help to fix the issue.

Error Logs:

Hello,

I just received my new dell server and the Intel x550-t2 card does not show up in the vmware console.  Do I need to install drivers for it to work properly?  It is displayed as compatible with VMWare so I thought it would work right out of the box but that doesn't seem to be the case.

This issue was covered here but was NOT resolved and mark answered by accident.

VLANs disabled in Windows 10 Build 17133.1 Version 1803

My steps were as follows

1. Ran fine with Windows 10 Ver. 1709 for months using multiple tagged VLANs and one untagged VLAN on Intel NUC NUC6i7KYK (aka Skull Canyon) and Intel i219-LM NIC.
2. Clean installed Windows 10 Build 17133.1 Version 1803 with latest Drivers from Intel.
3. Recreated all my tagged VLANs only to find they were all DISABLED.
4. Permanently removed Intel NIC 23.1 driver and installed previous Intel NIC 22.9 driver with no luck still.
5. Clean installed Windows 10 Ver. 1709 with Intel NIC 23.1 driver.
6. Recreated all my tagged VLANs and BAM they all worked like normal.

In conclusion, the latest Intel NIC driver 23.1 seems fine but there is something wrong with Windows 10 Build 17133.1 Version 1803 Springs Creators Update, aka Redstone 4.

Hello,

I'm having some issues using VLANs on a new system. (See system Specs at Bottom)

Last coupe of days I have tried to update the drivers to make VLANs work on my laptop.

First driver I tried to install went well. I could see The VLAN tab when configuring my network connection.
However when I tried to add a VLAN the laptop gave me a BSOD with BAD_POOL_CALLER as error message.

I tried to reinstall a couple of times, rebooted a few times and it alway repaired itself to the previous Driver installed.
Driver used: Download Intel® Network Adapter Driver for Windows® 10

After some searching on the web I found that  alot of people had an issue like this. There was a problem with the ProSet option during the driver installation and one post suggested another driver provided by Intel that would fix the issue crashing.

Using this driver solved the BSOD issue, but whenever I make a VLAN, it deactivates itself. activating it doesn't work, it just stays deactivated.
Driver used: https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=...

After some searching on the web I found this article from 2016 saying that VLAN or teaming or not supported by windows 10 with the ProSet driver.

Because it was an old article I searched for a more  recent one and found this.

So I tried to install every driver beginning from the newest one and ending on 22.3 as the article says following:

Image may be NSFW.
Clik here to view.

Every driver has these same issues.

Driver page: Download Intel® Network Adapter Driver for Windows® 10

Anyone here who had/has similar issues?

Are there any known solutions for these issues?

Best regards,

Bert
----------------------------------------------------System Specifications

Manufacturer:Lenovo

Model: X1 Carbon

OS: Windows 10 Pro 64 Bit

Processor: Intel(R)  Core(TM) i7-7500U CPU @2.70GHz 2.90GHz

RAM: 16GB

Ethernet adapter: Intel(R) Ethernet Connection (4) I219-V

----------------------------------------------------

Hi,

I recently build my PC and noticed a very strange problem..While my download speed is fine, my upload speed is almost 0. However using the same Ethernet cable on my laptop, upload speed is fine (~5-6 Mbps). So problem is not with the cable.

Things i tried:

- Reset modem -> do not work

- Update all drivers including the Intel Ethernet connection driver 1219 (version 12.17.10.7) -> do not work

- Ipconfig/release & renew -> do not work

- Disable all windows services and stop running programs -> do not work

- Change the intel ethernet connection driver settings to increase throughput -> do not work

Kindly help me to figure out what is happening? My last resort is to buy a PCI-E Ethernet card but want to try everything before doing that..

PC Specs:

- OS: Windows 10 64 bit Home Edition

- Motherboard: Asus Rog Strix Z370-H Gaming

- CPU: Intel i5 - 6400 8th Gen

- GPU: MSI Geforce 1050Ti (4GB DDR5)

- RAM: Patriot 8GB x 2 DDR4 2400Mhz

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.