Tag Info

Hot answers tagged

3

Actually it's not colliding. One subnet has more specific mask 192.168.0.0/24 has more specific mask than 192.168.0.0/16 For example default gateway is default because it has less specific mask /0. If you add a route to 192.168.0.3/32 via another interface it would have more specific mask than other two routes.


2

The routing table is a system-wide thing, and not user-specific. So, it is not really simple. The steps are the following: 1: Create the multiple routing tables with the extensive usage of the ip route and ip rule commands. 2: Set up iptables to mark the outgoing packets based on the UID of the sender process. 3: Set up your routing tables based on the ...


2

Routing table looks okay, look at metric column. Route with the lowest metric will be preferred. Your routing table contains now two default routes and 10.11.12.13 will be preferred over 192.168.178.1 because of lower metric. About the traffic on physical interface; this is also normal because you have listening services which respond for ...


1

without knowing network prefixes of all the networks that all routers in table are being attached to? What makes you think, there is not a table of all the networks? OSPF is Link State routing protocol. So it has to know. (At least for networks inside an area. There are differences routing across areas.) And by the way, usually (I am sure this is true ...


1

I've found the solution for this in case you still need it: Right Click on every Interface in the RRAS Console in the General section. Select properties and click on incoming filter click new and add every other vlan with its ip address range as destination network except the one you are currently configuring of course


1

I very strongly suspect that the problem is this line in the qemu host's iptables -t nat -L -n -v: 76 6384 MASQUERADE all -- * * 10.10.15.0/24 !10.10.15.0/24 This is causing original (ie, not return-half) traffic from hadoop2 to driver to be NATted to 10.10.15.1. You could test this hypothesis by exempting just the traffic ...


1

An Elastic IP address is a property of network interfaces. That is, it's bound by VPC to the elastic network interface attached to your instance. Your instance's IP stack is not aware of the Elastic IP address. An Elastic IP address is accessed through the Internet gateway of a VPC. The Internet Gateway VPC object is the logical entity that does ...


1

I'd be surprised if you need a static route on the RRAS server for 192.168.101.0/24 at all, as it is a "directly connected" network - the RRAS server should know how to get to that network without a static route configured. In any event, setting the gateway for 192.168.101.0/24 as the RRAS server's IP on that network is functional, as you have discovered ...



Only top voted, non community-wiki answers of a minimum length are eligible