[AG-TECH] Binding a bridge to a nic

Thomas D. Uram turam at mcs.anl.gov
Thu Jun 26 18:26:06 CDT 2008


Hi Jon:

Try setting the AG_HOSTNAME environment variable to the name/ip of the 
NIC you want to use.

Tom


On 6/26/08 8:56 PM, Jon Johansson wrote:
> Hi,
>
> I'm moving my bridge to a new machine and I would like to bind
> the bridge process to a particular nic because the other one
> is going to be busy doing other stuff. I can't seem to make it
> work, though. I've used the 'listenPort' option to the Bridge3.py
> where
>    IPADDRESS="129.128.125.61:23000"
>    --listenPort=$IPADDRESS
> but listenPort is supposed to be an integer, only the port number.
>
> When I run the bridge without this, the ip address of the other
> nic appears in the bridge registry.
>
> Is there any way to force the bridge process to use a particular
> nic?
>
> Thanks,
> Jon.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~   Jon I Johansson, Ph.D.              * Tel.: (780) 492-9304   ~~
> ~~   jon.johansson at ualberta.ca           * Fax.: (780) 492-1729   ~~
> ~~                                       * Office: G.S.B. 323C    ~~
> ~~   Programmer/Analyst          http://sciviz.aict.ualberta.ca   ~~
> ~~                                                                ~~
> ~~   Research Computing Support                                   ~~
> ~~   Room 352, General Services Building                          ~~
> ~~   Academic Information and Communication Technologies (AICT)   ~~
> ~~   University of Alberta                                        ~~
> ~~   Edmonton, Alberta, CANADA, T6G 2H1                           ~~
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ! "This  communication is intended for the use of the recipient to !
> ! which  it  is addressed, and may contain confidential, personal, !
> ! and/or  privileged  information.  Please contact  us immediately !
> ! if you are not the  intended  recipient  of  this communication. !
> ! If you are not the  intended  recipient  of  this communication, !
> ! do  not  copy,  distribute,   or   take   action  on   it.   Any !
> ! communication  received  in  error,  or subsequent reply, should !
> ! be deleted or destroyed."                                        !
> !------------------------------------------------------------------!
>
>
>
>
>   




More information about the ag-tech mailing list