was under the impression that all comms from client > media uses vnetd 13724 when being utilised .
It's the whole point of it I think. Regards Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 25 August 2006 11:40 To: Dave Lowenstein; veritas-bu@mailman.eng.auburn.edu Cc: [EMAIL PROTECTED] Subject: Re: [Veritas-bu] vnetd question Hello Dave You will need to open for 13724 (data port) media to client if you want to do restores. But looks like the client isn't using vnetd Regards Michael On Thu, 24 Aug 2006 15:58:08 -0700, Dave Lowenstein wrote > I'm trying to make sure that netbackup 5.1 will work through a > firewall with minimal ports being opened. > > What ports need to be open on the firewall if filtering by destination > port: > > Media >> Client > 13782 (bpcd) > > Client >> Media > 13724 (vnetd) > > If the client needs to run user backups/restores, then the following > port will also need to be opened: > Client >> Master > 13720 (bprd) > > Right? So I'm testing this out between two hosts with some more > liberal firewall rules than above. Backups are working fine, restores > are working fine. > > I believe I have all the vnetd stuff set correctly, although every > piece of documentation I find shows a slightly different gui interface > than what I'm seeing. > > Why am I still seeing it talking back and forth between media server > and client with randomly selected destination ports (like 852 and > 811)? There's also a fair amount of icmp going on back and forth > between the two, which I'd like to be able to close down. > > client -> server TCP D=13724 S=852 Ack=392120625 > Seq=931198138 Len=0 Win=49680 client -> server TCP D=13724 > S=852 Push Ack=392120625 Seq=931198138 Len=2 Win=49680 server - > > client TCP D=852 S=13724 Ack=931198140 Seq=392120625 > Len=0 Win=33118 server -> client TCP D=852 S=13724 > Push Ack=931198140 Seq=392120625 Len=2 Win=33120 client -> > server TCP D=13724 S=852 Ack=392120627 Seq=931198140 Len=0 Win=49680 > client -> server TCP D=13724 S=852 Push > Ack=392120627 Seq=931198140 Len=2 Win=49680 server -> client > TCP D=852 S=13724 Ack=931198142 Seq=392120627 Len=0 Win=33120 > client -> server TCP D=13724 S=852 Push Ack=392120627 > Seq=931198142 Len=21 Win=49680 server -> client TCP > D=852 S=13724 Push Ack=931198163 Seq=392120627 Len=33 Win=33120 > client -> server TCP D=13724 S=852 Ack=392120660 > Seq=931198163 Len=0 Win=49680 client -> server TCP > D=811 S=13782 Push Ack=1618165286 Seq=912667687 Len=2 Win=49680 > server -> client TCP D=13782 S=811 Ack=912667689 > Seq=1618165286 Len=0 Win=34500 > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Cybercity Webhosting (http://www.cybercity.dk) _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu