Bridge network and bond interface taking same ip - keep-alive

I have a HA (High available) openstack controller with a Newton version. Openstack controller OAM management network uses bond0 interface with the network ip address 172.28.252.198 (primary). I also have keepalived configuration in the system and my controller servers are using 172.28.252.200 as VIP address (as secondary). I am using bridge network system. After creating provider network (which is the same network with OAM: 172.28.252.192/26) on dashboard, the bridge interface brq88cc4ef1-0f is created on the controller.
I observed that the ip address <172.28.250.198> is assigned on both bridge(brq88cc4ef1-0f) and a bond0 interface. In this case i cannot access to my controller server. I think the problem is related with ip conflict on the interface. Is it possible to use openstack OAM management network and provider network in a same subnet? Could you please help me about it. How can i make the system create network only on a single interface?
31: brq88cc4ef1-0f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 1e:bb:ff:aa:90:11 brd ff:ff:ff:ff:ff:ff
inet 172.28.252.198/26 brd 172.28.250.255 scope global brq88cc4ef1-0f
valid_lft forever preferred_lft forever
inet 172.28.252.200/32 brd 172.28.250.200 scope global brq88cc4ef1-0f
valid_lft forever preferred_lft forever
36: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether a0:36:9f:54:59:72 brd ff:ff:ff:ff:ff:ff
inet 172.28.252.198/26 brd 172.28.250.255 scope global bond0
valid_lft forever preferred_lft forever

Related

Unable to ping from GNS3 topology to Physical Adapter

I'm trying to setup a connection b/w GNS3 Router and Local PC. Following are the steps done so far in GNS3:-
1. setup a router interface, e0/0/ = 192.168.1.1 255.255.255.0
2. created a cloud loopback adapter, interface, and assigned IP = 192.168.1.5 255.255.255.0
(Note: loopback adapter has been created as Mictosoft KM-Test loopback on my PC. and same interface has been added to cloud in GNS3 which is then connected to Router interface, e0/0)
When I tried ping from my PC to GNS3 R, arp entries get created in Router (running on GNS3 topology). See below:
RTR#sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 192.168.1.1 - aabb.cc00.0200 ARPA Ethernet0/0
Internet 192.168.1.5 134 0200.4c4f.4f50 ARPA Ethernet0/0
But ICMP isn't successful on Router (See below) :-
RTR#ping 192.168.1.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.3, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Can anyone help here pls ??
Try setting the IP address of the KM-Test adapter to an address outside your home network. Such as 10.0.0.1/24. Attach your cloud to the network adapter and then create persistent static routes by opening a command prompt as administrator and entering the command.
route -p add [Destination] mask [Subnet Mask] [Gateway(KM-Test)]
Note that any additional network you create within GNS3 will need a static route so that windows knows to send your packets through the KM-Test rather than your home network gateway.

Database interface with RYU controller

Is it possible to interface a database containing IP address with RYU controller where the incoming packet IP address is compared and a result is sent to the controller as true or false?
you can use a Python package called NetworkX which will store the network topology as a graph and store all of the devices as nodes in that graph then you can get any information about the network such as a host IP.
https://networkx.github.io/

How to make IBM Kitura Framework listen on IPv6 port?

I made a web application using IBM Kitura Framework, but the service only listens on IPv4? How to make it listen on both IPv4 and IPv6?
The source code which adds a HTTP server is as follow
Kitura.addHTTPServer(onPort: 8090, with: router)
And I run lsof -i:8090 on my Ubuntu Server, the result is
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ServerNew 1731 root 4u IPv4 24114 0t0 TCP *:8090 (LISTEN)
It shows that the 8090 port only listens on IPv4.
I'm the Business Development Manager for Kitura in IBM. Kitura 2 doesn't yet support IPv6. It's supported in Bluesocket and the underlying frameworks, but has not yet been implemented in the socket.create() api. This is in the backlog and will be coming in the not too distant future.

ARP : What Mac ARP does request when a Host want to communicate to Host in different Network

Please Clarify my doubt in ARP. In the below Topology,.
Looking for better understanding, how ARP works when Hosts are connected between default Gateways .
Host A(10.10.10.1)-----Switch-----(10.10.10.2)Router(20.20.20.2)--------HostB
When a Host want to communicate to Host B , does hostA send an ARP request for Destination IP (20.20.20.1) or to Default Gateway (10.10.10.2) .
If it send ARP for HOST B mean, Host A identifies Host B is in different network, it will send the Packet only to the Configured Default Gateway , so will it request for Default Gateway Mac address
Host B mac will not be learnt by Host A by any cost, So does Host A will generate ARP request for each time?
Since a MAC address is only useful for a layer-2 domain which is bounded by a layer-3 device (router), a host will not ARP for a MAC address on a different subnet unless it has a misconfigured mask.
The host will ARP for the address of its configured gateway so that it can send the frame to the gateway, and the gateway will remove the layer-2 frame and try to forward the layer-3 packet to the port toward the end host. The router will then encapsulate the layer-3 packet with a new layer-2 frame (possibly using ARP if the nest hop isn't in its ARP cache) for the next link.

Raw Sockets - Internet Protocol Layers

I have been working with Raw Berkeley Sockets in C, which allow the programmer to access Layer 2 (IP Headers) of the Internet Protocol Suite. I would like to know how the raw sockets handle transport on Layer 1 (Link Layer), specifically with regard to wireless local area networks.
For example, how does the socket know which network interface (eth0 or wlan0) to send the packet to?
If I am behind a wireless router, should I still fill the IP Source Address of my IP Header with my LAN address (192.168.1.1), or with the internet address (74.125.226.68) of my router?
If I do fill the IP Source address with my LAN address (192.168.1.1), does the IP Header get changed when it goes through the router, or does it stay that way, so that the receiving end of the packet attempts to send the response to a local host on its network?
I would appreciate any insights in this area.
For example, how does the socket know which network interface (eth0 or wlan0) to send the packet to?
You can use the socket option SO_BINDTODEVICE to bind your socket to a specific interface. Otherwise, the operating system chooses one.
If I am behind a wireless router, should I still fill the IP Source Address of my IP Header with my LAN address (192.168.1.1), or with the internet address (74.125.226.68) of my router?
You should use your LAN address. The router is responsible to take care of NAT (network address translation) if necessary.
If I do fill the IP Source address with my LAN address (192.168.1.1), does the IP Header get changed when it goes through the router, or does it stay that way, so that the receiving end of the packet attempts to send the response to a local host on its network?
If NAT is enabled at the router, the source address is changed to reflect the router's external address. Otherwise, your packages are likely to be dropped by routers or firewalls, because your source address is invalid in their context.

Resources