[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66fee4c617dc073ce355addd19a9543cd1b344d8.camel@microchip.com>
Date: Tue, 13 Sep 2022 10:57:44 +0000
From: <Arun.Ramadoss@...rochip.com>
To: <vladimir.oltean@....com>
CC: <claudiu.manoil@....com>, <UNGLinuxDriver@...rochip.com>,
<alexandre.belloni@...tlin.com>, <vivien.didelot@...il.com>,
<andrew@...n.ch>, <idosch@...dia.com>, <linux@...pel-privat.de>,
<petrm@...dia.com>, <f.fainelli@...il.com>, <hauke@...ke-m.de>,
<martin.blumenstingl@...glemail.com>, <xiaoliang.yang_1@....com>,
<kuba@...nel.org>, <pabeni@...hat.com>, <edumazet@...gle.com>,
<netdev@...r.kernel.org>, <Woojung.Huh@...rochip.com>,
<davem@...emloft.net>
Subject: Re: [RFC PATCH net-next 3/3] net: dsa: never skip VLAN configuration
Hi Vladimir,
Thanks for reply.
On Mon, 2022-09-12 at 15:42 +0000, Vladimir Oltean wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Mon, Sep 12, 2022 at 03:30:18PM +0000, Arun.Ramadoss@...rochip.com
> wrote:
> > On Tue, 2022-07-26 at 17:21 +0000, Vladimir Oltean wrote:
> > > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > > know the content is safe
> >
> > Hi Vladimir,
> > I am trying to bringup the kselftest for bridge_vlan_aware.sh, in
> > that
> > I am facing problem during the ping test and all the tests are
> > failing.
> >
> > #ip vrf exec vlan1 ping 192.0.2.2
> > Cannot open network namespace: No such file or directory
> > Failed to get name of network namespace: No such file or directory
> >
> > Is there any configurations need to be enabled in the linux kernel,
> > can
> > you suggest/help me out in resolving it.
> >
> > --
> > Arun
>
> Yes, quite a few, in fact.
> Note that I'm not quite sure why it says "cannot open network
> namespace"
> when the command accesses a VRF instead.
>
> Try these:
>
> CONFIG_IP_ADVANCED_ROUTER=y
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_NET_L3_MASTER_DEV=y
> CONFIG_IPV6_MULTIPLE_TABLES=y
> CONFIG_NET_VRF=y
> CONFIG_BPF_SYSCALL=y
> CONFIG_CGROUP_BPF=y
In addition to above config, I had set CONFIG_NAMESPACES=y, then the
above error message disappered.
But the ping is not successful.
If I change the setup like
Linux laptop 1 --> DUT1 (Lan2) --> DUT1 (Lan3) --> Linux laptop 2
then ping is successful.
If I use the standard kselftest setup
lan1 --> lan2 --> lan3 --> lan4, ping is not success.
I went through the comments given in this thread to bring up ping for
openwrt, is that applicable to kselftest also.
ip netns add ns0
ip link set lan2 netns ns0
ip -n ns0 link set lan2 up
ip -n ns0 addr add 192.168.2.2/24 dev lan2
ip netns exec ns0 tcpdump -i lan2 -e -n ping 192.168.2.2
I am struck with the ping test bringup. It would be helpful, if you can
give some suggestion to bring it up.
Powered by blists - more mailing lists