Fragmented ping makes OSR5 reboot

Fragmented ping makes OSR5 reboot

Post by John W. Templ » Sun, 10 Nov 1996 04:00:00



I was testing my OSR5 servers to see if they were vulnerable to the
fragmented ping bug; one of them was not affected, while one of them
rebooted both times I tried it.  Both servers are running on Compaqs,
and both have net100 applied.  The only difference between them that I
can think would matter here is the network adapters.  The one that's
not affected is using the Compaq built-in adapter with Compaq's driver,
while the one that reboots is using an SMC 8013EWC with the
OSR5-supplied driver.  The Compaq driver requires a 4096 byte
STRMAXBLK; could using that value on the other system fix the problem?
--
John W. Temples, III       ||       Providing the first public access Internet
Gulfnet Kuwait             ||            site in the Arabian Gulf region

 
 
 

1. ping problem - only one ping made although -c option

Hi !

Another strange issue on my linux box...
When i do a "ping", it always transmits only _one_ packet
and then "hangs", I'll have to CTRL-C out to stop it.

It doesn't matter at all if i specify the -c option or not...
Its very likely that i messed up something on my box, because
that problem wasn't there a few weeks ago.

(I had some problems with shared libraries, maybe thats
where to start searching ?)

Example:

Centaur:/var/named # ping localhost -c 50
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.431 ms

--> no more packets here....after a few minutes CTRL-C'ing out:

--- localhost ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.431/0.431/0.431 ms

Any suggestion whats going wrong here?

Watz

2. character operations

3. ping don't fragment flag

4. Unix developed kiosks?

5. Problem with large pings with don't fragment set

6. RH 3.0.3 bootup problem

7. Or how set dont fragment (fragment) + iptables?

8. Sysback/6000 and file order

9. Business Basic Extended and SCO OSR5, or shutdown every night vs. never rebooting.

10. osr5 ftp commands hangs when try to connect with another osr5

11. OSR5.0.0 ==> OSR5.0.4 UIP Errors

12. Upgrade 3.2.4.2 ->OSR5 Host -> OSR5 Ent

13. reboot error reboot error reboot error