help Network driver

Dear all,

Subject: IOCTL error: no such interface for Bridge interface

Context: We are developing a Network Bridge Card for Cable-TV to Ethernet
running on QNX 4.25. Our driver interfaces with Net via Net.fd

Symptom: We are unable to run both ethernet and Our driver. Though both
drivers run (listed by ps), and though netinfo shows correct configuration
information for both interfaces, ifconfig of en1 fails with IOCTL error: no
such interface.

Details: Basic network installation works:

  1. Ethernet only startup

Net &

Net.etherXXXX -l1&

Socket MyHostName &

ifconfig en1 MyHostName up

A ping to another machine works

  1. Cable Networking only

Net &

CATVnet & # this is our program which maps to /dev/catvnet

Net.fd -l1 /dev/catvnet&

Socket MyHostName &

ifconfig en1 MyHostName up

A ping make our driver log it has received the ICMP packet

  1. Cable & Ethernet

Net -d3& #not sure that lo0 (loopback) counts as an interface

Net.etherXXXX -l1 &

CATVnet &

Net.fd -l2 /dev/catvnet&

Socket MyHostName &

ifconfig en1 MyHostName up

IOCTL error: no such interface

netstat -i shows en2 and lo0 only



can you help us understanding what could be the cause ?

YE

I don’t have an answer to your question but rather a question…

At the other end of the “CATVnet” is there a QNX box you need to talk to
natively
or are you just passing IP packets?

Because, if you are only using this for IP making CATVnet a PPP interface
for Socket
instead of Net.fd and handle all the inner workings for QNX networking is
probably
a lot easier.

Jay

“Daphne SA” <daphne.sa@bigfoot.com> wrote in message
news:9n4rs4$ott$1@inn.qnx.com

Dear all,

Subject: IOCTL error: no such interface for Bridge interface

Context: We are developing a Network Bridge Card for Cable-TV to Ethernet
running on QNX 4.25. Our driver interfaces with Net via Net.fd

Symptom: We are unable to run both ethernet and Our driver. Though both
drivers run (listed by ps), and though netinfo shows correct configuration
information for both interfaces, ifconfig of en1 fails with IOCTL error:
no
such interface.

Details: Basic network installation works:

  1. Ethernet only startup

Net &

Net.etherXXXX -l1&

Socket MyHostName &

ifconfig en1 MyHostName up

A ping to another machine works

  1. Cable Networking only

Net &

CATVnet & # this is our program which maps to /dev/catvnet

Net.fd -l1 /dev/catvnet&

Socket MyHostName &

ifconfig en1 MyHostName up

A ping make our driver log it has received the ICMP packet

  1. Cable & Ethernet

Net -d3& #not sure that lo0 (loopback) counts as an interface

Net.etherXXXX -l1 &

CATVnet &

Net.fd -l2 /dev/catvnet&

Socket MyHostName &

ifconfig en1 MyHostName up

IOCTL error: no such interface

netstat -i shows en2 and lo0 only



can you help us understanding what could be the cause ?

YE







\

“Daphne SA” <daphne.sa@bigfoot.com> wrote in message
news:9n4rs4$ott$1@inn.qnx.com

Dear all,

Subject: IOCTL error: no such interface for Bridge interface

Context: We are developing a Network Bridge Card for Cable-TV to Ethernet
running on QNX 4.25. Our driver interfaces with Net via Net.fd

You are in the wrong conference, this is for QNX6 related question.

Try the QNX4 conference.

Symptom: We are unable to run both ethernet and Our driver. Though both
drivers run (listed by ps), and though netinfo shows correct configuration
information for both interfaces, ifconfig of en1 fails with IOCTL error:
no
such interface.

I’m fairly sure Net.fd can be start on the second lan. What
if you inverse lan and start Net.fd on the first lan (-l1)

[cut]

Net -d3& #not sure that lo0 (loopback) counts as an interface

No lo0 doesn’t count

Net.etherXXXX -l1 &

CATVnet &

Net.fd -l2 /dev/catvnet&

Socket MyHostName &

ifconfig en1 MyHostName up

IOCTL error: no such interface

netstat -i shows en2 and lo0 only

can you help us understanding what could be the cause ?

Try setting Net.fd to use the serial port instead to see
if the problem is related to your CATVnet driver.
Is this CATVnet thing ethernet like?

I’m actually surprise this works at all. I would have though
that Socket expect/requires the device to be ethernet like,
thus requiring a valid MAC address. I did a setup like
this (with a custom network driver as well) and I had
to fake a MAC address to Net.fd (-a option I beleive),
and it worked very well.



YE







\