On Sat, Aug 02, 2008 at 01:21:36PM -0400, Robert Craig wrote:
> About mid way through this forum thread is a good description of the ioctl usage with io-pkt.
> 
> http://community.qnx.com/sf/discussion/do/listPosts/projects.networking/discussion.drivers.topc1801
> 
> The short answer is that because you can't pass pointers around with the ioctl in a message passing OS, you have to 
wrapper the  ioctl calls in your application.
> 
>   You'll probably still have some questions after reading the post, but that's a good place to start.
> 

There is a PR internally to make some of the common ioctls
that use embedded pointers more 'intuituve'.  Since they
need special case handling there may always be some that
need to be addressed on a per instance basis.

-seanb

Hi,

More update on this. Apparently, I see this problem when I package io-pkt into our BSP but if I keep all binaries inside
 the stage directory and create an environment around it then the vlan configuration works just fine.

Looks like an environment issue. Is there a specific environment setting I need to create? Im running only io-pkt and so
 I start iopkt off and then mount all io-net network drivers followed by any other protocol I need like qnet etc...

Any advise of help would be much appreciated.

Thanks,
Santosh
> Hi There,
> 
> Things seemed to be working with VLAN creation but for some reason, it stopped
>  working for me and I'd like to get some urgent help on this.
> 
> I am using io-pkt (I think revision 400) a little old but I have applied some 
> changes to io-pkt to support one feature currently available in RFC2292 only. 
> Everything else seems to be working fine excepting that I cannot create VLAN 
> groups. I would like to add that it used to work a while back but not any more
> . The difference is that currently I am packaging io-pkt into a BSP and 
> previously I used to run it out of compact flash. Im assuming that shouldnt 
> make a difference.
> 
> Anyway, the exact problem is that the VLAN interface gets created, but in the 
> following creation, ifconfig does a get of the interface and that fails.
> 
> Following the stack trace upon executing ifconfig vlan4 create vlan 256 vlanif
>  en4:
> 
> Thread [2] (Suspended)	
> 	9 vlan_ioctl() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/
> net/if_vlan.c:610 0x48081ca8	
> 	8 in_control() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/
> netinet/in.c:587 0x48085ae8	
> 	7 udp_usrreq() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/
> netinet/udp_usrreq.c:1282 0x480eb160	
> 	6 compat_ifioctl() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/
> sys/compat/common/uipc_syscalls_43.c:620 0x480fda24	
> 	5 ifioctl() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/net/
> if.c:2160 0x480618b4	
> 	4 soo_ioctl() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/
> kern/sys_socket.c:182 0x480d3b8c	
> 	3 tcpip_devctl() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/
> msg.c:1567 0x480ad6c8	
> 	2 startproc() /media/sda2/workspace/mv/ne/thirdparty/Networking/trunk/sys/
> proc.c:703 0x480ba3e8
> 
> The exact area where the problem is discovered is:
> 
> memset(&vlr, 0, sizeof(vlr));
> if (ifv->ifv_p != NULL) {
>     snprintf(vlr.vlr_parent, sizeof(vlr.vlr_parent), "%s",
>     ifv->ifv_p->if_xname);
>     vlr.vlr_tag = ifv->ifv_tag;
> }
> #ifndef __QNXNTO__
> 	error = copyout(&vlr, ifr->ifr_data, sizeof(vlr));
> #else
> 	error = copyout(&vlr, data + sizeof(*ifr), sizeof(vlr));
> 
> The contents of ifv is:
> ifv	0x48563a00	
> 	ifv_u	{...}	
> 	ifv_p	0x00000000	
> 	ifv_mib	{...}	
> 	ifv_mc_listhead	{...}	
> 	ifv_list	{...}	
> 	ifv_flags	0	
> 	ifv_alloc	0x485639e0	
> 
> 
> 
> and quite obviously, the code returns with a BAD Address error. I dont know 
> what happened to the data passed in the ioctl, seems like it never got to this
>  point. How can I proceed to debug this?
> 
> 
> Another issue is that during creation of vlan interface, the interface flags 
> are set to IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST. Beats me as to why it 
> is defaulted to SIMPLEX. Any idea? This is in the vlan_clone_create() function
>  in sys/net/if_vlan.c
> 
> Thank you in Advance.
> 
> -Santosh
> 
> 
> 
> > Hi,
> > 
> > I tried to programmatically add and delete VLAN group by using the following
>  
> > ioctl calls. Doesn't work as intended. I then...