3Com 3c509/3c900/3c905 problems

QNX Newsgroups (Archives) qdn.public.qnxrtp.newuser
1

Hi

Years passed i had QNX running on my computer.
At last, with RTP, there’s possibility to show it to the people :slight_smile:

I’ve installed RTP, and here’s the problem description.

I had 3Com 3c900 installed.
Phlip showed me en0 device enabled (‘devices’ tab).

After manual IP configuration, everything seems to be ok :

pidin | grep io-net

86030 1 o-net/x86/o/io-net 10o SIGWAITINFO
86030 2 o-net/x86/o/io-net 10o RECEIVE 1
86030 3 o-net/x86/o/io-net 10o RECEIVE 1
86030 4 o-net/x86/o/io-net 21o RECEIVE 3
86030 5 o-net/x86/o/io-net 21r RECEIVE 14
86030 6 o-net/x86/o/io-net 17f CONDVAR 805d94c
86030 7 o-net/x86/o/io-net 10o RECEIVE 1
86030 8 o-net/x86/o/io-net 19f CONDVAR 8052268
86030 11 o-net/x86/o/io-net 18f CONDVAR 805c7a4

pidin ar | grep io-net

86030 io-net -pttcpip -ppppmgr
573474 grep io-net

pidin -p 86030 mem

pid tid name prio STATE code data
stack
86030 1 o-net/x86/o/io-net 10o SIGWAITINFO 36K 220K
8192(516K)*
86030 2 o-net/x86/o/io-net 10o RECEIVE 36K 220K
4096(12K)
86030 3 o-net/x86/o/io-net 10o RECEIVE 36K 220K
8192(12K)
86030 4 o-net/x86/o/io-net 21o RECEIVE 36K 220K
4096(132K)
86030 5 o-net/x86/o/io-net 21r RECEIVE 36K 220K
4096(132K)
86030 6 o-net/x86/o/io-net 17f CONDVAR 36K 220K
4096(132K)
86030 7 o-net/x86/o/io-net 10o RECEIVE 36K 220K
4096(12K)
86030 8 o-net/x86/o/io-net 19f CONDVAR 36K 220K
4096(132K)
86030 11 o-net/x86/o/io-net 18f CONDVAR 36K 220K
4096(132K)
ldqnx.so.1 @b0300000 300K 12K
npm-ttcpip.so @b034e000 72K 8192
npm-pppmgr.so @b0362000 20K 8192
devn-el900.so @b0369000 52K 8192

I’ve got tiny stack, thus, later we’ll see in /proc/ipstats some net
infos

nettrap

io-net -del900

nicinfo

3COM (90xB) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 00105A E161F7
Current Physical Node ID … 00105A E161F7
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0x6500 → 0x657F
Hardware Interrupt … 0xB

Total Packets Txd OK … 2
Total Packets Txd Bad … 0
Total Packets Rxd OK … 12
Total Rx Errors … 0

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx defered … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0

phlip -d

PHLIP spawn: netmanager -w all -f /etc/net.cfg

  • Contents of file ‘/etc/net.cfg’ (after spawn)
    % # nto network config file v1.2
    % version v1.2
    %
    % [global]
    % hostname gronk
    % domain ikp.pl
    % nameserver 157.25.5.18
    % nameserver 157.25.5.3
    % route 192.168.7.1 0.0.0.0 0.0.0.0
    %
    % [en0]
    % type ethernet
    % mode manual
    % manual_ip 192.168.7.11
    % manual_netmask 255.255.255.0
    %

cat /proc/ipstats

Ttcpip Sep 5 2000 08:56:16

verbosity level 0
ip checksum errors: 0
udp checksum errors: 0
tcp checksum errors: 0

packets sent: 83
packets received: 92

en0 : addr 192.168.7.11 netmask 255.255.255.0 up
lo0 : addr 127.0.0.1 netmask 255.0.0.0 up

DST: 192.168.7.0 NETMASK: 255.255.255.0 GATEWAY: en0
DST: 127.0.0.0 NETMASK: 255.0.0.0 GATEWAY: lo0
DST: 0.0.0.0 NETMASK: 0.0.0.0 GATEWAY: 192.168.7.1

TCP 127.0.0.1.2656 > 127.0.0.1.6000 ESTABLISHED snd 0
rcv 0
TCP 127.0.0.1.6000 > 127.0.0.1.2656 ESTABLISHED snd 0
rcv 0
TCP 0.0.0.0.6000 LISTEN

Don’t lokk at the packets sent/received number -when it wasn’t working
i had alway 0 there.

Till now, everything was ok.
Let’s see what ifconfig responds :

ifconfig -a

ifconfig: SIOCGIFMETRIC en0: Operation not supported
en0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX>
inet 192.168.7.11 netmask 0xffffff00 broadcast 192.168.7.255
ifconfig: SIOCGIFMETRIC en0: Operation not supported
ifconfig: SIOCGIFMETRIC lo0: Operation not supported
lo0: flags=49<UP,LOOPBACK,RUNNING>
address: 00:10:5a:e1:61:f7
inet 127.0.0.1 netmask 0xff000000

Answers aren’t proper - there’s no MAC address of the NIC,
and those SIOCGIFMETRIC messages…

Network isn’t working - no traffic to gateway, empty arp cache,
all this “advantages” when you got something wrong with NIC :slight_smile:)))

I’ve tried about 10 times with three NICs :

  • 3Com 3c509
  • 3Com 3c900
  • 3Com 3c905

Solution was : use full TCP stack instead of tiny one.

Here’s how to do it :
Change the file /etc/system/enum/include/net :

macro definitions for network

all

set(IONET_CMD, io-net -pttcpip -ppppmgr)

set(IONET_CMD, io-net -ptcpip )

I’ve skipped also pppmgr.

M.

2

Miroslaw Jaworski <mjaw@ipartners.pl> wrote:

ifconfig -a

ifconfig: SIOCGIFMETRIC en0: Operation not supported
en0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX
inet 192.168.7.11 netmask 0xffffff00 broadcast 192.168.7.255
ifconfig: SIOCGIFMETRIC en0: Operation not supported
ifconfig: SIOCGIFMETRIC lo0: Operation not supported
lo0: flags=49<UP,LOOPBACK,RUNNING
address: 00:10:5a:e1:61:f7
inet 127.0.0.1 netmask 0xff000000

ifconfig and route really don’t work very well with the small
stack. That is why you have to use phlip and netmanager.

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

3

Hello,
I noticed u said u tried using a couple 3com90x cards. I have one now,
and i have a Cable modem hooked to it. Problem i have is my modem won’t
initialize in qnx. Its weird because to have cable working i need 3
lights turned on on the modem. When i go into qnx, only 2 are on. When i
run netmanager the 3rd light flashes, but goes back off.

Any ideas what i could do to get this problem solved?
thnx for the help
terence

Miroslaw Jaworski wrote:

Hi

Years passed i had QNX running on my computer.
At last, with RTP, there’s possibility to show it to the people > :slight_smile:

I’ve installed RTP, and here’s the problem description.

I had 3Com 3c900 installed.
Phlip showed me en0 device enabled (‘devices’ tab).

After manual IP configuration, everything seems to be ok :

pidin | grep io-net

86030 1 o-net/x86/o/io-net 10o SIGWAITINFO
86030 2 o-net/x86/o/io-net 10o RECEIVE 1
86030 3 o-net/x86/o/io-net 10o RECEIVE 1
86030 4 o-net/x86/o/io-net 21o RECEIVE 3
86030 5 o-net/x86/o/io-net 21r RECEIVE 14
86030 6 o-net/x86/o/io-net 17f CONDVAR 805d94c
86030 7 o-net/x86/o/io-net 10o RECEIVE 1
86030 8 o-net/x86/o/io-net 19f CONDVAR 8052268
86030 11 o-net/x86/o/io-net 18f CONDVAR 805c7a4

pidin ar | grep io-net

86030 io-net -pttcpip -ppppmgr
573474 grep io-net

pidin -p 86030 mem

pid tid name prio STATE code data
stack
86030 1 o-net/x86/o/io-net 10o SIGWAITINFO 36K 220K
8192(516K)*
86030 2 o-net/x86/o/io-net 10o RECEIVE 36K 220K
4096(12K)
86030 3 o-net/x86/o/io-net 10o RECEIVE 36K 220K
8192(12K)
86030 4 o-net/x86/o/io-net 21o RECEIVE 36K 220K
4096(132K)
86030 5 o-net/x86/o/io-net 21r RECEIVE 36K 220K
4096(132K)
86030 6 o-net/x86/o/io-net 17f CONDVAR 36K 220K
4096(132K)
86030 7 o-net/x86/o/io-net 10o RECEIVE 36K 220K
4096(12K)
86030 8 o-net/x86/o/io-net 19f CONDVAR 36K 220K
4096(132K)
86030 11 o-net/x86/o/io-net 18f CONDVAR 36K 220K
4096(132K)
ldqnx.so.1 @b0300000 300K 12K
npm-ttcpip.so @b034e000 72K 8192
npm-pppmgr.so @b0362000 20K 8192
devn-el900.so @b0369000 52K 8192

I’ve got tiny stack, thus, later we’ll see in /proc/ipstats some net
infos

nettrap

io-net -del900

nicinfo

3COM (90xB) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 00105A E161F7
Current Physical Node ID … 00105A E161F7
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0x6500 → 0x657F
Hardware Interrupt … 0xB

Total Packets Txd OK … 2
Total Packets Txd Bad … 0
Total Packets Rxd OK … 12
Total Rx Errors … 0

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx defered … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0

phlip -d

PHLIP spawn: netmanager -w all -f /etc/net.cfg

  • Contents of file ‘/etc/net.cfg’ (after spawn)
    % # nto network config file v1.2
    % version v1.2
    %
    % [global]
    % hostname gronk
    % domain ikp.pl
    % nameserver 157.25.5.18
    % nameserver 157.25.5.3
    % route 192.168.7.1 0.0.0.0 0.0.0.0
    %
    % [en0]
    % type ethernet
    % mode manual
    % manual_ip 192.168.7.11
    % manual_netmask 255.255.255.0
    %

cat /proc/ipstats

Ttcpip Sep 5 2000 08:56:16

verbosity level 0
ip checksum errors: 0
udp checksum errors: 0
tcp checksum errors: 0

packets sent: 83
packets received: 92

en0 : addr 192.168.7.11 netmask 255.255.255.0 up
lo0 : addr 127.0.0.1 netmask 255.0.0.0 up

DST: 192.168.7.0 NETMASK: 255.255.255.0 GATEWAY: en0
DST: 127.0.0.0 NETMASK: 255.0.0.0 GATEWAY: lo0
DST: 0.0.0.0 NETMASK: 0.0.0.0 GATEWAY: 192.168.7.1

TCP 127.0.0.1.2656 > 127.0.0.1.6000 ESTABLISHED snd 0
rcv 0
TCP 127.0.0.1.6000 > 127.0.0.1.2656 ESTABLISHED snd 0
rcv 0
TCP 0.0.0.0.6000 LISTEN

Don’t lokk at the packets sent/received number -when it wasn’t working
i had alway 0 there.

Till now, everything was ok.
Let’s see what ifconfig responds :

ifconfig -a

ifconfig: SIOCGIFMETRIC en0: Operation not supported
en0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX
inet 192.168.7.11 netmask 0xffffff00 broadcast 192.168.7.255
ifconfig: SIOCGIFMETRIC en0: Operation not supported
ifconfig: SIOCGIFMETRIC lo0: Operation not supported
lo0: flags=49<UP,LOOPBACK,RUNNING
address: 00:10:5a:e1:61:f7
inet 127.0.0.1 netmask 0xff000000

Answers aren’t proper - there’s no MAC address of the NIC,
and those SIOCGIFMETRIC messages…

Network isn’t working - no traffic to gateway, empty arp cache,
all this “advantages” when you got something wrong with NIC > :slight_smile:> )))

I’ve tried about 10 times with three NICs :

  • 3Com 3c509
  • 3Com 3c900
  • 3Com 3c905

Solution was : use full TCP stack instead of tiny one.

Here’s how to do it :
Change the file /etc/system/enum/include/net :

macro definitions for network

all

set(IONET_CMD, io-net -pttcpip -ppppmgr)

set(IONET_CMD, io-net -ptcpip )

I’ve skipped also pppmgr.

M.

4

Terence <viperm5@home.com> wrote:

Hello,
I noticed u said u tried using a couple 3com90x cards. I have one now,
and i have a Cable modem hooked to it. Problem i have is my modem won’t
initialize in qnx. Its weird because to have cable working i need 3
lights turned on on the modem. When i go into qnx, only 2 are on. When i
run netmanager the 3rd light flashes, but goes back off.

Any ideas what i could do to get this problem solved?

Yes. Absolutely.

In order for DHCP to work, you MUST usae the machine name that
the cable modem people gave you. I am absolutely convinced that
they would not have told you your machine name was `gronk’


3COM (90xB) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 00105A E161F7
Current Physical Node ID … 00105A E161F7
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0x6500 → 0x657F
Hardware Interrupt … 0xB

Total Packets Txd OK … 2
Total Packets Txd Bad … 0
Total Packets Rxd OK … 12
Total Rx Errors … 0

Your network card is enabled, configured and handling packets. Your
problem is absolutely not your network card, or io-net


phlip -d

PHLIP spawn: netmanager -w all -f /etc/net.cfg

  • Contents of file ‘/etc/net.cfg’ (after spawn)
    % # nto network config file v1.2
    % version v1.2
    %
    % [global]
    % hostname gronk
    % domain ikp.pl
    % nameserver 157.25.5.18
    % nameserver 157.25.5.3
    % route 192.168.7.1 0.0.0.0 0.0.0.0
    %
    % [en0]
    % type ethernet
    % mode manual
    % manual_ip 192.168.7.11
    % manual_netmask 255.255.255.0

You should not be using manual mode. Even so, I don’t think the netmask
is correct anyway. My netmask on my cable mode comes up as 255.255.252.0

verbosity level 0
ip checksum errors: 0
udp checksum errors: 0
tcp checksum errors: 0

packets sent: 83
packets received: 92

en0 : addr 192.168.7.11 netmask 255.255.255.0 up
lo0 : addr 127.0.0.1 netmask 255.0.0.0 up

DST: 192.168.7.0 NETMASK: 255.255.255.0 GATEWAY: en0
DST: 127.0.0.0 NETMASK: 255.0.0.0 GATEWAY: lo0
DST: 0.0.0.0 NETMASK: 0.0.0.0 GATEWAY: 192.168.7.1

TCP 127.0.0.1.2656 > 127.0.0.1.6000 ESTABLISHED snd 0
rcv 0
TCP 127.0.0.1.6000 > 127.0.0.1.2656 ESTABLISHED snd 0
rcv 0
TCP 0.0.0.0.6000 LISTEN

Don’t lokk at the packets sent/received number -when it wasn’t working
i had alway 0 there.

Till now, everything was ok.
Let’s see what ifconfig responds :

ifconfig -a

ifconfig: SIOCGIFMETRIC en0: Operation not supported
en0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX
inet 192.168.7.11 netmask 0xffffff00 broadcast 192.168.7.255
ifconfig: SIOCGIFMETRIC en0: Operation not supported
ifconfig: SIOCGIFMETRIC lo0: Operation not supported
lo0: flags=49<UP,LOOPBACK,RUNNING
address: 00:10:5a:e1:61:f7
inet 127.0.0.1 netmask 0xff000000

Answers aren’t proper - there’s no MAC address of the NIC,
and those SIOCGIFMETRIC messages…

There definitely is a MAC address there and it matches the MAC
address from nicinfo…

address: 00:10:5a:e1:61:f7

Network isn’t working - no traffic to gateway, empty arp cache,
all this “advantages” when you got something wrong with NIC > :slight_smile:> )))

There is nothing wrong with your NIC. Your problem is quite simply that
you have set `gronk’ as your machine name/host name. If you set your
machine name to the correct name, and use DHCP, everything will work.

I’ve tried about 10 times with three NICs :

  • 3Com 3c509
  • 3Com 3c900
  • 3Com 3c905

You are wasting your time.

5

<pete@qnx.com> wrote in message news:8rfar9$s1v$1@nntp.qnx.com…

Terence <> viperm5@home.com> > wrote:
Hello,
I noticed u said u tried using a couple 3com90x cards. I have one now,
and i have a Cable modem hooked to it. Problem i have is my modem won’t
initialize in qnx. Its weird because to have cable working i need 3
lights turned on on the modem. When i go into qnx, only 2 are on. When
i
run netmanager the 3rd light flashes, but goes back off.

Any ideas what i could do to get this problem solved?

Yes. Absolutely.

In order for DHCP to work, you MUST usae the machine name that
the cable modem people gave you. I am absolutely convinced that
they would not have told you your machine name was `gronk’

I you sure about this Pete? I didn’t provide a name and it works
fine for me. I’m using a 3com card though :wink:

3COM (90xB) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 00105A E161F7
Current Physical Node ID … 00105A E161F7
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0x6500 → 0x657F
Hardware Interrupt … 0xB

Total Packets Txd OK … 2
Total Packets Txd Bad … 0
Total Packets Rxd OK … 12
Total Rx Errors … 0

Your network card is enabled, configured and handling packets. Your
problem is absolutely not your network card, or io-net

\

phlip -d

PHLIP spawn: netmanager -w all -f /etc/net.cfg

  • Contents of file ‘/etc/net.cfg’ (after spawn)
    % # nto network config file v1.2
    % version v1.2
    %
    % [global]
    % hostname gronk
    % domain ikp.pl
    % nameserver 157.25.5.18
    % nameserver 157.25.5.3
    % route 192.168.7.1 0.0.0.0 0.0.0.0
    %
    % [en0]
    % type ethernet
    % mode manual
    % manual_ip 192.168.7.11
    % manual_netmask 255.255.255.0

You should not be using manual mode. Even so, I don’t think the netmask
is correct anyway. My netmask on my cable mode comes up as 255.255.252.0

verbosity level 0
ip checksum errors: 0
udp checksum errors: 0
tcp checksum errors: 0

packets sent: 83
packets received: 92

en0 : addr 192.168.7.11 netmask 255.255.255.0 up
lo0 : addr 127.0.0.1 netmask 255.0.0.0 up

DST: 192.168.7.0 NETMASK: 255.255.255.0 GATEWAY: en0
DST: 127.0.0.0 NETMASK: 255.0.0.0 GATEWAY: lo0
DST: 0.0.0.0 NETMASK: 0.0.0.0 GATEWAY: 192.168.7.1

TCP 127.0.0.1.2656 > 127.0.0.1.6000 ESTABLISHED snd 0
rcv 0
TCP 127.0.0.1.6000 > 127.0.0.1.2656 ESTABLISHED snd 0
rcv 0
TCP 0.0.0.0.6000 LISTEN

Don’t lokk at the packets sent/received number -when it wasn’t working
i had alway 0 there.

Till now, everything was ok.
Let’s see what ifconfig responds :

ifconfig -a

ifconfig: SIOCGIFMETRIC en0: Operation not supported
en0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX
inet 192.168.7.11 netmask 0xffffff00 broadcast 192.168.7.255
ifconfig: SIOCGIFMETRIC en0: Operation not supported
ifconfig: SIOCGIFMETRIC lo0: Operation not supported
lo0: flags=49<UP,LOOPBACK,RUNNING
address: 00:10:5a:e1:61:f7
inet 127.0.0.1 netmask 0xff000000

Answers aren’t proper - there’s no MAC address of the NIC,
and those SIOCGIFMETRIC messages…

There definitely is a MAC address there and it matches the MAC
address from nicinfo…

address: 00:10:5a:e1:61:f7

Network isn’t working - no traffic to gateway, empty arp cache,
all this “advantages” when you got something wrong with NIC > :slight_smile:> )))

There is nothing wrong with your NIC. Your problem is quite simply that
you have set `gronk’ as your machine name/host name. If you set your
machine name to the correct name, and use DHCP, everything will work.

I’ve tried about 10 times with three NICs :

  • 3Com 3c509
  • 3Com 3c900
  • 3Com 3c905

You are wasting your time.

6

Mario Charest <mcz@videotron.ca> wrote:

pete@qnx.com> > wrote in message news:8rfar9$s1v$> 1@nntp.qnx.com> …
Terence <> viperm5@home.com> > wrote:
Hello,
I noticed u said u tried using a couple 3com90x cards. I have one now,
and i have a Cable modem hooked to it. Problem i have is my modem won’t
initialize in qnx. Its weird because to have cable working i need 3
lights turned on on the modem. When i go into qnx, only 2 are on. When
i
run netmanager the 3rd light flashes, but goes back off.

Any ideas what i could do to get this problem solved?

Yes. Absolutely.

In order for DHCP to work, you MUST usae the machine name that
the cable modem people gave you. I am absolutely convinced that
they would not have told you your machine name was `gronk’

I you sure about this Pete? I didn’t provide a name and it works
fine for me. I’m using a 3com card though > :wink:

Yes, I’m pretty sure you need to have the correct name.

If you don’t you can certainly set all the other stuff up manually
since your IP and other stuff is all static, but then you’re not
really using DHCP.

In the building here, our DHCP server doesn’t need the machine name
because it knows who you are from the MAC address of the ethernet
card you’re using, but the cable company has no way of forcing you
to use a specific ethernet card with a specific MAC address, so they
only know who you are by the machine name/ host name.

7

<pete@qnx.com> wrote in message news:8rg1u2$bj2$1@nntp.qnx.com…

Mario Charest <> mcz@videotron.ca> > wrote:

pete@qnx.com> > wrote in message news:8rfar9$s1v$> 1@nntp.qnx.com> …
Terence <> viperm5@home.com> > wrote:
Hello,
I noticed u said u tried using a couple 3com90x cards. I have one
now,
and i have a Cable modem hooked to it. Problem i have is my modem
won’t
initialize in qnx. Its weird because to have cable working i need 3
lights turned on on the modem. When i go into qnx, only 2 are on.
When
i
run netmanager the 3rd light flashes, but goes back off.

Any ideas what i could do to get this problem solved?

Yes. Absolutely.

In order for DHCP to work, you MUST usae the machine name that
the cable modem people gave you. I am absolutely convinced that
they would not have told you your machine name was `gronk’

I you sure about this Pete? I didn’t provide a name and it works
fine for me. I’m using a 3com card though > :wink:

Yes, I’m pretty sure you need to have the correct name.

If you don’t you can certainly set all the other stuff up manually
since your IP and other stuff is all static, but then you’re not
really using DHCP.

In the building here, our DHCP server doesn’t need the machine name
because it knows who you are from the MAC address of the ethernet
card you’re using, but the cable company has no way of forcing you
to use a specific ethernet card with a specific MAC address, so they
only know who you are by the machine name/ host name.

One think is certain Pete, the cable company where I live doesn’t required
the machine to be set to a specific name and it uses DHCP.

Lately I installed a home gateway (there is no way to set a name in that
box)
and it works wonder.

I think the cable company know who you are by talking directly with
the cable modem. I once called their tech support because I was loosing
connection once in a while. They asked me for the serial
number of my modem and a few seconds later they knew exactly
when and for how long I lost connection in the last week.
They send somebody to change something outside the house
and the problem never came back!

8

In the building here, our DHCP server doesn’t need the machine name
because it knows who you are from the MAC address of the ethernet
card you’re using, but the cable company has no way of forcing you
to use a specific ethernet card with a specific MAC address, so they
only know who you are by the machine name/ host name.

They key it off the MAC addie/IP of your modem. If you happen to have one
of the older Motorola modems (white ones…), they actually have know way of
knowing if you’re connected… But, nothing is keyed off the NIC card. I
happen to have all my machine names set to stuff different than the
hostnames the cable service provides. This is the usual @home policy
anyway. There is the off-chance that in Terence’s market they do require
the hostname, so I think he should try it, but more than likely it won’t
matter…

Mike Menefee

9

Mario Charest <mcz@videotron.ca> wrote:

pete@qnx.com> > wrote in message news:8rfar9$s1v$> 1@nntp.qnx.com> …
Terence <> viperm5@home.com> > wrote:
Hello,
I noticed u said u tried using a couple 3com90x cards. I have one now,
and i have a Cable modem hooked to it. Problem i have is my modem won’t
initialize in qnx. Its weird because to have cable working i need 3
lights turned on on the modem. When i go into qnx, only 2 are on. When
i
run netmanager the 3rd light flashes, but goes back off.

Any ideas what i could do to get this problem solved?

Yes. Absolutely.

In order for DHCP to work, you MUST usae the machine name that
the cable modem people gave you. I am absolutely convinced that
they would not have told you your machine name was `gronk’

I you sure about this Pete? I didn’t provide a name and it works
fine for me. I’m using a 3com card though > :wink:

I recall also that if you install from inside windows, we snarf your
machine name out of the registry anyway, so it might have just worked
for you.

What’s your /etc/net.cfg say Mario?

10

mikem@mnetwork.org.remove.this wrote:

They key it off the MAC addie/IP of your modem. If you happen to have one
of the older Motorola modems (white ones…), they actually have know way of
knowing if you’re connected… But, nothing is keyed off the NIC card. I
happen to have all my machine names set to stuff different than the
hostnames the cable service provides. This is the usual @home policy
anyway. There is the off-chance that in Terence’s market they do require
the hostname, so I think he should try it, but more than likely it won’t
matter…

I’m in Ottawa on Rogers cable @ home…

If I don’t give our phliup config dialog the correct DHCP ID
I most definitely don’t ever get successful DHCP configuration.

If I give it the same DHCP ID as the machine beside it connected
through a router to the same cable modem, both machines complain
about there being a conflict.

I do not give any other TCP/IP configuration information whatsoever.

I can pull out a network card and throw another one into either
machine, and neither of them will ever fail to get the DHCP config,
or get the wrong config.

I can boot any of Win98, Win2K or WinME on either machine, and their
successful configuration all depend solely on wether I give them
the correct machine name or not.

So in my area, DHCP is keyed off of the DHCP ID.