many VNIC's (Virtual Network card) on one physical NIC
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
many VNIC's (Virtual Network card) on one physical NIC
Please help me to find module for VNIC.
About year ago I downloaded one module, which help me generate many virtual network interfaces on one physical interface on Linux with different IP and MAC addresses and bridged with the physical interface.
I forget the name, and now I’m trying to find it, but have not success…. I looked all available search engines and forums…
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
Do you mean Aliasing IP? eth0:0
If so then it is usually normally configured into the kernel. It is the TCPIP Networking item or called ' config_inet ' from a kernel config file.
No, with bridge_utils you can create virtual interface, and connect to it many interfaces, but each interface only once, it means that you can't create many virtual interfaces based on one physical interface.
My problem is having many virtual cards (with differenet MAC addresses, and bridged with physical network card) on one physical card.
Yeah I want something like a "tap" interface, but "netkit" is not enough for me, because "tap" interface created with "netkit" not working like a virtual network card with different MAC address.
It is just show different MAC address on created “tap” interface, but when I'm connecting with that virtual interface or when I'm sending some request to ip address of that virtual interface, in arp table I can see only MAC address of real interface.
It means that it only show that my new virtual interface has different MAC address, but in real it communicates with MAC address of real network card.
Wow, it's been a long time. Somehow I completely forgot about this thread. My apologies.
Anyway, have you found a solution yet? One thing that I found interesting was linux's 802.1q implementation, which allows VLANs to exist for actual physical interfaces. You need to have a kernel that supports it (either built-in or module), and you need the vconfig program.
Here's what I did (it seemed to work for me):
Code:
# ip link show
1: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:61:02:31:7f brd ff:ff:ff:ff:ff:ff
2: wan0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:61:02:31:80 brd ff:ff:ff:ff:ff:ff
3: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
# vconfig add eth0 1
# ip link show
1: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:61:02:31:7f brd ff:ff:ff:ff:ff:ff
2: wan0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:61:02:31:80 brd ff:ff:ff:ff:ff:ff
3: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
4: eth0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:04:61:02:31:7f brd ff:ff:ff:ff:ff:ff
# ip link set dev eth0.1 address 00:04:61:02:31:7e
# ip addr add 192.168.2.1/24 dev eth0.1
# ip addr show
1: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:61:02:31:7f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0
2: wan0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:61:02:31:80 brd ff:ff:ff:ff:ff:ff
inet 64.179.4.146/24 brd 255.255.255.255 scope global wan0
3: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
4: eth0.1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noop
link/ether 00:04:61:02:31:7e brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 scope global eth0.1
Is this what you needed?
EDIT: changed public IP address to protect my identity (it doesn't really matter, but I substituted one of LQ's for mine)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.