Network interface sees broadcasts but nothing else!?!

Network interface sees broadcasts but nothing else!?!

Post by Charles Gree » Tue, 27 Nov 2001 02:45:28



Hi,

Well, I've finally gotten our Performa 6400/200 to use the Asound ALM2
Ethernet card - almost.  The driver module (myson803) loads in my
LinuxPPC 2000 Q4 system with 2.2.18 kernel, it identifies the card
(vendor 1516 and device 803 - the chip is labeled as "ASOUND LAN-8139",
and I earlier tried the rti8139 and 8139too drivers without success),
and I can load an IP address.

While I see traffic leaving the card by using 'ethereal' on another
Linux box on the network, the only evidence that the card can receive
data is in response to an ARP request.  For example:
---
41 183.551804 3COM_cf:6e:79    ff:ff:ff:ff:ff:ff  ARP   Who has
192.168.0.99?  Tell 192.168.0.100
42 183.552137 Asound_ef:ca:f5  3COM_cf:6e:79      ARP   192.168.0.99 is
at 00:02:2a:ef:ca:f5
43 183.552165 192.168.0.100    192.168.0.99       ICMP  Echo (ping)
request
44 184.552094 192.168.0.100    192.168.0.99       ICMP  Echo (ping)
request
---
The LinuxPPC system (Asound_) sees the ARP broadcast and responds with
its IP address (set via 'ipconfig'), but it does not see the subsequent
'ping'.

It appears to me that the LinuxPPC can see broadcasts, but not packets
addressed to it.  For example, when attempting to use DHCP to set the
IP address:
---
13  78.269795 0.0.0.0          255.255.255.255    DHCP  DHCP Discover -
Transaction ID 0xef2a08d9
14  78.287393 192.168.0.1      192.168.0.101      DHCP  DHCP Offer    -
Transaction ID 0xef2a08d9
---
In the above exchange, packet 13 is from the LinuxPPC and packet 14 is
from the DHCP server to the LinuxPPC, which doesn't react.

One of the suggestions from the HOWTOs I located was to verify that
interrupts were being received.  If I check /proc/interrupts after
booting (when the system has attempted to initialize the interface with
DHCP), there are none, but as soon as I use 'ifconfig' to configure a
static IP address, there are, e.g., 43 interrupts on 25, and activities
such as 'ping' requests raise the number.

Has anyone seen behavior like this?  Any suggested solutions?  I'll be
happy to summarize Email replies.

Thanks,


 
 
 

1. single interface multiple networks + broadcast to all networks

Hello,

I have a machine which is in one network say 192.168.1.0.
But we have here a configuration where two networks 192.168.1.0
and 192.168.2.0 are local and directly available.
So I had to set up two routes to the local networks.
Now this machine should be a cups-server to both networks
and broadcast his cups-information into both networks.
I seems that I can sent only broadcast-packets  to the network
where the host belongs.
Is it so uncommon to sent broadcast into the other network?
Or must be the source of a broadcast packet originate in the same network?
Do I have to enable something under /proc/sys/net/...
Or is just cups broken?

Greetings,
        David

2. Data overruns?

3. Broadcasting with multiple network interfaces

4. ]

5. Broadcast RPC (Well, any network broadcast code...)

6. dhcpd option remove for specific client

7. HELP: Seeing nothing!!!!

8. Sun Micro. 3/60 or 3/80

9. Linux sees campus but nothing else

10. ifconfig sees eth0, but nothing seems to work

11. Redhat 6.0 - kppp connects but nothing else sees the connection

12. IPX broadcast packet not seen by app

13. BRINGING UP INTERFACE ETH1 - then nothing.