Hi Rami,
Thanks for all the help and sorry for late reply. I don't have the kernel .config of current build (its very difficult to get it) but I have .config of earlier build where I see :
# CONFIG_VETH is not set
My confusion is can these two o/p come concurrently:
1. # CONFIG_VETH is not set
2. root@Krishna:~# modprobe -r veth
modprobe: FATAL: Module veth is builtin.
Pls help me here in my understanding.
Also
root@krishna:~# ip -V
ip utility, iproute2-ss150706
And I don't have any man page help here.
I am using private customized distro for this.
BR/Krish
On Wed, Dec 7, 2016 at 12:39 AM, Rami Rosen <roszenrami@xxxxxxxxx> wrote:
Hi Er,
First, the veth modules should be in your kernel, as it does exist in 3.14:
On Wed, Dec 7, 2016 at 12:39 AM, Rami Rosen <roszenrami@xxxxxxxxx> wrote:
Hi Er,
First, the veth modules should be in your kernel, as it does exist in 3.14:
http://lxr.free-electrons.com/source/drivers/net/veth.c?v=3. 14
It could be that the iprotue1 package you have does not support veth.
What does the version of iproute2 you have on your machine ? what is
the output of "ip -V"?
Also do you have man page of "ip link" ? and in case you have, please
run "man ip link" and post here what you see in the "TYPE :="
section, you have veth,
Also, assuming you have access to the source tree where the kernel was
built, what do you get when running, from the root of this tree:
more .config | grep VETH
And finally - which distro is running on this device ?
Regards,
Rami Rosen
http://ramirose.wix.com/ramirosen
On 6 December 2016 at 18:25, Er Krishna <erkrishna@xxxxxxxxx> wrote:
> Hi Rami,
>
> Thanks, some how I am able to manage all the details you asked :
>
> root@krishna:~# lsmod | grep veth
> root@krishna:~#
> root@krishna:~#
> root@krishna:~# uname -a
> Linux <some name> 3.14.55-<some name> #1 SMP PREEMPT i686 GNU/Linux
> root@krishna:~#
> root@krishna:~#
> root@krishna:~# modprobe -r veth
> modprobe: FATAL: Module veth is builtin.
> root@krishna:~#
>
> Any suggestion from your end to enable this is most welcome.
>
> BR/Krish
>
> On Tue, Dec 6, 2016 at 9:18 PM, Er Krishna <erkrishna@xxxxxxxxx> wrote:
>>
>> Thanks Rami for all the help. Yes lsmod shows that veth is not there.
>> Perhaps the kernel has not been compiled with config_veth option enable in
>> .config. Exact kernel version I will let you know tomorrow but most of the
>> chances its 4.* kernel. Its customized kernel I got from different team,
>> they have build it via yocto and I had to setup one network topology on it.
>>
>> BR/Krish
>>
>> On Tue, Dec 6, 2016 at 8:18 PM, Rami Rosen <roszenrami@xxxxxxxxx> wrote:
>>>
>>> Hi Eri,
>>> The driver is the veth driver, but it should be loaded automatically
>>> when running this
>>> command.
>>>
>>> What do you get when running:
>>>
>>> modprobe veth
>>>
>>> And what do you have when running
>>> lsmod | grep veth ?
>>>
>>> Which kernel are you working with ? can you paste the output of
>>> "uname -a"? is it a kernel you built from source, or a kernel which is
>>> part of a distro?
>>>
>>> Regards,
>>> Rami Rosen
>>> http://ramirose.wix.com/ramirosen
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 6 December 2016 at 15:15, Er Krishna <erkrishna@xxxxxxxxx> wrote:
>>> > Hi All,
>>> >
>>> > Can some one pls let me know for below command to run on linux which
>>> > driver
>>> > and which package I need to install ? I see I have iproute package
>>> > installed
>>> > on my box, but still I am facing below error.
>>> >
>>> > root@krishna:~# ip link add ep1 type veth peer name ep2
>>> > RTNETLINK answers: Operation not supported
>>> >
>>> > BR/Krish
>>> >
>>> > _______________________________________________
>>> > Kernelnewbies mailing list
>>> > Kernelnewbies@kernelnewbies.org
>>> > https://lists.kernelnewbies.org/mailman/listinfo/ kernelnewbies
>>> >
>>
>>
>
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
