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] Mininet hosts with multiple interfaces (Re: Miniedit UI 2.0.0.4)

Phiho Hoang hohoangphi at gmail.com
Wed Aug 28 22:53:12 PDT 2013


Dear List,

> 1.  h2 is not a switch, so traffic is not going to pass through it.

unless h2 runs 'Click' ?-)

> 2. By default, mininet chooses a single interface on each host and
assigns an IP address.  If a host has multiple interfaces, then mininet
will only auto assign an interface to one of them.

Is this a feature of MiniEdit or MiniNet?

When a host is added it is not known how many interfaces will be needed on
that host until the links are created?
Should the host's interfaces and IP's be assigned when the links are
created?

Currently, h2-eth1 has 'inet6 addr' but no 'inet addr':

mininet> h2 ifconfig
h2-eth0   Link encap:Ethernet  HWaddr 1a:c4:82:a3:b6:2e
          inet addr:10.0.0.2  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::18c4:82ff:fea3:b62e/64 Scope:Link
...
h2-eth1   Link encap:Ethernet  HWaddr 4a:db:04:7f:39:16
          inet6 addr: fe80::48db:4ff:fe7f:3916/64 Scope:Link
...

Can the extra interfaces be configured manually?

I tried

mininet> h2 ifconfig h2-eth1 10.0.0.20
mininet> h2 ifconfig
...
h2-eth1   Link encap:Ethernet  HWaddr 4a:db:04:7f:39:16
          inet addr:10.0.0.20  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::48db:4ff:fe7f:3916/64 Scope:Link
...

So, now h2-eth1 has proper 'inet addr', but h1 still cannot ping h2.

What do I need to do so that h1 can ping h2?
Restarting some thing?

Thank you for your time and your help.

Regards,

PhiHo




On Wed, Aug 28, 2013 at 9:41 PM, Gregory Gee <gee.developer at gmail.com>wrote:

>
>   Well, there are 2 reason that this won't work.
>
> 1.  h2 is not a switch, so traffic is not going to pass through it.
>
> 2. By default, mininet chooses a single interface on each host and assigns
> an IP address.  If a host has multiple interfaces, then mininet will only
> auto assign an interface to one of them.
>
>   To do test, hosts should be on the edge of the network and not a node
> that traffic is supposed to pass though.
>
> Greg
>
>
> On 28/08/2013 2:48 PM, Phiho Hoang wrote:
>
> Hi Greg,
>
>  Thank you for the new release.
>
>  I tried a simple topology with 3 hosts and 2 switches:
>
>  mininet> nodes
> available nodes are:
> c0 h2 h3 h1 s2 s1
> mininet> net
> c0
> s2 lo:  s2-eth1:h2-eth0 s2-eth2:h3-eth0
> s1 lo:  s1-eth1:h1-eth0 s1-eth2:h2-eth1
> h2 h2-eth0:s2-eth1 h2-eth1:s1-eth2
> h3 h3-eth0:s2-eth2
> h1 h1-eth0:s1-eth1
>
>  I don't know why h2 can ping h3 but it cannot ping h1:
>
>  mininet> h2 ping -c1 h3
> PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
> 64 bytes from 10.0.0.3: icmp_req=1 ttl=64 time=5.67 ms
>
>  --- 10.0.0.3 ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 5.675/5.675/5.675/0.000 ms
> mininet> h2 ping -c1 h1
> PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
> From 10.0.0.2 icmp_seq=1 Destination Host Unreachable
>
>  --- 10.0.0.1 ping statistics ---
> 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
>
>  mininet>
>
>  Please find attached a screen shot with MiniEdit and MiniNet
>
>  Cheers,
>
>  PhiHo
>
>
>
> On Thu, Aug 22, 2013 at 9:14 PM, Gregory Gee <gee.developer at gmail.com>wrote:
>
>>  Another small update visibly, but laying the ground work for bigger
>> stuff.
>>
>>    - Add more link opts (max_queue_size, loss)
>>    - Update Load, Save and Export with above additions
>>    - Started adding right click menu on switch, host and link
>>    - Default terminal type in preferences
>>    - Fix small bug in Export Topology
>>
>> Pick it up at http://gregorygee.wordpress.com/ .
>>
>> Also, from previous question about wanted features, I have come up with
>> the following list of features I'm going to try and add in upcoming
>> releases.
>>
>> TODO:
>>
>>    - add host cpu opts
>>       - cpu: desired overall system CPU fraction
>>       - cores: (real) core(s) this host can run on
>>    - multiple controllers
>>    - connect switch to host ethernet (like the example hwintf.py)
>>    - create tunnel endpoint on switch. This might be a stretch for
>>    Miniedit and should probably have direct support within mininet.
>>
>>  GRE Ethernet tunnels
>>      ovs-vsctl add-port s1 s1-gre1 -- set interface s1-gre1 type=gre
>> options:remote_ip=192.168.10.10 options:key=1
>>      ovs-vsctl add-port s1 s1-gre2 -- set interface s1-gre2 type=gre
>> options:remote_ip=192.168.10.11 options:key=2
>>  VXLAN tunnels (if using OpenVSwitch 1.10)
>>      ovs-vsctl add-port s1 s1-vx1 -- set interface s1-vx1 type=vxlan
>> options:remote_ip=192.168.1.13
>>
>>    - add tunnels between switches in Mininet
>>    - more link options
>>       - jitter
>>       - speedup
>>       - Bandwidth Limiting
>>          - use_hfsc or use_tbf/latency_ms or none
>>          - enable_ecn or enable_red or none
>>        - Connect switch to external minitoring software (NetFlow and
>>    SFlow clients)
>>
>>
>>
>> _______________________________________________
>> 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/20130829/8a55f421/attachment-0001.html>


More information about the mininet-discuss mailing list