1 * FqCzCDVso-Strange behaviour from Sun FastEthernet Adapters

1 * FqCzCDVso-Strange behaviour from Sun FastEthernet Adapters

Post by Kbaa WMAIL-exch3 » Thu, 23 Sep 1999 04:00:00



Hi,

Having recently upgraded from 2.5.1 to 2.6, I've discovered some
strange problems with Sun ethernet Adapters, and wondered if anyone
could shed some light on it.

I have tried this on a couple of identical machines (Ultra 10's), each
with 3 adapters configured, hme0, 1 and 2 and the same problems occur.
Each adapter is connected to a separate subnet.

Problem 1:

On boot-up, only Hme0 can talk out on to the network. In order to get
hme1 and 2 to talk to their respective networks, I run snoop. This
appears to put the cards into promiscuous mode and they can then talk
to the network. Before running snoop, system cannot ping anything
except itself.

Problem 2:

On our internal network, we use a class B address with a 5 bit mask,
but the system cannot see any address above the first 254 hosts.

e.g hme1 = 172.16.8.1 mask = 255.255.248.0

I have added a route to get to another network:

172.16.16.0 netmask 255.255.248.0 172.16.8.1 1

in a normal world this should allow routing to addresses from
172.16.16.1 to 172.16.23.254, but the Sun can only see up to
172.16.16.254. In order to get it to see the other addresses, I have
to put explicit routes in such as 172.16.17.0 and 172.16.18.0, etc..

Anyone else had similar problems on 2.6? I've looked through the
patches on Sunsolve but cannot find anything that appears to be
related to these particular problems. Besides, I don't think it is a
common problem, otherwise I think I would have been able to find lots
of similar problems searching thru Usenet archives!

Many thanx for any input.

Cheers,

Nig

 
 
 

1. Strange behaviour from Sun FastEthernet Adapters

Hi,

Having recently upgraded from 2.5.1 to 2.6, I've discovered some
strange problems with Sun ethernet Adapters, and wondered if anyone
could shed some light on it.

I have tried this on a couple of identical machines (Ultra 10's), each
with 3 adapters configured, hme0, 1 and 2 and the same problems occur.
Each adapter is connected to a separate subnet.

Problem 1:

On boot-up, only Hme0 can talk out on to the network. In order to get
hme1 and 2 to talk to their respective networks, I run snoop. This
appears to put the cards into promiscuous mode and they can then talk
to the network. Before running snoop, system cannot ping anything
except itself.

Problem 2:

On our internal network, we use a class B address with a 5 bit mask,
but the system cannot see any address above the first 254 hosts.

e.g hme1 = 172.16.8.1 mask = 255.255.248.0

I have added a route to get to another network:

172.16.16.0 netmask 255.255.248.0 172.16.8.1 1

in a normal world this should allow routing to addresses from
172.16.16.1 to 172.16.23.254, but the Sun can only see up to
172.16.16.254. In order to get it to see the other addresses, I have
to put explicit routes in such as 172.16.17.0 and 172.16.18.0, etc..

Anyone else had similar problems on 2.6? I've looked through the
patches on Sunsolve but cannot find anything that appears to be
related to these particular problems. Besides, I don't think it is a
common problem, otherwise I think I would have been able to find lots
of similar problems searching thru Usenet archives!

Many thanx for any input.

Cheers,

Nig

2. Weird NFS behaviour in busybox

3. Lunix support for Sun Quad FastEthernet Adapter ?

4. POP/IMAP Config Problem

5. Sun fastethernet (hme) adapter

6. D-Link DFE-530TX ethernet card

7. Strange forking behavior (no offense intended) on Sun

8. PCI access from and app, ioremap

9. Quad Ethernet SBus and Quad FastEthernet SBus adapters in Ultra2

10. FastEthernet adapter for MC RS/6000 machines

11. Sun Quad FastEthernet 1.0 SQFE/S on Ultra 1

12. Multicast & Sun Fastethernet HME...

13. Sun FastEthernet 1.0 supported on Ultra?