Displaying 20 results from an estimated 4000 matches similar to: "Fw: iax2 bindaddress: how to reload so iax2 can bind to an alias IP"
2009 Jan 09
1
iax2 bindaddress: how to reload so iax2 can bind to an alias IP
I'm trying to figure out how to reload iax2 (without breaking existing calls) so it can listen on a new IP address (like "ip addr add local ..."). This alias IP is added/removed by a custom process (script) for clustering purposes.
The iax.conf file contains "bindaddr=0.0.0.0".
I tried a "iax2 reload" (executed without errors or warnings) but I'm still not
2014 Mar 05
0
Cannot chain to another PXE server on the same subnet
On Wed, Mar 5, 2014 at 1:55 AM, Vieri <rentorbuy at yahoo.com> wrote:
> Sorry for top-posting but my webmail forces me to.
Odd. It's been a while since I used Yahoo but I didn't think I had
that issue. GMail does default to top-posting but clicking the
ellipsis to look at the previous email is enough.
> I added -W to the APPEND line as suggested but I'm still getting
2014 Mar 05
2
Cannot chain to another PXE server on the same subnet
Sorry for top-posting but my webmail forces me to.
I added -W to the APPEND line as suggested but I'm still getting the same result:
Booting...
Altiris, inc. X86PC PreBoot, PXE-2.x Enhanced
Build ID=402
PXEPreZero: Invalid PXE Server list format.
and the client PC freezes right there.
Here's the full content of my dhcp.conf:
max-lease-time 86400;
ddns-update-style interim;
2018 Nov 08
0
Getting two different guest in the same network
Dear list,
Being a libvirt noob, I have some trouble understanding.
It is about getting two different guest in the same network.
***********
I've defined a network with libvirt. This is the source xml:
<network>
<name>private2</name>
<uuid>9684f2c6-6fd0-491b-9cb5-80ee268b01ce</uuid>
<bridge name='br2' stp='on' delay='0'/>
2019 Feb 08
0
netmask on aliases overriden by netmask on interface
On 08.02.19 15:08, James B. Byrne via CentOS wrote:
> # ifconfig eth1:192008001
> eth1:192008001 Link encap:Ethernet HWaddr 00:25:90:61:74:C1
> inet addr:192.168.8.1 Bcast:192.168.8.255
> Mask:255.255.255.128
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:17 Memory:feae0000-feb00000
>
> Which shows that the network mask is
2009 Mar 02
1
early dial (or overlap dial) and Asterisk 1.2 vs. 1.4
Hi,
I am testing some IP phones (eg. GXP2000) and noticed that the "early dial" feature works fine with Asterisk 1.4 but not with 1.2.
"early dial" is when digits are sent immediately, one by one, and Asterisk replies with a "484 Address Incomplete" and waits for the next digit until a match is found. This is a very useful feature where no dial patterns have to be
2008 Mar 05
2
Passing variables between two DUNDi/IAX2 peers
Hi.
I am trying to pass a variable from one Asterisk PBX
to another.
I'm using DUNDi with IAX2. Is there a way to do it?
I tried the following but it fails.
On peer1:
[dundi-outgoing]
switch => DUNDI/priv
exten => s,1,Set(CDR(userfield)=test)
exten => s,2,Set(DUNDIVAR=${ARG1}#TEST)
exten => s,3,NoOp(Passing ${DUNDIVAR} to DUNDi peer.)
exten => s,4,Goto(${DUNDIVAR},1)
On
2018 Nov 17
2
Cannot connect when using BindAddress
Hi there,
Thanks for tinc, firstly. It's awesome. Now, I've found that if I specify:
BindAddress = 127.0.0.1 655
Then my tincd cannot make outbound connections (on attempting to
connect to another tinc daemon is receives 'Invalid argument').
Removing BindAddress fixes the issue. Unless I've misunderstood the
purpose of this option, is this a bug?
I'm running v1.0.35 on
2009 Dec 14
1
[Bug 1685] New: ssh attempts v4 connection w/v6 BindAddress setting in ssh config
https://bugzilla.mindrot.org/show_bug.cgi?id=1685
Summary: ssh attempts v4 connection w/v6 BindAddress setting in
ssh config
Product: Portable OpenSSH
Version: 5.3p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Miscellaneous
AssignedTo:
2010 May 13
2
LAN IAX2 trunk bad audio quality vs. LAN SIP trunk good audio quality
Hi,
I have an audio quality problem regarding IAX2. I have 2 Asterisk servers interconnected via 2 LAN trunks at 1Gbps (no nat, no firewall).
One trunk is SIP and the other IAX2.
Normally, I use IAX2 but have noticed easily reproducible audio quality problems (voice in/out is OK but there's a "third" noise overlapping with a "scratchy sound" as if it were some kind of
2002 Mar 21
1
BindAddress with Openssh
Hi
In a nutshell, the BindAddress functionality doesn't seem to work (at
least on Solaris 7 when using the fake-gettaddrinfo module provided). I
haven't been able to test on other OS versions or using an OS library
provided getaddrinfo (such as OpenBSD), but the unless the functionality
of getaddrinfo is majorly different, I think this problem would be
similar everywhere.
The code in
2018 Nov 17
0
Cannot connect when using BindAddress
The only thing „localhost“ can talk to is „localhost“ - by definition & independently of tinc.
What are you trying to accomplish with that choice?
Clemens
Von meinem iPad gesendet
> Am 17.11.2018 um 21:58 schrieb Jonny Tyers <jtyers at gmail.com>:
>
> Hi there,
>
> Thanks for tinc, firstly. It's awesome. Now, I've found that if I specify:
>
>
2002 Nov 21
0
[Bug 441] New: should ssh BindAddress apply to LocalForward ports
http://bugzilla.mindrot.org/show_bug.cgi?id=441
Summary: should ssh BindAddress apply to LocalForward ports
Product: Portable OpenSSH
Version: 3.5p1
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: ssh
AssignedTo: openssh-unix-dev at mindrot.org
2018 Nov 17
3
Cannot connect when using BindAddress
I want tinc to listen locally on loopback, so that port 655 is not
exposed on any system interfaces. Can't tinc make outbound connections
when listening on loopback? I can't see any reason why it should. This
system will never have other tinc daemons connect to it, it will only
ever connect to other tinc daemons in order to establish a VPN
connection.
--
Jonny Tyers
On Sat, 17 Nov 2018
2002 Nov 21
0
[Bug 441] should ssh BindAddress apply to LocalForward ports
http://bugzilla.mindrot.org/show_bug.cgi?id=441
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From markus at openbsd.org 2002-11-22
2011 Sep 06
2
[Bug 1211] option BindAddress is ignored by option UsePrivilegedPort
https://bugzilla.mindrot.org/show_bug.cgi?id=1211
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |1930
--- Comment #4 from Damien Miller <djm at mindrot.org> 2011-09-06 10:34:10 EST ---
Retarget unresolved
2013 Jul 25
1
[Bug 1211] option BindAddress is ignored by option UsePrivilegedPort
https://bugzilla.mindrot.org/show_bug.cgi?id=1211
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |2130
--- Comment #12 from Damien Miller <djm at mindrot.org> ---
Retarget to openssh-6.4
--
You are
2013 Sep 19
2
[Bug 1211] option BindAddress is ignored by option UsePrivilegedPort
https://bugzilla.mindrot.org/show_bug.cgi?id=1211
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dtucker at zip.com.au
Status|NEW |ASSIGNED
Assignee|openssh-bugs at
2016 Aug 02
0
[Bug 1211] option BindAddress is ignored by option UsePrivilegedPort
https://bugzilla.mindrot.org/show_bug.cgi?id=1211
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #16 from Damien Miller <djm at mindrot.org> ---
Close all resolved bugs after 7.3p1 release
2018 Nov 17
0
Cannot connect when using BindAddress
On Sat, Nov 17, 2018 at 11:20:47PM +0000, Jonny Tyers wrote:
> I want tinc to listen locally on loopback, so that port 655 is not
> exposed on any system interfaces. Can't tinc make outbound connections
> when listening on loopback? I can't see any reason why it should. This
> system will never have other tinc daemons connect to it, it will only
> ever connect to other tinc