use of eth1 NIC

[perlmutr]

I have 2 systems. the first is a full vicidial machine. the second is only a dialer.

when I tried running them the traffic disrupted all activity on my local network. I have installed a second NIC in each system and defined them as eth1.

I have fios coming in going to a switch which then goes to a router for my local network.

I have cabled the 2 new eth1 nic's to the switch and have assigned them to unique static ip's.

How do I tell vicidial to use eth1 for my voip traffic to my external sip provider?

Thank you in advance

installation Details:
Vicidibox-7.0.3
Version: 2.12b0.5
BUILD: 160414-1013
SVN Version: 2534

[chornyi_taras]

You can isolate you Vicidial traffic from management traffic using different subnets,
or you can add rule in linux route table for specific types of traffic to use specific interfaces

[williamconley]

This is NOT a Vicidial question. It's a simple networking question.

You don't "tell" an OS to use one network for "voip traffic" and another network for "other stuff". Networking packets are routed based on destination IP and Port (note: it can be done, but it's very complicated ... and unnecessary). If you are running your server with a local IP (on eth0?) and a public IP (on eth1?) ... you configure a "gateway" for eth1 and you do NOT configure or assign a gateway to eth0. Thus NO public traffic will be sent on the local network as that route will not reach the internet. local traffic ONLY will be sent on the local IP based on the subnet mask in use for that network. If both are using DHCP, you'll need to change to static and manually configure it (and avoid the gateway configuration! LOL). If you do manually configure the network card, you may want to either "reserve" the IP on the router or assign an IP outide the range of the DHCP assignment to avoid a collision later on.

For instance: If your eth0 interface is configured with 192.168.1.100 (your IP) and a subnet mask of 255.255.255.0 (or /24), then ONLY network traffic heading for IPs 192.168.1.1 through 192.168.1.255 will be sent over eth0 since that is the only destination available at that route. As long as you avoid putting a Gateway on that network port, no other traffic will be sent.

Since you have Verizon FiOS, however, you SHOULD get a public IP directly to the Vicidial servers and use the Dynamic Good Guys firewall instead of routing through ANY router at all. Five IPs is about $20/month if I recall correctly. And then you'd still only be using three IPs: 1 for the Router (office, humans) and 2 for Vicidial servers.

None of this works if both network ports (eth0/eth1) are on the same network. IE: You can not have 192.168.1.100 and 192.168.1.155 on two network ports connected to the same router. Those are really the same network and will share traffic regardless of what else you attempt to do. If you do get networking to work that way, you will find out you've wasted your time as the traffic will still be sent to the entire network through all connected switches and ports, backwashing from the router's local network ports will be part of that routing. The only viable way to accomplish this with two private networks would be to "nest" one of them inside another local router. In that case, you'd have the two Vicidials on the first router (single NAT, connected directly to the primary router) and another (secondary) router also connected. Then, in the new private network created by the secondary router, you could have all your agents and a second network port for Vicidial ... manually configured to avoid a gateway.Vicidial would be able to communicate with the agents via the secondary router and with the world via the primary router. Agents would have internet via the "double NAT" route through both routers. As long as the agents don't use VOIP other than Vicidial, this has been known to work. But not nearly as well as giving each Vicidial server its own Public IP address.