02-03-2023 05:24 AM
Hello,
I have a problem with configuration of our VLAN network with our VoIP provider.
We have set-up Cisco Router C860 with a P2P connection between us on VLAN 1467 with host on our side on 100.64.0.53/30 and their side 100.64.0.54/30 which works perfectly (we can ping each others).
Next step is that on their side above IP 100.64.0.54/30 are IPs of network 5.226.X.X/29.
I have added a route:
5.226.X.X [1/0] via 100.64.0.54
5.226.Y.Y [1/0] via 100.64.0.54
Pinging via cisco CLI works correctly on these addrresess.
Then i have our server with 2 NICs.
Eth0 with WAN connection
Eth1 with VLAN 100.64.0.53
From Eth1 i can ping their VLAN IP but cannot reach above it. Provider also cannot reach our IP (Eth0 WAN) above our VLAN IP.
Firewall rules are disabled.
I'm sorry if there is a answer on forum but i was looking for solution for over a week and coludn't find an answer also I'm a newbie in this matter.
Below is actual config for VLAN.
interface FastEthernet0
switchport access vlan 1467
no ip address
!
interface FastEthernet1
switchport access vlan 1467
no ip address
!
interface Vlan1467
ip address 100.64.0.53 255.255.255.252
ip route 5.226.X.X 255.255.255.248 100.64.0.54
ip route 5.226.Y.Y 255.255.255.248 100.64.0.54
Thanks in advance for help.
02-03-2023 06:03 AM - edited 02-03-2023 06:05 AM
Then i have our server with 2 NICs.
Eth0 with WAN connection
Eth1 with VLAN 100.64.0.53
how is your routing on the Server for this
route print give you an idea, if you setup a default gateway for this you need to make change, also change metric if required.
best is setup a IP address with out gateway and add static route towards 100.64.0.54
Another question, what IP address configured on Eth1 ? (f this was configured 100.64.0.53 - then this is conflict with switch IP right ??)
02-05-2023 11:30 PM - edited 02-05-2023 11:39 PM
Hello,
I've deleted IP from VLAN on router and right now pings are working correctly (without drops) to VLAN IP 100.64.0.54. Still we have a problem with pinging IPs 5.226.X.X and 5.226.Y.Y. When i had an ip route added on cisco router i could ping these addresses but via server i cannot. For test i've disabled WAN NIC on server and configured only VLAN with ip route but still couldn't ping providers IPs. Below i attach how network looks like (entire network works only with static IPs)
02-06-2023 12:40 AM
Hello
@mjCompany wrote:
Hello,
Still we have a problem with pinging IPs 5.226.X.X and 5.226.Y.Y. When i had an ip route added on cisco router i could ping these addresses but via server i cannot.
The reason is you are trying to bridge the 10.64.0..0 subnet, but havnet set bridging up.
on the router try the following:
conft
bridge irb
bridge 1 protocol ieee
bridge 1 route ip
int x/x
Description facing SBC
no ip address
bridge group 1
int x/x
Description facing Server
no ip address
bridge group 1
int bvi 1
ip address 100.64.0.x 255.255.x.x
no shut
02-06-2023 01:34 AM
int Fa1
Description facing SBC
no ip address
bridge-group 1 <-- when i do this i get info FastEthernet1 does not support bridging
02-07-2023 02:22 AM
I'm little confused about the setup. You said that when you configured the ip address and the static routes on the router, then you where able to ping both next hop and also the server with 5.226 adresses. That proves that the concept works. But when you remove the address from the router and configure your server with 10.64.0.53 you can only ping 10.64.0.54 and not the 5.226 adresses. That proves your router acts as switch, sending packets between 2 ports in the same vlan, and is not a router anymore. Have you configured those routes on your server? Because when you remove the address from the router, those 2 routes will be unavailable due to the fact that the router don't have the address 10.60.0.53 anymore. The router will just act as a switch in this scenario switching traffic between 2 ports in the same vlan.
02-07-2023 02:51 AM - edited 02-07-2023 02:52 AM
Yes i've tried to add routes like:
ip route add 5.226.X.X/29 via 100.64.0.54
ip route add 5.226.X.X/29 dev eth1
ip route add 5.226.X.X/29 via 100.64.0.53 <--- this i added after checking that ip route via .54 didn't work.
and it still doesn't work.
Even i disabled WAN (eth0) for tests purpose and added GW:100.64.0.54 to eth1 to move all traffic to VLAN but still doesn't work.
02-08-2023 01:41 AM
You said you can ping 100.64.0.54, to be 100% sure this ping is going via your cisco router, disconnect the port that goes to the provider, not the port to the server, and see if the ping stops. If it stops and start to function again when you reconnects the provider, then we are sure the communication is going the correct way and not via internet. If the result from this test is as wanted, you have problem with the routing table in the server.
02-15-2023 12:17 AM
Thank you everyone for help. Right now i have a correct connection between my server and provider. The last problem is that i need to route outgoing SIP/RTP traffic to 5.226.X.X. The order of the route should be like this:
WAN IP(82.177.X.X)->VLAN(100.64.0.53)->cisco router VLAN 1467->P2P provider SBC(100.64.0.54)->5.226.X.X
I need to send SIP/RTP traffic "hiding" behind this WAN IP. Right now i can send packets correctly but only using LAN 100.64.0.53
11-11-2024 04:15 AM
HI Can you help me i need same configuration to our company. how to configuration sip with Airtel sip.Please find the over ip address.
Wan ip address our ip address 10.21.25.2-airtel ip address 10.21.25.3 and P2P provider SBC(10.5.8.225)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide