cpj@CITI.UMICH.EDU (Charles Jerian) (03/23/88)
The brl ping only records 6 routes and the documentation says that only 6 will fit into the ip header, however the one I wrote last year has 9 routes brl's gives ./ping -R umda.umd.edu PING umda.umd.edu (128.8.10.10): 56 data bytes 64 bytes from 128.8.10.10: icmp_seq=1 time=1880 ms citi->cntr (35.1.17.2) cntr.pgw (35.1.1.12) umich->cleveland (128.182.18.2) cleveland->psc (128.182.16.2) psc->sura (128.167.31.2) sura->umdbogon (128.167.1.3) while mine gives /etc/ping -r umda.umd.edu options 7==7(RR) 39 40 citi->cntr cntr.pgw umich->cleveland cleveland->psc psc->sura sura->umdbogon 129.2.1.5 bogon-gw.umd.edu terp.umd.edu umda.umd.edu is alive
phil@BRL.ARPA (Phil Dykstra) (03/23/88)
You are correct in that up to 9 routes can fit in an IP header if record route is the only option. I'm not sure how ours ended up set to six (the documentation just laments the max IP header size). You can simply change the "#define NROUTES" from 6 to 9. I have done so to VGR's copy. - Phil