Re: Netbooting odyssey (SGI Indy)
>> First, bootpd answered with packets that had DF (don't fragment) bit
>> set. Turning PMTU off in /proc did not seem to help for some reason(???).
TS>
TS> It most likely did, the DF bit itself doesn't matter (and remains
TS> set for me as well).
I did some more testing. I was partly wrong.
/proc/sys/net/ipv4/ip_no_pmtu_disc only works for new sockets created.
Since bootpd runs from inetd I have to restart inetd for the change to
take effect.
As long as DF is set on the bootp answer, my Indy seems to ignore it.
Drop DF and everything is OK. Same for TFTP answers. My only mistake was
not restarting inetd - when inetd is restarted,
/proc/sys/net/ipv4/ip_no_pmtu_disc = 1 is working fine and no setsockopt
is necessary.
Indy PROM version is 5.1.2 Rev B4.
>> Also, to get any answer back to my Indy at all, I needed to use a
>> crossover cable to the boot server (with Intel NIC using e100 driver but
>> that's probably unimportant) because my Trendnet TE100-S55E 5-port
>> 10/100 switch and Indy don't communicate (Indy doesn't seem to get any
>> answers, at least in PROM mode).
TS>
TS> Sounds like this was the root of the problem.
Nope, this was the first thing I changed (to crossover). In the end I
tested the working conf again with switch and it broke again. But all my
other testing was done using crossover. This time I tested on realtek
8139 nic and it worked too, as expected.
--
Meelis Roos (mroos@linux.ee)
Reply to: