NFS mount for reading and writing by a regular user. NFC technology in smartphones and its practical use Nfs windows protocol

lTPNE RPDDETTSLY NOPZYI RTPYUYI FIRPCH ZHBKMPCCHCHI UYUFEN, PE FreeBSD CHUFPEOB RPDDETTSLB UEFECHPK ZHBKMPCHPK UYUFENSH (Network File System), YACHUFOPK LBL NFS. NFS RPCHPMSEF UYUFENE YURPMSH'PCHBFSH LBFBMPZY Y ZHBKMSCH UPCHNEUFOP U DTHZYNY NBYYOBNY, RPUTEDUFCHPN UEFY. rPUTEDUFCHPN NFS RPMSH'PCHBFEMY Y RTPZTBNSCH NPZHF RPMKHYUBFSH DPUFHR L JBKMBN ABOUT HDBMЈOSCHI UYUFENBI FPYUOP FBL TSE, LBL EUMY VSCHM BISCHBV

chPF OELPFPTSCHE Y OBYVPMEE BNEFOSHI RTEINHEUFCH, LPFPTSCHE DBЈF YURPMSH'PCHBOYE NFS:

pFDEMShOP CHSFSCHE TBVPYUYE UFBOGYY YURPMSHHAF Neosho UPVUFCHEOOPZP DYULPCHPZP RTPUFTBOUFCHB, FBL LBL UPCHNEUFOP YURPMSHHENSCHE DBOOSCHE NPZHF ITBOYFSHUS ON PDOPK PFDEMSHOPK NBYYOE J VSCHFSH DPUFHROSCHNY LCA DTHZYI NBYYO B UEFY.

rPMSh'PCHBFEMSN OE OKHTSOP YNEFSH DPNBYOYE LBFBMPZY, PFDEMSHOSHE DMS LBTSDPK NBYYOSCH CH CHBYEK UEFY. DPNBYOYE LBFBMPZY NPZHF TBURPMBZBFSHUS ABOUT THE NFS FOLLOWING YI SPTSOP UDEMBFSH DPUFKHROSCHNY PFPCHUADH CH UEFY.

hUFTKUFCHB ITBOEOYS YOZHPTNBGY, FBLYE, LBL DYULEFSCH, RTYCHPDSCH CD-ROM Y HUFTKUFCHB Zip (R), NPZHF YURPMSHUPCHBFSHUS DTHZYBNY NBYYEOEO ьФП NPTSEF RTYCHEUFY L HNEOSHYEOOYA RETEOPUYNSHI HUFTKUFCH ITBOEOYS YOZHPTNBGY CH UEFY.

chPF OEULPMSHLP RTEINETOSHI UTPL YJ ZhBKMB / etc / exports:

h UMEDKHAEYI RTYNETBI DBЈFUS PVEBS YDES FPZP, LBL LURPTFYTPCHBFSH ZHBKMPCHCHE UYUFENSCH, IPFS LPOLTEFOSCHE RBTBNEFTSCH NPZHF PFMYYUBFUBFSHUJU CHUZHU l RTYNETH, YUFPVSCH LURPTFYTPCHBFSH LBFBMPZ / cdrom LCA FTЈI NBYYO, OBIPDSEYIUS H FPN CE UBNPN DPNEOE, YUFP UETCHET Q (YNS RPFPNH PFUHFUFCHHEF DPNEOOPE LCA LBTSDPK NBYYOSCH) YMY LCA LPFPTSCHI YNEAFUS BRYUY H ZHBKME / etc / hosts. ЖМБЗ -ro ХЛБЪЩЧБЕФ ABOUT YURPMSHUPCHBOYE LURPTFYTKHENPK ZHBKMPCHPK UYUFENSCH CH TETSYNE FPMSHLP UFEOIS. u FYN ZhMBZPN HDBMЈOOBS UYUFENB OE UNPTSEF OILPINE PVTBPN YONEOIFSH YLURPTFYTKHENKHA ZHBKMPCHHA UYUFENH.

/ cdrom -ro host1 host2 host3

h UMEDHAEEK UVTPLE LLURPTFYTKHEFUS ZHBKMPCHBS UYUFENB / home, LPFPTBS UVBOPCHYFUS DPUFKHROPK FTEN IPUFBN, KHLBBOOSCHN RP YI IP-BDTEUBN. ьFP RPMEHOP, EUMY X CHBU EUFSH UPVUFCHEOOBS UEFSH WEB OBUFTFEOOOPZP UETCHETB DNS. lBL CHBTYBOF, ZhBKM / etc / hosts NPTSEF UPDETTSBFSH CHOHFTEOOOYE YNEOB IPUFPCH; RPCBMKHKUFB, PVTBFYFEUSH L URTBCHPYUOHA UYUFENKH RP DMS RPMHYUEOYS DPRPMOYFESHOPK YOZHPTNBGY. ЖМБЗ -alldirs RPCHPMSEF TBUUNBFTYCHBFSH RPDLBFBMPZY CH LBYUEUFCHE FPYUEL NPOFYTPCHBOYS. dTHZYNY UMPCHBNY, LFP OE NPOFYTPCHBOYE RPDLBFBMPZPCH, OP TBTEYEOYE LMYEOFBN NPOFYTPCHBFSH FPMSHLP LBFBMPZY, LPFPTSCHAFU YN FTEVM.

/ home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4

h UVTPLE, RTYCHEDЈOOPK OYCE, JBKMPCHBS UYUFENB / a LURPTFYTKHEFUS FBLINE PVTBPN, UFP POB DPUFHROB DCHN LMYEOFBN YY DTHPCHY DPNEOPHYI. RBTBNEFT -maproot \u003d root RPJCHPMSEF RPMSh'PCHBFEMA root HDBMЈOOPK UYUFENSCH PUHEEUFCHMSFSH ABRYUSH ABOUT LURPTFYTKHENKHA ZhBKMPCHHA UYUFENKHJ LBCH RPB. eUMY RBTBNEFT -maproot \u003d root OE ЪBDBO, FP DBCE EUMY RPMSHUPCHBFEMSH YNEEF RTBCHB DPUFKHRB root ABOUT KDBMЈOPK UYUFENE, ON OE UNPTSEF NPDUCHBCHBFENCHYTPK ZHEPK

/ a -maproot \u003d root host.example.com box.example.org

dMS FPZP, UFPVSch LMYEOF UNPZ PVTBFYFSHUS L LLURPTFYTPCHBOOPK ZhBKMPCHPK UYUFENE, PO DPMTSEO YNEFSH RTBCHB UDEMBFSH ЬFP. rTPCHETSHFE, UFP LMYEOF KhLBBBO Ch CHBYEN ZhBKME / etc / exports.

h ZhBKME / etc / exports LBTSDBS UFTPLB UPDETTSYF YOZHPTNBGYA PV LURPTFYTPCHBOY DMS PFDEMSHOPK ZHBKMPCHPK UYUFENSH DMS PFDEMSHOP CHSFPPZP IPUFF. xDBMЈOSCHK IPUF NPTSEF VSCHFSH БBDBO FPMSHLP PDYO TBJ DMS LBTSDPK ZhBKMPCHPK UYUFENSCH, J NPTSEF YNEFSH FPMSHLP PDOKH БРBRYUSH, YURPMSHCHANPHENKHENKHENBYUK l RTEINETH, RTEDRPMPTSYN, UFP / usr SCHMSEFUS PFDEMSHOPK ZhBKMPCHPK UYUFENPK. uMEDHAEYK / etc / exports VHDEF OELPTTELFEO:

# Invalid when / usr is one file system / usr / src client / usr / ports client

pDOB ZhBKMPCHBS UYUFENB, / usr, YNEEF DCHE UVTPLY, BDBAEYE ЬLURPTFYTPCHBOYE DMS PDOPZP Y FPZP TSE IPUFB, client. rTBCHYMSHOSCHK ZhPTNBF CH FPN UMKHUBE FBLPCH:

/ usr / src / usr / ports client

uCHPKUFCHB PFDEMSHOPK ZhBKMPCHPK UYUFENSCH, LLURPTFYTKHENPK OELPFPTPNKH IPUFKH, DPMTSOSCH YBDBCHBFSHUS CH PDOK UVTPLE. uFTPLY VEH KHLBBOYS LMYEOFB CHPUTYOINBAFUS LBL PFDEMSHOSCHK IPUF. ьФП ПЗТБОЙЮЙЧБЕФ ФП, ЛБЛ ЧЩ NPTSEFE LURPTFYTPCHBFSH ZhBKMPCHCHE UYUFENSCH, OP DMS VPMSHYOUFCHB ЬFP OE RTPVMENB.

oYTSE RTICHEDЈO RTYNET RTBCHYMSHOPZP URYULB BLURPTFYTPCHBOYS, ZDE / usr TH / exports SCHMSAFUS MPLBMSHOSCHNY ZhBKMPCHSCHNY UYUFENBNY:

# ьLURPTFYTKHEN src ports DMS client01 client02, OP # FPMShLP client01 NEEF RTBCHB RPMShЪPCHBFEMS root ABOUT OYI / usr / src / usr / ports -maproot \u003d root client01 / usr / src / usr / NPOFAYTPCHBFSH CHUЈ CH # LBFBMPZE / exports. LFP HZPDOP NPTSEF NPOFYTPCHBFSH / exports / obj CH TETSINE UFEOIS / exports -alldirs -maproot \u003d root client01 client02 / exports / obj -ro

dBENPO mountd DPMTSEO VSCHFSH RTPYOZHPTNYTPCHBO PV YUNEOOOY ZHBKMB / etc / exports, YUFPVSH YUNNEOOYS CHUFKHRIMY CH UIMH. ьFP NPTSEF VSCHFSH DPUFYZOHFP RPUCHMLPK UYZOBMB HUP RTPGEUUH mountd:

YMY CHCHCHUPCHPN ULTYRFB mountd RPDUYUFENSH U UPPFCHEFUFCHHAEIN RBTBNEFTPN:

ъB RPDTPPVOPK YOZHPTNBGYEK P TBVPFE ULTIRFPH rc.d PVTBEBKFEUSH L tB'DEMљ12.7,\u003e.

lBL CHBTYBOF, RTY RETEBZTHLE FreeBSD CHUЈ OBUFTPYFUS RTBCHYMSHOP. iPFS CHCHRPMOSFSH RETEBZTHALKH CHCHUE OE PVSBFESHOP. hSCHRPMOEOYE UMEDKHAEYI LPNBOD RPMSh'PCHBFEMEN root ABKHUFF CHUЈ, UFP OKHTSOP.

aBOUT NFS FETTING:

aBOUT LMYEOFE NFS:

fERETSH CHUЈ DPMTSOP VSCHFSH ZPFPCHP L TEBMSHOPNKH NPOFAYTPCHBOYA KDBMЈOOPK ZhBKMPCHPK UYUFENSCH. h RTICHPDYNSCHI RTYNETBI UETCHET VHDEF OPUIFSH YNS server, B LMYEOF VHDEF OPUIFSH YNS client. eUMY BL FPMSHLP IPFYFE CHTENEOOP UNPOFYTPCHBFSH HDBMЈOOHA ZHBKMPCHHA UYUFENH, YMY CHUEZP MYYSH RTPFEUFYTPCHBFSH CHBY OBUFTPKLY, OP RTPUFP BRHUFYFE LPNBODSCH, RPDPVOSCHE RTYCHPDYNSCHN DEUSH, TBVPFBS LBL RPMSHPCHBFEMSH root ON LMYEOFULPK NBYYOE:

rp LFPK LPNBODE ZhBKMPCHBS UYUFENB / home ABOUT THE VHDEF UNPOFYTPCHBOB CHARGE LBFBMPZ / mnt ABOUT LMYEOF. eUMY CHUЈ OBUFPTPEOP RTBCHYMSHOP, CHSCH UNPTSEPHE CHPKFY CH LBFBMPZ / mnt ABOUT LMYEOFY HCHYDEFSH ZHBKMSCH, OBIPDSEYEUS ABOUT THE UCHETTE.

eUMY CHSCH IPFYFE BCHFPNBFYUEEULY NPOFYTPCHBFSH HDBMЈOOHA ZHBKMPCHHA UYUFENH RTY LBTSDPK ABZTHHLE LPNRSHAFETB, DPVBCHSHFE CHBKMUPCHHA etc. ppf rtynet:

Server: / home / mnt nfs rw 0 0

aBOUT UFTBOYGBI URTBCHPYUOPK UYUFENSH RP PETEYUMEOSCH CHUE DPUFKHROSCHE RBTBNEFTSCH.

25.3.4. rTBLFYUEEULPE YURPMSHSPCHBOYE

x NFS EUFSH NOPZP CHBTYBOFPCH RTBLFYUEEULPZP RTEOEOOYS. OYTSE RTYCHPDYFUS OEULPMSHLP OBYVPME YYTPLP TBURTPUFTBOЈOOSHI URPUPVPCH EЈ YURPMSHUPCHBOYS:

oBUFTKLB OEULPMSHLP NBYYO DMS UPCHNEUFOPZP YURPMSHUPCHBOYS CDROM YMY DTHZYI OPUIFEMEK. ьFP VPME DEYЈCHSCHK Y YBYUBUFHA VPME KHDPVOSCHK URPUPV HUFBOPCHLY RTPZTBNOPZP PVEUREUEOIS ABOUT OEULPMSHLP NBYO.

h VPMSHYYI UEFSI NPTSEF PLBBFSHUS VPMEE HDPVOSCHN OBUFTPIFSH GEOFTBMSHOSCHK UETCHET NFS, ABOUT LPFPTPN TBNEEBAFUS CHUE DPNBYOYE RBFBMSHMPZY. FY DPNBYOYE LBFBMPZY NPZHF BFEN LURPTFYTPCHBFSHUS UEFSH B FBL, YUFP RPMSHPCHBFEMY CHUEZDB VHDHF YNEFSH PDYO J FPF CE DPNBYOYK LBFBMPZ Choi BCHYUYNPUFY PF FPZP, ON LBLPK TBVPYUEK UFBOGYY Sing TBVPFBAF.

oEULPMSHLP NBYYO NPZHF YNEFSH PVEIK LBFBMPZ / usr / ports / distfiles. fBLYN PVTBYPN, LPZDB CHBN OKHTSOP VKHDEF HUFBOPCHYFSH RPTF ABOUT OEULPMSHLP NBYO, CHSCH UNPTSEFE VSCHUFTP RPMKHYUYFSH DPUFHR L YUIFKHYUPBYBYBYBYBYBYPK L

25.3.5. bCHFPNBFYUEEULPE NPOFYTPCHBOYE U amd

fELUF RTEDPUFFBCHIM Wylie stilwell.

fELUF RETERYUBM Chern lee.

(DBENPO BCHFPNBFYUEULPZP NPOFYTPCHBOYS) BCHFPNBFYUEULY NPOFYTKHEF HDBMЈOOHA JBKMPCHHA UYUFENH, LBL FPMSHLP RTPYUIPEZOFYBMEK LHPKH lTPNE FPZP, ZHBKMPCHCHE UYUFENSCH, LPFPTSCHE VSCHMY OEBLFYCHOSH OELPFPTPE CHTENS, VHDHF BCHFPNBFYUEULY TBNPOFYTPCHBOSCH DBENPOPN amd. yURPMSHUPCHBOYE amd SCHMSEFUS RTPUFPK BMSHFETOBFYCHPK UFBFYUEULPNKH NPOFYTPCHBOYA, FBL LBL CH RPUMEDOEN UMHYUBE PVSCHUOP CHUЈ DPMTSOP VSPUFSPK / fBUst etc

amd TBVPFBEF, UBN CHSCHUFHRBS LBL UETCHET NFS DMS LBFBMPZPCH / host J / net. lPZDB RTPYUIPDIF PVTBEEOOYE L ZHBKMH CH PDOPN Y'FYI LBFBMPZPCH, amd YEF UPPFCHEFUFCHHAEIK HDBMEOOSCHK TEUHTU DMS NPOFYTPCHBOYFYUPEUHTU / net YURPMSh'KHEFUS DMS NPOFYTPCHBOYS ЛУLURPTFYTKHENPK ZhBKMPCHPK UYUFENSCH RP BDTEUKH IP, LPZDB LBL LBFBMPZ / host YURPMSh KHEFUS YURPMSh KHEFUS IMS NPOFYTPCHBOYS.

pVTBEEOYE L ZHBKMH CH LBFBMPZE / host / foobar / usr ХЛБЦЕФ amd ABOUT CHCHRPMOEYE RPRSCHFLY NPOFYTPCHBOYS TEUKHTUB / usr, LPFPTSCHK OBIPDYFUS ABOUT IPUFE.

rTINET 25.2. nPOFYTPCHBOYE TEUKHTUB RTY RPNPEY amd

chSCH NPTSEFE RPUNPFTEFSH DPUFKHROSCHE DMS NPOFYTPCHBOYS TEUKHTUSCH PFDBMЈOOOPZP IPUFB LPNBODPK showmount. l RTEINETKH, YUFPVSH RPUNPFTEFSH TEUKHTUCH IPUFB U YNEOEN foobar, CHSCH NPTSEFE YURPMSHSPCHBFSH:

lBL CHYDOP YJ RTYNETB, showmount RPLBSCHCHBEF / usr LBL BLURPTFYTKHENSCHK TEUHTU. rTY RETEIPDE CH LBFBMPZ / host / foobar / usr DBENPO amd RSCHFBEFUS TBBTEYIFSH YNS IPUFB foobar J BCFPNBFYUEULY UNPOFYTPCHBFSH FTEVKHENSCHK TEUKHTU.

amd NPTSEF VSCHFSH ЪBRKHEEO Y У ULTIRFPCH OBYUBMSHOPK БBZTKHLJ, EUMY RPNEUFIFSH FBLHA UVTPLKH CH ZHBKM /etc/rc.conf:

Amd_enable \u003d "YES"

lTPNE FPZP, DBENPOKH amd NPZHF VSHFSH RETEDBOSCH OBUFTPEUOSCHE ZhMBZY YUETE RBTBNEFT amd_flags. rP HNPMYUBOYA amd_flags OBUFTFEO UMEDHAEIN PVTBPN:

Amd_flags \u003d "- a /.amd_mnt -l syslog / host /etc/amd.map / net /etc/amd.map"

жБКМ /etc/amd.map ABDBEF PRGYY, YURPMSHHENSCHE RP KHNPMYUBOYA RTY NPOFYTPCHBOY ILURPTFYTKHENSHI TEUKHTUPCH. h ZHBKME /etc/amd.conf BDBOSCH OBUFTPKLY OELPFPTSCHI VPME UMPTSOSHI CHP'NPTSOPUFEK amd.

pVTBFYFEUSH L URTBCHPYUOSCHN UVTBOYGBN RP Y DMS RPMHYUEOIS VPMEE RPMOPK YOZHPTNBGY.

25.3.6. rTPVMENSCH CHBYNPDEKUFCHYS U DTHZYNY UYUFENBNY

fELUF RTEDPUFFBCHIM John lind.

oELPFPTSCHE UEFECHCHE BDBRFETSCH DMS UYUFEN PC U YYOPK ISA YNEAF PZTBOYUEOYS, LPFPTSCHE NPZHF RTYCHEUFY L UETSHEOSCHN RTPVMENBN CH UEFY, CH NUFOPUFY. FY RTPVMENSCH OUREGYUZHYUOSCH DMS FreeBSD, PDOBLP LFH UYUFENH POI JBFTBZYCHBAF.

rTPVMENB, LPFPTBS CHUOILBEF RTBLFYUEULY RTBLFYUEULY CHUEZDB RTJ TBVPFE RP UEFY UYUFEN PC (FreeBSD) U CHUPLPRTPYYCHPDIFESHOSHCHNY TBBWGUYUNEYN Graphics Th Sun Microsystems, Inc. nPOFYTPChBOYE RP RTPFPLPMH NFS VHDEF TBVPFBFSH OPTNBMSHOP, J OELPFPTSCHE PRETBGYY FBLTSE VHDHF CHSCHRPMOSFSHUS HUREYOP, OP OEPTSYDBOOP UETCHET PLBTSEFUS OEDPUFHROSCHN LCA LMYEOF, IPMF BRTPUSCH L J PF DTHZYI UYUFEN VHDHF RTPDPMTSBFSHUS PVTBVBFSCHCHBFSHUS. fBLPE CHUFTEYUBEFUS U LMYEOFULYNY UYUFENBNY, OE JBCHYUYNP PF FPZP, SCHMSEFUS MY LMYEOF NBYYOPK U FreeBSD YMJ TBVPYUEK UVBOGJEK. private enterprise NOPZYI UYUFENBI RTY CHOOYLOPCHEOYY FPC RTPVMENSCH OEF URUPPVB LPTTELFOP ABCHETYYFSH TBVPFH LMYEOFB. EDYOUFCHOOSCHN CHCHIPDPN YBYUBUFKHA SCHMSEFUS IPMPDOBS PETEBZTKHLB LMYEOFB, RPFPNKH UIFP UIFKHBGYS U NFS OE SPCEF VSHFSH TBBTEYEOB.

iPFS RTBCHYMSHOSCHN \u003e\u003e TEYEOYEN SCHMSEFUS HUFBOPCHLB RPMEE RTPYCHPDYFESHOPZP Y ULPTPUFOPZP UEFECHPZP BDBRFETB ABOUT UYUFENH FreeBSD, RNEEFUEPUCHT eUMY WYUFENB FreeBSD SCHMSEFUS UETCHETPN , HLBTSIFE RBTBNEFT -w \u003d 1024 ABOUT LMYEOF RTY NPOFYTPCHBOY. eUMY WYUFENB FreeBSD SCHMSEFUS LMYEOFFPN , FP UNPOFYTHKFE ZHBKMPCHHA UYUFENKH NFS U RBTBNEFTPN -r \u003d 1024. ьФЙ RBTBNEFTSCH NPZKHF VSHFSH ÄBDBOSCH CH YUEFCHETFPN RPME ABRYUY CH ZHBKME fstab LMYEOFB RTY BCHFPNBFYUEULPN NPOFYTPCHBOYUY, YMY RTY RPBTPNPHBOYT

oHTSOP PFNEFIFSH, UFP YNEEFUS FBLCE DTHZBS RTPVMENB, PYIVPYUOP RTYOINBENBS ЪB RTYCHDEOOKHA CHCHCHYE, LPZDB UETSCHY LMYEPSHBSCHO NFS OBSCHI. eUMY LFP FPF UBNSCHK UMHYUBK, RTPCHETSHFE , UFP CHBY NBTYTHFY'BFPTSCH RTPRKHULBAF OKHTSOKHA YOZHPTNBGYA UDP, CH RTPFYCHOPN UMKHYUBE CHSCH OYUEZP OE RPMKHYUIFE, UFP VSCH CHSCHOY RTEDRTEY.

h UMEDKHAEYI RTYNETBI fastws SCHMSEFUS YNEOEN IPUFB (YOFETZHEKUB) CHSCHUPLPRTPYCHPDIFESHOPK TBVPYUEK UVBOGYY, B freebox SCHMSEFUS UNEOSCH IPUZHEVDB (YOFETZHEKUB) lTPNE FPZP, / sharedfs VHDEF SCHMSFSHUS LURPTFYTHENPK YUETE NFS ZHBKMPCHPK UYUFENPK (L PVTBFYFEUSH UFTBOYGBN URTBCHPYUOPK UYUFENSCH LPNBODE RP), B / project VHDEF FPYULPK NPOFYTPCHBOYS LURPTFYTHENPK ZHBKMPCHPK UYUFENSCH ON LMYEOFE. h MAVPN UMKHYUBE, PFNEFSHFE, UFP DMS CHBYEZP RTEIMPTSEOIS NPZHF RPOBDPVIFSHUS DPRPMOYFESHOSCHE RBTBNEFTSCH, FBLJE, LBL hard, soft YMY bg.

rTYNET UYUFENSCH FreeBSD (freebox) LBL LMYEOFB W ZHBKME / etc / fstab ABOUT NBYOE freebox:

Fastws: / sharedfs / project nfs rw, -r \u003d 1024 0 0

lPNBODB, CHCHDBCHBENBS CHTHYUOHA ABOUT NBYOE freebox:

rTYNET UYUFENSCH FreeBSD H LBYUEFCH UETCHETB H JBKME / etc / fstab ABOUT fastws:

Freebox: / sharedfs / project nfs rw, -w \u003d 1024 0 0

lPNBODB, CHCHDBCHBENBS CHTHYUOHA ABOUT Nbyyo fastws:

rTBLFYUEULY CHUE 16-TBTSHE UEFECHCHE BDBRFETSCH RPJCHPMSF TBVPFBFSH VEH KHLBBOOSHCHYE PZTBOYUEEOIK ABOUT TBNET VMPLPCH RTY YUFEYUYUY Y Ъ.

dMS FEI, LFP JOFETEUKHEFUS, OYCE PRYUSCHBEFUS, UFP TCE RTPYUIPDIF CH RTI RPSCHMEOYY UFPK PYIVLJ, Y PVYASUOSEFUS, RPYUENKH EPTZOOCHPHPUN. lBL RTBCHYMP, NFS TBVPFBEF U VMPLBNY \u003e\u003e TBNETPN 8љLYMPVBKF (IPFS PFDEMSHOSHE ZhTBZNEOFSCH NPZKHF YNEFSH NEOSHY TBNETSH). FBL, RBLEF Ethernet YNEEF NBLUYNBMSHOSCHK TBNET PLPMP 1500љVBKF, OP VMPL \u003e\u003e NFS TBVYCHBEFUS ON OEULPMSHLP RBLEFPCH Ethernet, IPMF ON VPMEE CHSCHUPLPN HTPCHOE FP Chueh FPF CE EDYOSCHK VMPL, LPFPTSCHK DPMTSEO VSCHFSH RTYOSF, UPVTBO TH RPDFCHETTSDEO LBL PDYO VMPL. hSCHUPLPRTPYCHPDIFESHOSHE TBVPYUE UVBOGY NPZHF RPUSCHMBFSH RBLEFSCH, LPFPTSCHE UPPFCHEFUFCHKHAF PDOPNKH VMPLKH NFS, UTBJH DTHZ BVPYUE UVBOGY NPZHF RPUCHMBFSH RBLEFSCH On UMBVSCHI, OYLPRTPYCHPDYFEMSHOSCHI BDBRFETBI RBLEFSCH, RTYYEDYYE RPTSE, OBLMBDSCHCHBAFUS RPCHETI TBOEE RTYYEDYYI RBLEFPCH FPZP CE UBNPZP VMPLB DP FPZP, LBL Sing NPZHF VSCHFSH RETEDBOSCH IPUFH J VMPL LBL EDYOPE gempen OE NPTSEF VSCHFSH UPVTBO YMY RPDFCHETTSDEO. h TEHMSHFBFE TBVPYUBS UFBOGYS CHIPDIF CH UIFKHBGYA FBKN-BKHFB Y RSCHFBEFUS RPChFPTYFSH RETEDBYUH, OP HTSE U RPMOSHN VMPLPN CH 8љLVUCH VMPLPN CH 8љLVUCHU RTPPUCH RTPPUCH

ъBDBCH TBNET VMPLB NEOSHY TBNETB RBLEFB Ethernet, NSCh DPUFIZBEN FPZP, UFP MAVPK RPMOPUFSHA RPMHYUEOSCHK RBLEF Ethernet NPTSEF VSCHFSH RPDFCHETTSDEO YOBDYCH.

oBMPTsEOYE RBLEFPCH NPTSEF Chueh of the ECE RTPSCHMSFSHUS, LPZDB CHSCHUPLPRTPYCHPDYFEMSHOSCHE TBVPYUYE UFBOGYY UVTBUSCHCHBAF DBOOSCHE ON PC-UYUFENH, PDOBLP RPCHFPTEOYE FPK UYFHBGYY OE PVSBFEMSHOP have VPMEE ULPTPUFOSCHNY BDBRFETBNY have VMPLBNY \u003e\u003e NFS. lPZDB RTPYUIPDIF OBMPTSEOYE, BFTPOKHFSCHE VMPLY VHDHF RETEDBOSCH UOPCHB, Y ULPTEE CHUEZP, POI VHDHF RPMHYUEOSCH, UPVTBOSCH YPDFCHETTSDEO.

A long time ago in the early 2000s, many were amused by the fact that they regularly "scan" the networks of their provider, and sometimes more distant targets, in order to detect Windows machines and resources on them (SMB), available for reading (writing). The search process was primitive: a range of IP addresses or a network mask was set, and using various tools - LANguard Network Scanner, xIntruder and the like - addresses were scanned and servers were found. Often, on the discovered machines, various network resources (disks, printers, directories) were available for reading, less often for writing. Through an anonymous session using IPC $ and the “Guest” user, it was possible to enumerate resources on the machine, sometimes there were “Administrators” members without passwords, and sometimes, after more “active” exposure to the discovered machines, it was possible to find servers running Windows NT 4.0 or Windows 2000 Server. If luck deigned to find machines with the then widespread Windows 98, then it became easier - at that time the specified OS contained many different vulnerabilities, including in the implementation of work with SMB, brute force to gain access to the resource was carried out in a matter of minutes, even on dial-up connections. For those who want to plunge into the old days, here it is written in detail about "access" to Windows 9x - Hacking Exposed: Network Security Secrets & Solutions. Chapter 4: Hacking Windows 95/98 and Me. But later in the article we are not talking about that.

I never thought that such "entertainment" would be possible in 2019. The similarity lies in the ease of finding other people's available resources for all the curious. Further, we will not talk about the trend popular in the last 2 years - the search for open-source MongoDB or Elasticsearch databases - but about a slightly more mundane service.

Further, I propose not to evaluate the entire procedure, their ethical standard, I note that this post is not a call to action that can be attributed to some articles of the Criminal Code of the Russian Federation or similar norms from the legislation of other states.

Network File System (NFS)

After visualizing the graph from such "mapping", it becomes clear that this is not the best option: you can see the relation of the server's IP address to the IP addresses and hosts from which access is possible, and the available NFS resources on the server, but after all, different resources can be accessed from different IP. Therefore, we create another schema (for any table, you can create many schemas).

Scheme 2

Better. Everything falls into place - on which server there are resources, and from which IP addresses you can access them:

This option for creating a graph schema template from a table is convenient only when you do not often have to work with your own module, or when you import text files (csv) into an application. The fact is that the "mapping" created in this way is preserved only within the framework of the current investigation. After creating a new "investigation" the module will be saved and will be executed with the resulting table, but the schema will not be saved and it will have to be rebuilt.

To combine the results from the search by Shodan and NFS, you need to open the Shodan search scheme, activate the add to active tab button and put the result of our module on the same tab - the schemes will be combined:

Combined circuits:

The module code for Lampyre is available, there is also the second version of the module without using an ssh connection.

Instead of a conclusion - colleagues, regularly check the correctness of your NFS settings and more.

Today we will figure out how to install and configure the NFS (Network File System) client in Windows Server 2012 R2 / Windows 8. So, to mount a directory (share) in Windows Server 2012 R2 / Win 8, you need, as in previous versions of Windows, install a separate component - NFS client ( Client for NFS). Additionally, to be able to manage NFS connection settings, you can install the NFS Services component ( Services for Network File System).

The NFS client has been included with Microsoft since Windows 7. In Windows 2012/8, the NFS client has received minor changes. Now the NFS client supports authentication using the Krb5p protocol - Kerberos version 5 (in addition to Krb5 and Krb5i, support for which appeared in Windows 7), large NFS packets are supported - up to 1024KB (in Win 7 the maximum packet size is 32KB)

The NFS client can be installed via the GUI or using Powershell. To install in graphical mode, open and select the (Features) component named Client for NFS.

By default, the graphical NFS management console is not installed with this component, to fix this, set the option Services for Network File System Management Tools under Remote Server Administration Tools -\u003e Role Administration Tools -\u003e File Services Tools.

To install an NFS client in Windows 8, you need to activate the component Services for NFS -\u003e Client for NFS, through the installation / removal of components (Turn Windows features on or off) in the Control Panel (Control Panel -\u003e Programs -\u003e Programs and Features).

Note... Unlike Windows 7, in which the NFS client was present in the Enterprise and Ultimate editions, in Windows 8 the Network File System client is supported only in the older version - Windows 8 Enterprise.

All of the above system components can be installed with just one Powershell command:

Install-WindowsFeature NFS-Client, RSAT-NFS-Admin

After finishing the installation, start the console Services for Network File System Managemen and open the NFS client properties window ( Client for NFS).

In the NFS client settings, you can set:

• Transport protocols used - default TCP + UDP
• Mount type NFS ball: hard or soft
• The File Permissions tab specifies the default rights for the created folders and files on NFS shares
• The Security tab specifies the authentication protocols that can be used to authenticate to the NFS server

After configuring the installation, administrators will be able to mount the NFS directory using the mount command:

Mount \\\\ lx01.abc.lab \\ nfs z:

In this example, we have mounted under the letter Z: the NFS directory located on the lx01.abc.lab server.

After mounting, the directory mounted in this way on the NFS server is available in the system as a separate drive with the letter Z: \\.

You can also mount the NFS share using Powershell:

New-PSdrive -PSProvider FileSystem -Name Z -Root \\\\ lx01.abc.lab \\ nfs

Note... The nfs directory connected in this way will be available only within the Powershell session in which the mount command was executed. To permanently mount the NFS directory on the system, at the end of the Powershell command you need to add the key –Persist.

You can unmount a mounted directory like this.

N FS ( Network file system) is mainly designed to be shared files and folders between / Unix systems from by Sun Microsystems in 1980 year... It allows you to mount local file systems over the network and remote hosts to interact with them as if they were installed locally on the same system. Via NFS , we can set up file sharing between Unix in Linux system and Linux for the system Unix.

Benefits of NFS

1. NFS creates local access to remote files.
2. It uses a standard architecture customer/server to exchange files between all machines based on * NIX.
3. Via NFS it is not necessary that both machines run on the same OS.
4. Via NFS we can customize the solution centralized storage.
5. Users get their data regardless of their physical location.
6. Automatic renewal for new files.
7. Newer version NFS supports mounting acl, pseudo as root.
8. Can be protected firewalls and Kerberos.

NFS services

Service System V-launched... Server package NFS includes three tools included in packages portmap and nfs-Utils.

1. portmap: displays calls made from other machines to the correct service RPC (not required with NFSv4).
2. nfs: converts remote requests file sharing into queries on the local file system.
3. rpc.mountd: this service is responsible for mounting and unmounting file systems.

Important configuration files for NFS

1. / etc / exports: its main config file NFS, all exported files and catalogswhich are defined in this file and on destination NFS server.
2. / etc / fstab: To mount nFS directory on your system without reboots, we need to record in / etc / fstab.
3. / etc / sysconfig / nfs: Configuration file NFS to control which port RPC and other services listening.

Configuring and Mounting NFS on a Linux Server

To customize mount NFSwe will need at least two cars Linux/Unix... In this tutorial, we'll be using two servers.

1. NFS server: nfsserver.example.ru with IP - 192.168.0.55
2. NFS client: nfsclient.example.ru with IP - 192.168.0.60

Installing NFS Server and NFS Client

We need to install packages NFS on our nFS serveras well as by car nFS client... We can install it with “” ( Red Hat Linux) and installation package “ apt-get” (Debian and Ubuntu).

# yum install nfs-utils nfs-utils-lib # yum install portmap (not required with NFSv4) # apt-get install nfs-utils nfs-utils-lib

Now run service on both machines.

# /etc/init.d/portmap start # /etc/init.d/nfs start # chkconfig --level 35 portmap on # chkconfig --level 35 nfs on

After installing the packages and starting the services on both machines, we need to configure both machines to share files.

Setting up an NFS server

First, let's set up the server NFS.

Setting up the export directory

# mkdir / nfsshare

Now we need to write to “ / etc / exports”And restart services to make our directory shareable on the web.

# vi / etc / exports / nfsshare 192.168.0.60 (rw, sync, no_root_squash)

In the example above, there is a directory under / entitled " nfsshare", Currently shared with an IP client" 192.168.0.60 ”With privileges reading and records (RW), you can also use hostname client instead of IP in the example above.

NFS options

Some other options we can use in files “ / etc / exports”For file sharing looks like this.

1. ro: With this option we can provide read-only access to shared files, i.e. customer will only be able read.
2. rw: This option allows client to server access for both for reading and records within the shared directory.
3. sync: Synchronization confirms requests to the shared directory only after changes were committed.
4. no_subtree_check: This option prevents checking subtree... When a shared directory is a subdirectory of a larger filesystem, NFS scans every directory above it to check its permissions and details. Disable check subtree can improve reliability NFSbut reduce safety.
5. no_root_squash: This phrase allows root, connect to a specific folder.

For more options with “ / etc / exports“, It is recommended to read pages guidelines for export.

NFS client setup

After setting NFS-server, we need mount this shared directory or partition on client server.

Mounting shared directories on an NFS client

Now on nFS client, we need mount this directory to be accessed locally. To do this, first, we need to find out what resources are available on the remote or NFS server.

# showmount -e 192.168.0.55 Export list for 192.168.0.55: / nfsshare 192.168.0.60

Mounting an accessible directory in NFS

To mount general NFS directory, we can use the following mount command.

# mount -t nfs 192.168.0.55:/nfsshare / mnt / nfsshare

The above command will set the shared directory to “ / mnt / nfsshare”On the client's server. You can check it with the following command.

# mount | grep nfs sunrpc on / var / lib / nfs / rpc_pipefs type rpc_pipefs (rw) nfsd on / proc / fs / nfsd type nfsd (rw) 192.168.0.55:/nfsshare on / mnt type nfs (rw, addr \u003d 192.168.0.55)

The above mount command mounts on NFS shared directory on NFS client temporarily to mount the NFS directory constantly on your system regardless of reboots, we need to make an entry in “ / etc / fstab“.

# vi / etc / fstab

Add the following new line as shown below.

192.168.0.55:/nfsshare / mnt nfs defauls 0 0

Testing the NFS Installation Behavior

We can test our installing an NFS server by creating test file on the server side and check its presence on NFS client side or vice versa.

Server side nfsserver

We have created a new text file named “ nfstest.txt”In this general directory.

# cat\u003e /nfsshare/nfstest.txt This is a test file to test the working of NFS server setup.

Client side nfsclient

Go to the shared directory on client server and you will find the shared file without any manual update or reboot service.

# ll / mnt / nfsshare total 4 -rw-r - r-- 1 root root 61 Sep 21 21:44 nfstest.txt [email protected] ~] # cat /mnt/nfsshare/nfstest.txt This is a test file to test the working of NFS server setup.

Removing an NFS mount

If you want to unmount this shared directory from the server after you are done with file sharing you can simply unmount this particular directory using the command “ umount“. See this example below.

[email protected] ~] # umount / mnt / nfsshare

You can see that the mount has been removed on the filesystem.

# df -h -F nfs

You will see that these shared directories are no longer available.

Important commands for NFS

Some more important commands for NFS .

1. showmount -e : Shows available shared objects on the local computer
2. showmount -e : List of available shared objectson remote server
3. showmount -d : List of all subdirectory
4. exportfs -v : Displays a list of shared files and options on server
5. exportfs -a : Exports all available objects listed in / etc / exports, or name
6. exportfs -u : Re-export of all available objects listed in / etc / exports, or name
7. exportfs -r : Refresh server list after change / etc / exports

It's all about mount NFS at the moment, if interested, you can read the guide about that. Leave your

When it comes to computer networks, you can often hear the mention of NFS. What does this acronym mean?

It is a distributed file system protocol, originally developed by Sun Microsystems in 1984, that allows a user on a client computer to access files over a network, similar to accessing local storage. NFS, like many other protocols, is based on the Open Network Computing Remote Procedure Call (ONC RPC) system.

In other words, what is NFS? It is an open standard, defined in the Request for Comments (RFC), that allows anyone to implement the protocol.

Versions and variations

The inventor used only the first version for his own experimental purposes. When the development team added significant changes to the original NFS and released it outside of Sun's ownership, they labeled the new version as v2 so that interoperability between distributions could be tested and a fallback could be made.

NFS v2

Version 2 originally only worked over User Datagram Protocol (UDP). Its developers wanted to keep the server side without blocking outside the main protocol.

The virtual file system interface allows for modular implementation reflected in a simple protocol. By February 1986, solutions were demonstrated for operating systems such as System V release 2, DOS, and VAX / VMS using Eunice. NFS v2 only allowed the first 2 GB of a file to be read due to 32-bit limitations.

NFS v3

The first proposal to develop NFS version 3 at Sun Microsystems was announced shortly after the release of the second distribution. The main motivation was to try to mitigate the problem of synchronous write performance. By July 1992, practical improvements had resolved many of the shortcomings of NFS version 2, while leaving only insufficient file support (64-bit file sizes and offsets).

• support for 64-bit file sizes and offsets for processing data larger than 2 gigabytes (GB);
• support for asynchronous recording on the server to improve performance;
• additional file attributes in many answers to avoid having to retrieve them again;
• rEADDIRPLUS operation to get data and attributes along with filenames when scanning a directory;
• many other improvements.

During the introduction of version 3, support for TCP as a transport layer protocol began to increase. The use of TCP as a means of transferring data, performed using NFS over the WAN, began to allow large file sizes to be transferred for viewing and writing. Thanks to this, developers were able to overcome the 8K limit imposed by the User Datagram Protocol (UDP).

What is NFS v4?

Version 4, influenced by the Andrew File System (AFS) and Server Message Block (SMB, also called CIFS), includes performance improvements, better security, and a conditional protocol.

Version 4 was the first distribution developed by the Internet Engineering Task Force (IETF) after Sun Microsystems outsourced protocol development.

NFS version 4.1 aims to provide protocol support for using clustered server deployments, including the ability to provide scalable concurrent file access across multiple servers (pNFS extension).

The newest file system protocol, NFS 4.2 (RFC 7862), was officially released in November 2016.

Other extensions

With the development of the standard, appropriate tools have appeared for working with it. For example, WebNFS, an extension for versions 2 and 3, allows the network file system access protocol to more easily integrate into web browsers and enable firewalls.

Various third party protocols have also become associated with NFS. The most famous of them are:

• Network Lock Manager (NLM) with byte protocol support (added to support UNIX System V file locking API);
• remote quota (RQUOTAD), which allows NFS users to view storage quotas on NFS servers;
• NFS over RDMA - an adaptation of NFS that uses remote direct memory access (RDMA) as the transmission medium;
• NFS-Ganesha is a user-space NFS server that supports CephFS FSAL (File System Abstraction Layer) using libcephfs.

Platforms

The Network File System is often used with Unix operating systems (such as Solaris, AIX, HP-UX), Apple's macOS, and Unix-like operating systems (such as Linux and FreeBSD).

It is also available for platforms such as Acorn RISC OS, OpenVMS, MS-DOS, Microsoft Windows, Novell NetWare, and IBM AS / 400.

Alternative remote file access protocols include Server Message Block (SMB, also called CIFS), Apple Transfer Protocol (AFP), NetWare Core Protocol (NCP), and OS / 400 Server File System (QFileSvr.400).

This is due to the requirements of NFS, which are focused mostly on Unix-like "shells".

At the same time, SMB and NetWare (NCP) protocols are used more often than NFS on systems running Microsoft Windows. AFP is most widely used on Apple Macintosh platforms, and QFileSvr.400 is most commonly found on OS / 400.

Typical implementation

Assuming a typical Unix-style scenario where one machine (client) needs access to data stored on another (NFS server):

• The server implements Network File System processes, running as nfsd by default, to make its data publicly available to clients. The server administrator determines how to export directory names and options, usually using the / etc / exports configuration file and the exportfs command.
• Server security administration ensures that it can recognize and approve a verified client. Its network configuration ensures that the appropriate clients can negotiate with it through any firewall system.
• The client machine requests access to the exported data, usually by issuing the appropriate command. It queries the server (rpcbind) that is using the NFS port and subsequently connects to it.
• If all goes well, users on the client machine will be able to view and interact with the installed file systems on the server within the allowed options.

It should be noted that the automation of the Network File System process can also take place - perhaps using etc / fstab and / or other similar means.

Development to date

By the 21st century, rival protocols DFS and AFS have not achieved any major commercial success over the Network File System. IBM, which previously acquired all of the commercial rights to the above technologies, donated most of the AFS source code to the free software community in 2000. The Open AFS project still exists today. In early 2005, IBM announced the completion of AFS and DFS sales.

In turn, in January 2010, Panasas introduced NFS v 4.1, a technology that improves concurrent data access capabilities. The Network File System v 4.1 protocol defines a method for separating file system metadata from the location of specific files. So it goes beyond simple name / data separation.

What is NFS of this version in practice? The above feature distinguishes it from the traditional protocol, which contains the names of files and their data under the same binding to the server. With Network File System v 4.1, some files can be distributed across multisite servers, but client participation in separating metadata and data is limited.

In the implementation of the fourth distribution kit of the NFS protocol, the server is a set of server resources or components; they are assumed to be controlled by a metadata server.

The client still contacts the same MDS server to crawl or interact with the namespace. When it moves files to and from the server, it can directly interact with the dataset belonging to the NFS group.