Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Networking/Discussion/Networking Drivers/devnp-e1000 does not support altq/List of Posts
Forum Topic - devnp-e1000 does not support altq: (7 Items)
   
Update
Serg Krivolapov(deleted)
03/22/2016 4:38 PM
post116002
devnp-e1000 does not support altq   
Good time of day!

When I try to use this driver together with a firewall pf would receive an error message:pfctl: wm0: driver does not 
support altq
Whether altq support in this driver is planned?

QNX version 650SP1.
Driver devnp-e1000.so version 13.01.16.
Hugh Brown
03/23/2016 9:50 AM
post116008
Re: devnp-e1000 does not support altq   
Please try the attached desktop build version of the driver. I have added
the altq support.



On 2016-03-22, 4:38 PM, "Serg Krivolapov" <community-noreply@qnx.com>
wrote:

>Good time of day!
>
>When I try to use this driver together with a firewall pf would receive
>an error message:pfctl: wm0: driver does not support altq
>Whether altq support in this driver is planned?
>
>QNX version 650SP1.
>Driver devnp-e1000.so version 13.01.16.
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post116002
>To cancel your subscription to this discussion, please e-mail
>drivers-networking-unsubscribe@community.qnx.com
Attachment: Text devnp-e1000.so.650 327.7 KB
Serg Krivolapov(deleted)
03/23/2016 12:30 PM
post116013
Re: devnp-e1000 does not support altq   
I am very grateful for the quick response!

A new version of the driver is no longer displays an error message, then it shows the statistics for queues and 
rules(pfctl -vsq, pfctl -vsr, pfctl -vss commands is working properly).
nicinfo wm0(1) shows the nonzero counters packet reception and transmission. There seems to be all right. I will 
continue testing.

Note the difference MTU and RTU default values for drivers devn-pcnet - 1514 bytes and devnp-e1000 - 1500 bytes. The 
hypervisor VMware ESXi 5 in the guest OS QNX6.5 supports only these two types of network cards.
For the driver devnp-e1000 it is impossible to change the default MTU and RTU by mtu=1514 option. Apparently because of 
different MTU values when using qnet protocol must be specified for all nodes in the network parameter mtu_en with a 
lower value (for example, mtu_en=1400).

Thanks.
Hugh Brown
03/24/2016 7:41 AM
post116019
Re: devnp-e1000 does not support altq   
The e1000 mtu value can be changed with ³ifconfig wm0 mtu xxxx².



On 2016-03-23, 12:30 PM, "Serg Krivolapov" <community-noreply@qnx.com>
wrote:

>I am very grateful for the quick response!
>
>A new version of the driver is no longer displays an error message, then
>it shows the statistics for queues and rules(pfctl -vsq, pfctl -vsr,
>pfctl -vss commands is working properly).
>nicinfo wm0(1) shows the nonzero counters packet reception and
>transmission. There seems to be all right. I will continue testing.
>
>Note the difference MTU and RTU default values for drivers devn-pcnet -
>1514 bytes and devnp-e1000 - 1500 bytes. The hypervisor VMware ESXi 5 in
>the guest OS QNX6.5 supports only these two types of network cards.
>For the driver devnp-e1000 it is impossible to change the default MTU and
>RTU by mtu=1514 option. Apparently because of different MTU values when
>using qnet protocol must be specified for all nodes in the network
>parameter mtu_en with a lower value (for example, mtu_en=1400).
>
>Thanks.
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post116013
>To cancel your subscription to this discussion, please e-mail
>drivers-networking-unsubscribe@community.qnx.com
Serg Krivolapov(deleted)
03/24/2016 10:13 AM
post116020
Re: devnp-e1000 does not support altq   
During testing the driver devnp-e1000 while copying large files a message appears in slog:
wm0: discarding oversize frame (len=1518)

By viewing the source code of function ether_input(struct ifnet *ifp, struct mbuf *m) (file sys/net/if_ethersubr.c) and 
found the following line:
if(m->m_pkthdr.len  > ETHER_MAX_FRAME(ifp, etype, m->m_flags & M_HASFCS))
{
  printf("%s: discarding oversize frame (len=%d)\n", ifp->if_xname, m->m_pkthdr.len);
  m_freem(m);
  return;
}

Probably not seting M_HASFCS.

In the driver source code function i82544_receive(...) (file e1000/event.c) I have not found setting the bit.

I think that in the function (and i82544_adv_receive(...)) should be the next line:
m->m_flags |= M_HASFCS; /* hardware appends FCS */
at some point before the call (*ifp->if_input)(ifp, rm)

This line I have seen in other drivers.
In this case, everything should work fine even with the default MTU=1500.

Thanks.
Hugh Brown
03/24/2016 10:46 AM
post116021
Re: devnp-e1000 does not support altq   
You must be receiving VLAN messages, as in all the testing we have done
here without VLAN, we don¹t see these messages.




On 2016-03-24, 10:13 AM, "Serg Krivolapov" <community-noreply@qnx.com>
wrote:

>During testing the driver devnp-e1000 while copying large files a message
>appears in slog:
>wm0: discarding oversize frame (len=1518)
>
>By viewing the source code of function ether_input(struct ifnet *ifp,
>struct mbuf *m) (file sys/net/if_ethersubr.c) and found the following
>line:
>if(m->m_pkthdr.len  > ETHER_MAX_FRAME(ifp, etype, m->m_flags & M_HASFCS))
>{
>  printf("%s: discarding oversize frame (len=%d)\n", ifp->if_xname,
>m->m_pkthdr.len);
>  m_freem(m);
>  return;
>}
>
>Probably not seting M_HASFCS.
>
>In the driver source code function i82544_receive(...) (file
>e1000/event.c) I have not found setting the bit.
>
>I think that in the function (and i82544_adv_receive(...)) should be the
>next line:
>m->m_flags |= M_HASFCS; /* hardware appends FCS */
>at some point before the call (*ifp->if_input)(ifp, rm)
>
>This line I have seen in other drivers.
>In this case, everything should work fine even with the default MTU=1500.
>
>Thanks.
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post116020
>To cancel your subscription to this discussion, please e-mail
>drivers-networking-unsubscribe@community.qnx.com
Serg Krivolapov(deleted)
03/24/2016 11:08 AM
post116022
Re: devnp-e1000 does not support altq   
I did not use the VLAN, but packets are lost between devn-pcnet (default nicinfo mtu=1514, but ifconfig show mtu 1500) 
and devnp-e1000 (default nicinfo and ifconfig is the same mtu=1500). Both hosts are working under VMware ESXi 5.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems