mount ko sans ajouter l'option proto=tcp

[adn]

Bonjour,

J'ai un serveur NFS et un client sur lequel j'essaye de mounter un dossier sans succès si je ne mets pas l'option "proto=tcp". Si je stoppe iptables, le mount marche sans l'ajout de cette option. Le problème semble venir de firewall, son contenu avec iptables -vL (partie INPUT)

pkts bytes target prot opt in out source destination

48 6610 ACCEPT all -- lo any anywhere anywhere

0 0 ACCEPT icmp -- any any anywhere anywhere icmp any

0 0 ACCEPT esp -- any any anywhere anywhere

0 0 ACCEPT ah -- any any anywhere anywhere

0 0 ACCEPT udp -- any any anywhere 224.0.0.251 udp dpt:mdns

0 0 ACCEPT udp -- any any anywhere anywhere udp dpt:ipp

0 0 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ipp

881 3993K ACCEPT all -- any any anywhere anywhere state RELATED,ESTABLISHED

0 0 ACCEPT udp -- any any anywhere anywhere state NEW udp dpt:892

0 0 ACCEPT udp -- any any anywhere anywhere state NEW udp dpt:nfs

11 660 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:nfs

12 720 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:sunrpc

0 0 ACCEPT udp -- any any anywhere anywhere state NEW udp dpt:pftp

0 0 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:pftp

10 600 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:892

0 0 ACCEPT udp -- any any anywhere anywhere state NEW udp dpt:filenet-rpc

0 0 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:32803

0 0 ACCEPT udp -- any any anywhere anywhere state NEW udp dpt:875

0 0 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:875

0 0 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:webcache

0 0 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:ssh

6 992 REJECT all -- any any anywhere anywhere reject-with icmp-host-prohibited

Une idée du problème ?

[adn]

Résolu... il fallait que j'ouvre aussi portmap sur le protocole udp, pour ceux que çà intéresse