nfs client to use a designated source ip address
Iyer, Rahul
Rahul.Iyer at netapp.com
Mon Oct 9 22:17:36 EDT 2006
How about trying a packet trace... That might help.
Regards
Rahul
> -----Original Message-----
> From: Roopa Prabhu [mailto:roopa.prabhu at gmail.com]
> Sent: Monday, October 09, 2006 4:55 PM
> To: Iyer, Rahul
> Cc: nfsv4 at linux-nfs.org
> Subject: Re: nfs client to use a designated source ip address
>
> yes it does :
>
> / 1.3.14.5(ro,sync,no_root_squash)
>
> Thanks,
> Roopa
>
>
>
> On 10/9/06, Iyer, Rahul < Rahul.Iyer at netapp.com
> <mailto:Rahul.Iyer at netapp.com> > wrote:
>
> Does 1.3.14.5 have permissions in the /etc/exports file?
> Regards
> Rahul
>
>
> > -----Original Message-----
> > From: Roopa Prabhu [mailto:roopa.prabhu at gmail.com]
> > Sent: Monday, October 09, 2006 4:23 PM
> > To: Iyer, Rahul
> > Cc: nfsv4 at linux-nfs.org
> > Subject: Re: nfs client to use a designated source ip address
> >
> > Am sorry if I wasnt clear. I did use the client's own aliased
> > ipaddress to mount. I mentioned the server in my mail just
> > cause I wanted to let you know that I had my client's
> > ipaddress in the server's /etc/exportfs.
> >
> > Below is a log of steps that I am trying.
> >
> > Thanks,
> > Roopa
> >
> > [root at test-14 tmp]# ifconfig
> > eth0 Link encap:Ethernet HWaddr 00:13:21:0C:66:C9
> > inet addr:192.188.1.141 Bcast:192.188.1.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:2389736 errors:0 dropped:0
> overruns:0 frame:0
> > TX packets:1679714 errors:0 dropped:0
> overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:2059301699 (1963.9 Mb) TX bytes:983176655
> > (937.6 Mb)
> > Interrupt:25
> >
> > eth0:0 Link encap:Ethernet HWaddr 00:13:21:0C:66:C9
> > inet addr:1.3.14.5 Bcast:1.3.14.255 Mask:
> 255.255.255.0 <http://255.255.255.0>
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0
> carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > Interrupt:25
> >
> > [root at test-14 tmp]# ping -I 1.3.14.5 192.188.1.130
> <http://192.188.1.130> PING
> > 192.188.1.130 <http://192.188.1.130> (192.188.1.130) from
> > 1.3.14.5 <http://1.3.14.5> : 56(84) bytes of data.
> > 64 bytes from 192.188.1.130: icmp_seq=0 ttl=61 time= 0.179 ms
> > 64 bytes from 192.188.1.130: icmp_seq=1 ttl=61 time= 0.155 ms
> >
> > [root at test-14 tmp]# showmount -e 192.188.1.130 Export list
> > for 192.188.1.130 <http://192.188.1.130 > :
> > / 1.3.14.5
> >
> >
> > [root at test-14 tmp]# mount -t nfs -o addr=1.3.14.5
> > 192.188.1.130:/ /mnt
> > mount: 192.188.1.130:/ failed, reason given by server:
> > Permission denied
> >
> >
> >
> > On 10/9/06, Iyer, Rahul <Rahul.Iyer at netapp.com> wrote:
> >
> > Hi!
> > I think we have a misunderstanding... The addr option
> > is used by the
> > client to provide its (the client's own) IP address to
> > the server, not
> > to specify the server ip address the client mounts.
> > Regards
> > Rahul
> >
> >
> > > -----Original Message-----
> > > From: Roopa Prabhu [mailto:roopa.prabhu at gmail.com]
> > > Sent: Monday, October 09, 2006 3:38 PM
> > > To: Iyer, Rahul
> > > Cc: nfsv4 at linux-nfs.org
> > > Subject: Re: nfs client to use a designated
> source ip address
> > >
> > > Hello Rahul,
> > >
> > > Appreciate your quick response.
> > > However, I tried to use the addr option and
> it does not work
> > > for me for some reason.
> > > I get permission denied from the server. My
> client mount goes
> > > through fine if I export eth0 address on the
> server and it
> > > fails if I export eth0:0 address on the
> server and try to
> > > mount using 'mount -o addr=<eth0:0 address>.
> > >
> > > I checked all my settings. And it does look fine.
> > > Any hints on to what might be wrong ?
> > >
> > > Thanks again,
> > > Roopa
> > >
> > >
> > >
> > >
> > > On 10/9/06, Iyer, Rahul <
> Rahul.Iyer at netapp.com <mailto:Rahul.Iyer at netapp.com> > wrote:
> > >
> > > Hi,
> > > You could use the addr=<ip addr> option
> to mount for
> > > this. However, the
> > > Linux man page seems to say that it ignores it.
> > > However, I do believe,
> > > in v4, the address specified via the
> addr option is the
> > > address the
> > > server uses to make callbacks to the client.
> > > Regards
> > > Rahul
> > >
> > >
> > > > -----Original Message-----
> > > > From: Roopa Prabhu [mailto:
> roopa.prabhu at gmail.com <mailto:roopa.prabhu at gmail.com> ]
> > > > Sent: Monday, October 09, 2006 1:35 PM
> > > > To: nfsv4 at linux-nfs.org
> > > > Subject: nfs client to use a designated
> > source ip address
> > > >
> > > > I have an aliased interface on my first
> > ethernet interface.
> > > > And I would like my nfs client (mount -t nfs)
> > to use the ip
> > > > address on this aliased interface as the
> > source address for
> > > > all nfs mounts. I tried to look through the
> > archives to see
> > > > if I can find an answer.
> > > > Can anybody please let me know what
> is the best way
> > > to do this ?.
> > > >
> > > > Thanks,
> > > > Roopa
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
More information about the NFSv4
mailing list