You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run minindn with the default topology, a pings c successfully. However, when c pings a, I see the following:
mininet> c ping a
connect: Network is unreachable
But when I use a's IP address, c can reach it:
mininet> c ping 1.0.0.5 -c 1
PING 1.0.0.5 (1.0.0.5) 56(84) bytes of data.
64 bytes from 1.0.0.5: icmp_seq=1 ttl=64 time=20.2 ms
--- 1.0.0.5 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 20.242/20.242/20.242/0.000 ms
Here is the ifconfig output of a and c:
mininet> a ifconfig
a-eth0 Link encap:Ethernet HWaddr 06:3e:95:aa:d7:da
inet addr:1.0.0.1 Bcast:1.0.0.3 Mask:255.255.255.252
inet6 addr: fe80::43e:95ff:feaa:d7da/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2644 (2.6 KB) TX bytes:2816 (2.8 KB)
This is affecting my work such that some nlsr updates do not reach other nodes. I'm guessing it has to do with DNS resolution, but I'm unable to find a way around it.
The text was updated successfully, but these errors were encountered:
So nodes are connected like c(c-eth0)----(a-eth1)a(a-eth0)----(b-eth0)b(b-eth1)---(d-eth0)d
a-eth0 and b-eth0 will have consecutive IPs and can reach each other. And if it is not the default interface (ex: a-eth0, you will need to use IPs). You might be able to get over this problem by using routes using the route command.
Hi again,
When I run minindn with the default topology, a pings c successfully. However, when c pings a, I see the following:
mininet> c ping a
connect: Network is unreachable
But when I use a's IP address, c can reach it:
mininet> c ping 1.0.0.5 -c 1
PING 1.0.0.5 (1.0.0.5) 56(84) bytes of data.
64 bytes from 1.0.0.5: icmp_seq=1 ttl=64 time=20.2 ms
--- 1.0.0.5 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 20.242/20.242/20.242/0.000 ms
Here is the ifconfig output of a and c:
mininet> a ifconfig
a-eth0 Link encap:Ethernet HWaddr 06:3e:95:aa:d7:da
inet addr:1.0.0.1 Bcast:1.0.0.3 Mask:255.255.255.252
inet6 addr: fe80::43e:95ff:feaa:d7da/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2644 (2.6 KB) TX bytes:2816 (2.8 KB)
a-eth1 Link encap:Ethernet HWaddr 8e:ad:ee:03:5e:34
inet addr:1.0.0.5 Bcast:1.0.0.7 Mask:255.255.255.252
inet6 addr: fe80::8cad:eeff:fe03:5e34/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3066 (3.0 KB) TX bytes:2878 (2.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:785 errors:0 dropped:0 overruns:0 frame:0
TX packets:785 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3282928 (3.2 MB) TX bytes:3282928 (3.2 MB)
mininet> c ifconfig
c-eth0 Link encap:Ethernet HWaddr b2:71:c0:dc:c5:bf
inet addr:1.0.0.6 Bcast:1.0.0.7 Mask:255.255.255.252
inet6 addr: fe80::b071:c0ff:fedc:c5bf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2878 (2.8 KB) TX bytes:3066 (3.0 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2062 errors:0 dropped:0 overruns:0 frame:0
TX packets:2062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3610736 (3.6 MB) TX bytes:3610736 (3.6 MB)
This is affecting my work such that some nlsr updates do not reach other nodes. I'm guessing it has to do with DNS resolution, but I'm unable to find a way around it.
The text was updated successfully, but these errors were encountered: