On Thu, Mar 03, 2011 at 10:29:50AM +0100, Michal Simek wrote: > J. Bruce Fields wrote: > >You may also want to take a look at it yourself in wireshark. Probably > >you'll see the BADCRED error in one of the replies once you manage to > >capture the right stuff. > > I have looked at it and I see two things. > 1. TCP checksum is incorrect but BE has the same behavior that's why I think it is fine. > 2. Packet #9 (V2 UNSET Reply (Call In 8)) contains Reply state: denied and AUTH_ERROR > bad credential (seal broken) that's the confirmation what I saw from the kernel debug logs. > > What does it caused this rejection? > > I am looking for it in the kernel. The packets sent by the kernel look OK to me on a quick glance, so I'm inclined to suspect that portmap is misparsing them somehow. You probably want to figure out why exactly portmap is deciding to reject the first UNSET call. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
