Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[mininet-discuss] Custom topology - Ping: network is unreachable

mehmet fatih Aktaş mfatihaktas at gmail.com
Thu Jan 29 07:25:41 PST 2015


Hi Felipe,

I am not sure, but you can try to add these lines to your code:
h1.setDefaultRoute(intf='h1-eth0')
h2.setDefaultRoute(intf='h2-eth0')
h3.setDefaultRoute(intf='h3-eth0')

Mehmet

On Thu, Jan 29, 2015 at 9:07 AM, Felipe Alencar <contato at felipealencar.net>
wrote:

> Hi Chiara, first thanks for your time in helping me with this.
>
> Now, my Mininet topology is managed by a POX controller running a
> l2_switching module enabled. Is it enough?
>
> Em quinta-feira, 29 de janeiro de 2015, Chiara Contoli <
> chiara.contoli at gmail.com> escreveu:
>
> Hi Felipe and Mininet community,
>> would you mind provide more details, for example, are you using a custom
>> controller or the default controller?
>>
>> h1 and h2 are connected to the same network, that's why they're able to
>> reach each others; h3 is connected to another network, so if you want to
>> reach h3 from h1 or h2, you need a router; hosts should have a default
>> gateway, or specific entries in the routing table, so that they are able to
>> reach hosts in other networks.
>>
>> Anyway, in my opinion there are different approach with which you are
>> able to reach your goal.
>>
>> Best regards,
>>
>> Chiara
>> Il giorno 29/gen/2015, alle ore 02:43, Felipe Alencar ha scritto:
>>
>> Hi everyone,
>>
>> I'm trying to implement the following custom topology:
>>
>>                +------------+
>>             +--+controller c+--+
>>             |  +------------+  |
>>             |                  |
>>       +-----+---+        +-----+---+
>>    +--+switch s1+--+-----+switch s2+----+
>>    |  +---------+--+     +---------+    |
>>    |               |                    |
>> +--+-----+   +-----+--+           +-----+-----+
>> | host h1|   |host h2 |           | host h3   |
>> |10.0.0.1|   |10.0.0.2|           |192.168.1.1|
>> +--------+   +--------+           +-----------+
>>
>>
>> But I don't understand why the host h1 can't ping host h3 with the
>> defined IPs:
>>
>> mininet> h1 ping h3
>> connect: Network is unreachable
>>
>> However, if I set host h3 to 10.0.1.2:
>>
>> mininet> h1 ping h3
>> PING 10.0.1.2 (10.0.1.2) 56(84) bytes of data.
>> 64 bytes from 10.0.1.2: icmp_req=1 ttl=64 time=22.1 ms
>> 64 bytes from 10.0.1.2: icmp_req=2 ttl=64 time=0.256 ms
>> 64 bytes from 10.0.1.2: icmp_req=3 ttl=64 time=0.063 ms
>>
>> Someone could help me in it? Thank you guys!
>>
>> --
>> Felipe *A. *Lopes
>> Master's Candidate in Computer Science at the Informatics Center of
>> Federal University of Pernambuco (UFPE)
>> BSc in Information Systems at the Federal Institute of Alagoas (IFAL)
>>
>> (82) 9992-0023
>> http://felipealencar.net <http://www.felipealencar.net/>
>> http://lattes.cnpq.br/6490167896355223
>>  _______________________________________________
>> mininet-discuss mailing list
>> mininet-discuss at lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/mininet-discuss
>>
>>
>>
>
> --
> Felipe *A. *Lopes
> Master's Candidate in Computer Science at the Informatics Center of
> Federal University of Pernambuco (UFPE)
> BSc in Information Systems at the Federal Institute of Alagoas (IFAL)
>
> (82) 9992-0023
> http://felipealencar.net <http://www.felipealencar.net/>
> http://lattes.cnpq.br/6490167896355223
>
>
> _______________________________________________
> mininet-discuss mailing list
> mininet-discuss at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/mininet-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/mininet-discuss/attachments/20150129/de7059f8/attachment.html>


More information about the mininet-discuss mailing list