Well, that explains everything.
Thanks for the tip.

On Sat, 26 May 2012 10:48:59 +0300, Sergio Kviato writes:
> Hello,
>
> please show output of 'ovs-ofctl dump-flows br0'
>
> maybe you do not setup any flows?
>
> On May 25, 2012, at 9:40 PM, Volkan YAZICI wrote:
>
>> Hi!
>> 
>> After sleepless >48 hours, I might be missing something obvious
>> but I could not make an OVS 1.4.1 switch working on a particular
>> machine. Below are the diagnostics.
>> 
>> --8<---------------cut here---------------start------------->8---
>> $ lsmod | grep openv
>> openvswitch_mod        52448  1
>> 
>> $ ps afx | grep sbin/ovs
>> 1557 ?        Ss     0:00 /home/vyazici/usr-openvswitch/sbin/ovsdb-server 
>> --remote=punix:/home/vyazici/usr-openvswitch/var/run/openvswitch/db.sock 
>> --remote=db:Open_vSwitch,manager_options --detach
>> 
>> $ ~/usr-openvswitch/bin/ovs-vsctl show
>> c69614a4-5a84-4f85-abe2-d1228614a592
>>    Bridge "br0"
>>        fail_mode: standalone
>>        Port "eth1"
>>            Interface "eth1"
>>        Port "br0"
>>            Interface "br0"
>>                type: internal
>>        Port "eth3"
>>            Interface "eth3"
>>        Port "eth2"
>>            Interface "eth2"
>> 
>> $ sudo ~/usr-openvswitch/sbin/ovs-vswitchd
>> May 25 
>> 21:42:21|00001|reconnect|INFO|unix:/home/vyazici/usr-openvswitch/var/run/openvswitch/db.sock:
>>  connecting...
>> May 25 
>> 21:42:21|00002|reconnect|INFO|unix:/home/vyazici/usr-openvswitch/var/run/openvswitch/db.sock:
>>  connected
>> May 25 21:42:21|00003|bridge|INFO|created port eth1 on bridge br0
>> May 25 21:42:21|00004|bridge|INFO|created port eth2 on bridge br0
>> May 25 21:42:21|00005|bridge|INFO|created port eth3 on bridge br0
>> May 25 21:42:21|00006|bridge|INFO|created port br0 on bridge br0
>> May 25 21:42:21|00007|ofproto|INFO|using datapath ID 0000002320c75427
>> May 25 21:42:21|00008|ofproto|INFO|datapath ID changed to 0000000000000001
>> 
>> $ sudo ethtool eth1
>> Settings for eth1:
>>        Supported ports: [ TP MII ]
>>        Supported link modes:   10baseT/Half 10baseT/Full
>>                                100baseT/Half 100baseT/Full
>>                                1000baseT/Half 1000baseT/Full
>>        Supports auto-negotiation: Yes
>>        Advertised link modes:  10baseT/Half 10baseT/Full
>>                                100baseT/Half 100baseT/Full
>>                                1000baseT/Half 1000baseT/Full
>>        Advertised pause frame use: No
>>        Advertised auto-negotiation: Yes
>>        Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>                                             100baseT/Half 100baseT/Full
>>        Link partner advertised pause frame use: No
>>        Link partner advertised auto-negotiation: Yes
>>        Speed: 100Mb/s
>>        Duplex: Full
>>        Port: MII
>>        PHYAD: 0
>>        Transceiver: internal
>>        Auto-negotiation: on
>>        Supports Wake-on: pumbg
>>        Wake-on: g
>>        Current message level: 0x00000033 (51)
>>        Link detected: yes
>> 
>> $ sudo ethtool eth2
>> Settings for eth2:
>>        Supported ports: [ TP MII ]
>>        Supported link modes:   10baseT/Half 10baseT/Full
>>                                100baseT/Half 100baseT/Full
>>                                1000baseT/Half 1000baseT/Full
>>        Supports auto-negotiation: Yes
>>        Advertised link modes:  10baseT/Half 10baseT/Full
>>                                100baseT/Half 100baseT/Full
>>                                1000baseT/Half 1000baseT/Full
>>        Advertised pause frame use: No
>>        Advertised auto-negotiation: Yes
>>        Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>                                             100baseT/Half 100baseT/Full
>>        Link partner advertised pause frame use: No
>>        Link partner advertised auto-negotiation: Yes
>>        Speed: 100Mb/s
>>        Duplex: Full
>>        Port: MII
>>        PHYAD: 0
>>        Transceiver: internal
>>        Auto-negotiation: on
>>        Supports Wake-on: pumbg
>>        Wake-on: g
>>        Current message level: 0x00000033 (51)
>>        Link detected: yes
>> --8<---------------cut here---------------end--------------->8---
>> 
>> On eth1 and eth2, there are two notebooks connected to the switch
>> machine. And their network interfaces are set to 192.168.4.1/24
>> and 192.168.4.2/24. Further, connected NIC lights on the switch
>> machine are green. But notebooks somehow cannot ping each other.
>> What might I be missing?
>> 
>> 
>> Best.
>> _______________________________________________
>> discuss mailing list
>> [email protected]
>> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to