[ovs-discuss] 回复：discuss Digest, Vol 149, Issue 16

Thu, 11 Nov 2021 21:15:51 -0800

hi

发自我的华为手机


-------- 原始邮件 --------
发件人： [email protected]
日期： 2021年11月12日周五 半夜12:30
收件人： [email protected]
主 题： discuss Digest, Vol 149, Issue 16
Send discuss mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://mail.openvswitch.org/mailman/listinfo/ovs-discuss or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of discuss digest..." Today's Topics: 1. Re: question regarding utilities/nlmon.c tool (Gregory Rose) 2. Ovs ipv6 forwarding not working (Salman Khalid) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Nov 2021 08:02:30 -0800 From: Gregory Rose To: Mohammad Heib Cc: [email protected] Subject: Re: [ovs-discuss] question regarding utilities/nlmon.c tool Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed On 11/11/2021 12:01 AM, Mohammad Heib wrote: > Hi Gregory, > Thank you for the quick response :), > i have already implemented a basic TC Netlink monitor that is based on > nlmon code and it partially works > with some missing pieces, and waiting to hear from you if that ok to rely > on nlmon code. > > Thanks, > Mohammad Hi Mohammed, The nlmon tool should be reliable for what it decodes. It's just that it might not decode everything you want to see. But if it's helping out then I think you can trust it. - Greg > > On Wed, Nov 10, 2021 at 12:15 AM Gregory Rose wrote: > >> >> >> On 11/9/2021 8:05 AM, Mohammad Heib wrote: >>> hi folks, >>> i was looking for a way to monitor OVS TC Netlink messages that OVS sends >>> to TC when HW offloads are on (mostly for testing HWOL over non-supported >>> HW offload system ). >>> >>> as i understood, those Netlink's messages will be sent back from the >> kernel >>> to TC Netlink multicast group after the TC subsystem is finished >> processing >>> those requests, and the userspace process can capture them by listing to >>> the appropriate group. >>> >>> unfortunately, i didn't find any tool that give me the ability to capture >>> and parse (print) those TC Netlink messages. >>> so I started to implement my own tool but after a few more >> investigations I >>> found that nlmon already implement similar behavior for capturing Netlink >>> Link changes messages. >>> >>> so I was wondering if: >>> 1. I can convert nlmon code to be more generic and easier to add and >>> monitor new Netlink groups? >>> 2. can I add Netlink TC messages monitoring implementation to nlmon? >>> >>> if the answer to 2 was yes :) , >>> I have some dependencies that need to be included from linux/pkt_cls.h >>> which is a kernel header file and not sure if I can include it in nlmon ? >>> is that possible to include this file in nlmon.c? or is it ok to copy >> those >>> dependencies to a local file (maybe nlmon.h) especially that most of >> those >>> dependencies are enums and defines (e.g TCA_*/TCA_FLOWER_*)?. >> >> Hi Mohammed, >> >> I was looking into TC flower Netlink monitoring myself but haven't >> had a real chance to dig deeper into it. However, the nlmon tool you >> mentioned looks very interesting. I'll check it out and if I see an >> answer to question #2 I'll get back to you. >> >> Thanks, >> >> - Greg >> >> > ------------------------------ Message: 2 Date: Thu, 11 Nov 2021 13:59:08 +0000 From: Salman Khalid To: "[email protected]" Subject: [ovs-discuss] Ovs ipv6 forwarding not working Message-ID: Content-Type: text/plain; charset="utf-8" Ovs ipv6 forwarding not working Hello We have configured osv for ipv4 forwarding in the following way: sudo ovs-vsctl add-br br0 sudo ovs-vsctl add-port br0 ens192 sudo ovs-vsctl add-port br0 ens224 sudo ip link set br0 up then we add a route to the next device: sudo ip route add 1.2.0.0/16 via 1.2.2.2 dev br0 onlink for ipv6, we use: sudo ip -6 route add fd19:1234:5678:332::2 dev br0 onlink sudo ip -6 route add fd19:1234:5678::/48 via fd19:1234:5678:332::2 dev br0 onlink In case of ipv6 there?s no reply for ping or any other command. Is there any other configurations need to be done for ipv6? Complete setup: User(1) --------> ovs ------> User (2) All the traffic of user(1) is directed to go to osv which forwards it to user(2). IP forwarding is enabled as well: net.ipv4.ip_forward=1 net.ipv6.conf.all.forwarding=1 setup works for IPv4 but not for IPv6. -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ------------------------------ End of discuss Digest, Vol 149, Issue 16 **************************************** 
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to