LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 03-04-2015, 05:18 PM   #1
brett2name33
LQ Newbie
 
Registered: Mar 2015
Posts: 4

Rep: Reputation: Disabled
KVM Asterisks 2 diffrent networks


I setup a server Using Debian 7
using the onboard main network card and a dual network card

i run two networks one 192.168.1.1 for email and web and a seperate one for voip keeping networks seperate. So eth1 bridged runs voip and the onboard card seems to handle the openvz samba server I have running. (I plan later to move all to kvm or within a kvm runnung openvz)

DSL1 ---- router1 for data ---- Switch1 for data --- Openvz eth0
KVM
DSL2 ---- router1 for voip ---- Switch2 for voip --- Bri1 Eth1

having some lag and disconnects and made a guess its because i have two networks with same range 192.168.1.x so i made the phones (voip) 192.168.2.x but its still really laggy in the terminal and after i get things all connected and working good all of a sudden I get this lag and everything falls apart


Am able to setup a vm with asterisk (I am savvy on that ) everything is working great (though seems little laggy)

then my extentions start to lagg and are not longer connected
Code:
[2015-03-04 17:46:12] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer 'outSIPPRV1' is now UNREACHABLE!  Last qualify: 32
[2015-03-04 17:46:25] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer '214' is now UNREACHABLE!  Last qualify: 37
[2015-03-04 17:46:37] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'outSIPPRV1' is now Reachable. (1179ms / 2000ms)
[2015-03-04 17:46:53] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer '214' is now Reachable. (502ms / 4688ms)
pbx*CLI> sip show peers
Name/username             Host                                    Dyn Forcerport ACL Port     Status     
111                       (Unspecified)                            D              A  0        UNKNOWN    
112                       (Unspecified)                            D              A  0        UNKNOWN    
114                       (Unspecified)                            D              A  0        UNKNOWN    
115                       (Unspecified)                            D              A  0        UNKNOWN    
200                       (Unspecified)                            D   N          A  0        UNKNOWN    
201/201                   192.168.2.74                             D              A  2048     UNREACHABLE 
202                       (Unspecified)                            D              A  0        UNKNOWN    
210                       (Unspecified)                            D              A  0        UNKNOWN    
211/211                   192.168.2.37                             D              A  2048     UNREACHABLE 
212/212                   192.168.2.36                             D              A  2048     UNREACHABLE 
213/213                   192.168.2.55                             D              A  5060     OK (47 ms) 
214/214                   192.168.2.75                             D              A  5060     OK (502 ms) 
215/215                   192.168.2.79                             D              A  2048     UNREACHABLE 
216/216                   192.168.2.40                             D              A  2048     UNREACHABLE 
217/217                   192.168.2.52                             D              A  2048     UNREACHABLE 
218/218                   192.168.2.35                             D              A  2052     UNREACHABLE 
219/219                   192.168.2.34                             D              A  2048     UNREACHABLE 
220/220                   192.168.2.91                             D              A  2052     UNREACHABLE 
2201                      (Unspecified)                            D              A  0        UNKNOWN    
221/221                   192.168.2.94                             D              A  2051     UNREACHABLE 
222/222                   192.168.2.28                             D              A  2049     UNREACHABLE 
224                       (Unspecified)                            D              A  0        UNKNOWN    
225                       (Unspecified)                            D              A  0        UNKNOWN    
312                       (Unspecified)                            D              A  0        UNKNOWN    
315                       (Unspecified)                            D              A  0        UNKNOWN    
333/333                   192.168.2.23                             D              A  2048     UNREACHABLE 
inSIPPRV4/SIPPRV4   IPsip4x.x.x.x                               N             5060     Unmonitored 
outSIPPRV1/SIPPRV1    IPsip1x.x.x.x                                N             5060     OK (1179 ms) 
outSIPPRV4/SIPPRV4  IPsip4x.x.x.x                               N             5060     OK (39 ms) 
SIPpRovider2_out/SIPPRV2     IPsip2x.x.x.x                                N             5060     OK (51 ms) 
SIPpRovider3_out/SIPPRV3     IPsip3x.x.x.x                               N             5060     OK (55 ms) 
31 sip peers [Monitored: 6 online, 24 offline Unmonitored: 1 online, 0 offline]
[2015-03-04 17:47:08] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'SIPpRovider2_out' is now Lagged. (2031ms / 2000ms)
[2015-03-04 17:47:08] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'SIPpRovider3_out' is now Lagged. (2047ms / 2000ms)
[2015-03-04 17:47:18] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'SIPpRovider2_out' is now Reachable. (31ms / 2000ms)
[2015-03-04 17:47:18] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'SIPpRovider3_out' is now Reachable. (46ms / 2000ms)
[2015-03-04 17:47:19] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer '333' is now UNREACHABLE!  Last qualify: 2030
[2015-03-04 17:48:01] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer '214' is now Lagged. (5038ms / 4688ms)
[2015-03-04 17:48:11] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer '213' is now UNREACHABLE!  Last qualify: 1046
[2015-03-04 17:48:11] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer '214' is now Reachable. (38ms / 4688ms)
[2015-03-04 17:48:22] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer 'SIPpRovider3_out' is now UNREACHABLE!  Last qualify: 46
[2015-03-04 17:48:28] WARNING[3178]: chan_sip.c:3821 retrans_pkt: Retransmission timeout reached on transmission 544140aa0dfe96537c23c78e73c12b74@127.0.1.1 for seqno 128 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
[2015-03-04 17:48:35] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer '213' is now Reachable. (48ms / 2000ms)
[2015-03-04 17:48:46] NOTICE[3178]: chan_sip.c:13661 sip_reg_timeout:    -- Registration for 'SIPPRV3@toronto.voip.ms' timed out, trying again (Attempt #14)
[2015-03-04 17:48:48] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'SIPpRovider3_out' is now Reachable. (1433ms / 2000ms)
[2015-03-04 17:48:48] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'outSIPPRV1' is now Lagged. (2040ms / 2000ms)
[2015-03-04 17:48:53] NOTICE[3178]: chan_sip.c:13661 sip_reg_timeout:    -- Registration for 'SIPPRV1@montreal2.voip.ms' timed out, trying again (Attempt #2)
[2015-03-04 17:48:58] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'outSIPPRV1' is now Reachable. (29ms / 2000ms)
[2015-03-04 17:49:12] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer 'outSIPPRV4' is now UNREACHABLE!  Last qualify: 1025
[2015-03-04 17:49:23] NOTICE[3178]: chan_sip.c:27072 sip_poke_noanswer: Peer 'SIPpRovider2_out' is now UNREACHABLE!  Last qualify: 1032
[2015-03-04 17:49:34] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'SIPpRovider2_out' is now Reachable. (1031ms / 2000ms)
[2015-03-04 17:49:36] NOTICE[3178]: chan_sip.c:21600 handle_response_peerpoke: Peer 'outSIPPRV4' is now Reachable. (164ms / 2000ms)
What the heck is going on..

here is my debian server config
Code:
# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.101   *               255.255.255.255 UH    0      0        0 venet0
192.168.1.0     *               255.255.255.0   U     0      0        0 br0
192.168.1.0     *               255.255.255.0   U     0      0        0 br1
192.168.1.0     *               255.255.255.0   U     0      0        0 br2
default         192.168.1.1     0.0.0.0         UG    0      0        0 br0
# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

#+The primary network interface+++++#
allow-hotplug eth0
#iface eth0 inet dhcp
#iface eth0 inet static

#address 192.168.1.42
#netmask 255.255.255.0
#gateway 192.168.1.1
#broadcast 192.168.1.255
#network 192.168.1.0

auto eth0
iface eth0 inet manual
                                                                                                                                                                                    
auto br0                                                                                                                                                                            
iface br0 inet dhcp                                                                                                                                                                 
        bridge_ports eth0                                                                                                                                                           
        bridge_stp off                                                                                                                                                              
        bridge_fd 0                                                                                                                                                                 
        bridge_maxwait 0                                                                                                                                                            
                                                                                                                                                                                    
#iface br0 inet static                                                                                                                                                              
#        address 192.168.1.40                                                                                                                                                       
#        network 192.168.1.0                                                                                                                                                        
#        netmask 255.255.255.0                                                                                                                                                      
#        broadcast 192.168.1.255                                                                                                                                                    
#        gateway 192.168.1.1
#        bridge_ports eth0
#        bridge_stp off
#        bridge_fd 0
#        bridge_maxwait 0
#+++++++++++++++++++++++++++++++++++#
allow-hotplug eth1
#iface eth1 inet dhcp
#iface eth1 inet static

#address 192.168.1.41
#netmask 255.255.255.0
#gateway 192.168.1.1
#broadcast 192.168.1.255
#network 192.168.1.0

auto eth1
iface eth1 inet manual

auto br1
#iface br1 inet dhcp
#        bridge_ports eth0
#        bridge_stp off
#        bridge_fd 0
#        bridge_maxwait 0

iface br1 inet static
        address 192.168.1.41
        network 192.168.1.0
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0
#+++++++++++++++++++++++++++++++++++#

auto eth2
iface eth2 inet manual

auto br2
#iface br2 inet dhcp
#        bridge_ports eth0
#        bridge_stp off
#        bridge_fd 0
#        bridge_maxwait 0

iface br2 inet static
        address 192.168.1.42
        network 192.168.1.0
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0
Now this is weird when i connect to the voip router via a phone or direct and do a traceroute

So some times it traceroutes no problem some times it just goes through all these hops with **'s some times can ping sometimes not Agh
Code:
.$#  route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         VOIP             0.0.0.0         UG    0      0        0 eth0
192.168.2.0     *               255.255.255.0   U     0      0        0 eth0
.$# ping 192.168.1.104
PING 192.168.1.104 (192.168.1.104) 56(84) bytes of data.
From 192.168.2.2: icmp_seq=3 Redirect Host(New nexthop: 192.168.2.1)
From 192.168.2.2 icmp_seq=3 Redirect Host^C
--- 192.168.1.104 ping statistics ---
32 packets transmitted, 0 received, +1 errors, 100% packet loss, time 30998ms

.$# traceroute 192.168.2.104
traceroute to 192.168.2.104 (192.168.2.104), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * *^C
.$# traceroute 192.168.2.1
traceroute to 192.168.2.1 (192.168.2.1), 30 hops max, 60 byte packets
 1  BMP1 (192.168.2.1)  2.127 ms  2.572 ms  3.077 ms
.$# traceroute 192.168.2.104
traceroute to 192.168.2.104 (192.168.2.104), 30 hops max, 60 byte packets
 1  192.168.2.104 (192.168.2.104)  0.623 ms  0.598 ms  0.573 ms
.$# traceroute 192.168.2.104
traceroute to 192.168.2.104 (192.168.2.104), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * 192.168.2.104 (192.168.2.104)  2792.244 ms
.$# traceroute 192.168.2.104
traceroute to 192.168.2.104 (192.168.2.104), 30 hops max, 60 byte packets
 1  192.168.2.104 (192.168.2.104)  0.523 ms  0.489 ms  0.678 ms
.$# traceroute 192.168.2.104
traceroute to 192.168.2.104 (192.168.2.104), 30 hops max, 60 byte packets
 1  192.168.2.104 (192.168.2.104)  0.566 ms * *
 
Old 03-04-2015, 06:33 PM   #2
brett2name33
LQ Newbie
 
Registered: Mar 2015
Posts: 4

Original Poster
Rep: Reputation: Disabled
I am not having much luck finding examples about configurations with 2 diffrent networks connected to two diffrent network cards on a kvm . I find alot with vlans but i have two seperate connection no shared network. Should I have the bridge eth1 setup for the 192.168.2.x network.

i am running openvz side by side meaning I am running a 2.6.32_openvz-042stab094.7-amd64 kernel not that it matters but i have 8 cores.

there is point where typing in ssh it laggs as I type . where should I be looking for errors

note my attempts to run openvz making a vnet0 that talks to the eth1 (making a veth104.0 I stopped it for now ) just plain did not work so I created a kvm VM using a bridged eth1 e1000 virtual card and it seemed at first to work..

I just noticed this in my dmesg on my hardware ssh

Code:
# dmesg |grep eth
[    1.910016] tg3 0000:04:05.0: eth0: Tigon3 [partno(BCM95704CA40_HYB) rev 2100] (PCI:33MHz:32-bit) MAC address 00:10:18:24:4e:4a
[    1.910020] tg3 0000:04:05.0: eth0: attached PHY is 5704 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[    1.910022] tg3 0000:04:05.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[    1.910024] tg3 0000:04:05.0: eth0: dma_rwctrl[763f0000] dma_mask[64-bit]
[    1.913340] r8169 0000:02:00.0: eth1: RTL8168f/8111f at 0xffffc90000c60000, 40:16:7e:e8:bc:86, XID 08000800 IRQ 64
[    1.913343] r8169 0000:02:00.0: eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    1.923676] tg3 0000:04:05.1: eth2: Tigon3 [partno(BCM95704CA40_HYB) rev 2100] (PCI:33MHz:32-bit) MAC address 00:10:18:24:4e:4b
[    1.923679] tg3 0000:04:05.1: eth2: attached PHY is 5704 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[    1.923681] tg3 0000:04:05.1: eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[    1.923683] tg3 0000:04:05.1: eth2: dma_rwctrl[763f0000] dma_mask[64-bit]
[    3.832488] <30>udevd[572]: renamed network interface eth1 to rename3
[    3.853058] <30>udevd[552]: renamed network interface eth0 to eth1
[    3.882619] <30>udevd[572]: renamed network interface rename3 to eth0
[    7.340858] device eth0 entered promiscuous mode
[    7.486335] r8169 0000:02:00.0: eth0: link down
[    7.486342] r8169 0000:02:00.0: eth0: link down
[    7.556749] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.321855] r8169 0000:02:00.0: eth0: link up
[   10.322782] br0: port 1(eth0) entering forwarding state
[   10.322787] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   16.344569] device eth1 entered promiscuous mode
[   16.426489] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   19.575678] tg3 0000:04:05.0: eth1: Link is up at 1000 Mbps, full duplex
[   19.575681] tg3 0000:04:05.0: eth1: Flow control is off for TX and off for RX
[   19.576145] br1: port 1(eth1) entering forwarding state
[   19.576161] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   21.268025] eth0: no IPv6 routers present
[   23.815094] eth1: received packet with own address as source address
[   23.823020] eth1: received packet with own address as source address
[   23.897462] eth1: received packet with own address as source address
[   23.915092] eth1: received packet with own address as source address
[   24.398406] eth1: received packet with own address as source address
[   24.457538] eth1: received packet with own address as source address
[   24.466351] eth1: received packet with own address as source address
[   24.529460] eth1: received packet with own address as source address
[   24.773698] eth1: received packet with own address as source address
[   24.790230] eth1: received packet with own address as source address
[   28.829101] eth1: received packet with own address as source address
[   28.908700] eth1: received packet with own address as source address
[   28.913923] eth1: received packet with own address as source address
[   28.922959] eth1: received packet with own address as source address
[   28.923498] eth1: received packet with own address as source address
[   28.933821] eth1: received packet with own address as source address
[   29.008760] eth1: received packet with own address as source address
[   29.029708] eth1: received packet with own address as source address
[   29.033952] eth1: received packet with own address as source address
[   29.037168] eth1: received packet with own address as source address
[   33.945124] eth1: received packet with own address as source address
[   33.945726] eth1: received packet with own address as source address
[   34.054430] eth1: received packet with own address as source address
[   34.385732] eth1: received packet with own address as source address
[   34.404139] eth1: received packet with own address as source address
[   34.436312] eth1: received packet with own address as source address
[   34.584693] eth1: received packet with own address as source address
[   34.587120] eth1: received packet with own address as source address
[   34.594238] eth1: received packet with own address as source address
[   34.669789] eth1: received packet with own address as source address
[   36.308017] veth104.0: no IPv6 routers present
[   38.967705] eth1: received packet with own address as source address
[   38.968283] eth1: received packet with own address as source address
[   38.969402] eth1: received packet with own address as source address
[   39.028349] eth1: received packet with own address as source address
[   39.029152] eth1: received packet with own address as source address
[   39.030352] eth1: received packet with own address as source address
[   39.067343] eth1: received packet with own address as source address
[   39.067940] eth1: received packet with own address as source address
[   39.108797] eth1: received packet with own address as source address
[   39.176829] eth1: received packet with own address as source address
[   44.025169] eth1: received packet with own address as source address
[   44.284032] eth1: received packet with own address as source address
[   44.524232] eth1: received packet with own address as source address
[   44.705052] eth1: received packet with own address as source address
[   44.803056] eth1: received packet with own address as source address
[   44.983080] eth1: received packet with own address as source address
[   45.097899] eth1: received packet with own address as source address
[   45.232783] eth1: received packet with own address as source address
[   45.760855] eth1: received packet with own address as source address
[   45.864921] eth1: received packet with own address as source address
 
Old 03-04-2015, 06:36 PM   #3
brett2name33
LQ Newbie
 
Registered: Mar 2015
Posts: 4

Original Poster
Rep: Reputation: Disabled
Umm I dunno every time I solve a problem it happens again. like a fresh reboot all is good for a hour or so then bang

I read a post http://forum.proxmox.com/threads/918...ress-as-source and rembered I hooked up a used gigabyte switch so I deceied to remove it seems fine at the moment..


I will update in a day or 2 if it is the problem. note its a hp procurve 24something

the older is also a hp procurve but a 100/10
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] KVM virtual networks not routing properly theillien Linux - Networking 5 10-21-2017 07:37 PM
How to configure Asterisks on Fedora 10 myasir_genious Linux - Newbie 1 11-23-2009 12:35 PM
Need help with vpn solution connecting two diffrent networks. brittney Linux - Networking 1 10-12-2007 02:27 PM
pointers names with one and two asterisks? hubabuba Programming 3 03-19-2006 04:00 PM
How to assign diffrent ip/hostnames to diffrent services koppaspider Linux - General 1 02-10-2006 09:03 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 11:44 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration