Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] pS-3.4 primary address config

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] pS-3.4 primary address config


Chronological Thread 
  • From: Aaron Brown <>
  • To: Chad Kotil <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] pS-3.4 primary address config
  • Date: Tue, 18 Nov 2014 18:38:04 +0000
  • Accept-language: en-US

Hey Chad,

Can you try setting the “primary_interface eth0” or whatever the
primary interface is? I’m not sure if that does what you want, or if you’d
like something else.

Cheers,
Aaron

On Nov 18, 2014, at 12:55 PM, Chad Kotil
<>
wrote:

> Hello Perfsonar-Users,
> After updating to 3.4 on a multi homed test point I am now unable to
> tell the toolkit UI which interface to use as the primary address. It
> just seems to choose the default interface. In the past there was a
> file, external_addresses, that could be use to tune things closer to how
> I want them. I have read this file is no longer used:
> http://www.perfsonar.net/about/faq/#Q70
>
> I've already set allow_internal_addresses in
> /opt/perfsonar_ps/toolkit/web/root/gui/services/etc/web_admin.conf
>
> and have tried setting things like:
> external_address=
> default_accesspoint=
> default_ipv4_address=
> default_ipv6_address=
> default_accesspoint_iface=
> default_ipv4_address_iface=
> default_ipv6_address_iface=
> default_iface_speed=10000000000
> default_iface_mtu=9000
>
> I've also tried to override settings in ls_registration_daemon.conf.
>
> But nothing has worked so far.
>
> How can I tell the toolkit to use another interface in 3.4?
>
> Thanks,
> --Chad




Archive powered by MHonArc 2.6.16.

Top of Page