Debian Configuration :: Setup Multiple Mac Address Over Single Ethernet Interface?
Jul 23, 2015
I want to configure multiple virtual ethernet interfaces over a single physical ethernet interface (eth0) and for each virtual interface the MAC address must be unique and the IP address must be Static.Finally all the virtual interfaces must be able to communicate both internally and externally and the traffic should be captured using wireshark.
I need to have such kind of setup to communicate devices individually using one physical ethernet device.
Because I was fiddling with few kernel modules like MACVLAN and MACVTAP and successfully enabled those modules and rebuild kernel. Using macvlan and macvtap I can configure virtual interfaces with unique mac address and static IPs but while capturing packets using wireshark interfaces behave weirdly.
For example say on HOST machine I have 1 physical interface and created 3 virtual interfaces as shown below.
First from above interfaces I started pinging eth0 internally from host machine in which it worked as usually.
Second I did same externally from other machine which is connected to the same network of Host machine, and this did work as usually.
Third I pinged first virtual interface veth0 both internally and externally and this also works and after that I did check source and destination MAC address using wireshark tool-where both showed up there respective MAC address.
Now triggers the issue, where I pinged second virtual interface same like I did for first one, but this time ping was success and where as in wireshark tool the MAC address for veth0 is picked by veth1. This is where I got stuck and this issue happened for all the remaining virtual interfaces.
I couldn't see any virtual interface showing their respective MAC address, as of the remaining except the first virtual interface has been picking the first veth0 mac address.
I'm renting a server which comes with 5 IP addresses, but only one network device. From what I can understand I'm able to create aliases by adding entries to /etc/networks/interfaces, I haven't tried I'm in the planning stages. Hypothetically, 192.168.22.30 is my primary IP and I want to set eth0:1 to have 192.168.22.31, and then after that I want to create a virtual machine (using kvm/qemu) that is able to communicate bidirectionally to the internet over eth0:1, and leave eth0 strictly for administrating (not for VM traffic).
The qemu guides I'm finding seem to assume that I want to use TAP or VDE, what I want to use is a sub-ip/alias. One guide I saw had me eliminate everything from eth0 and put it under br0. That would leave me unable to ssh into my server (and unable to administrate). Is there a way I can do something along the lines of: qemu [options] -net [option] -netdev=eth0:1 ?
I am having some troubles using iptable rules on two Servers that act as Gateways pointed to one backend server with only one interface.
To be more exact, i have 3 Servers, 2 of those have a public and a private interface, with different public ips but common private interface ( they connect to the same switch ), the last one only has 1 private interface and is connected to that same switch.
Those 2 servers also act as a gateway and a firewall for the private network.
My problem is that i cannot seem able to route traffic from both of those to the third one and back to the same public ip that the request came from ( effectivly using two gateways on the machine with only one interface ).
As a testing scenario i am using ferm for applying iptable rules that forward ssh traffic ( for example ) to the backend server, and it works well when i do it with one gateway.
When i apply something like this in /etc/network/interfaces on the backend server though:
Even though forcing selection of an interface from the backend server ( like curl --interface ) seems to work well, meaning that the request to the curl appear to happen from the correct public ip, i can still only use one of the public ips to access the server with the ferm rules. Ideally i should be able to ssh to the backend server from both public ips using their ferm rules for forwarding traffic to the backend server.
I feel like i am missing some details on routing that should happen on the firewalls as the backend server seems to be able to use both gateways to access the internet and receive replies from it.
I am new to Debian. I am trying out the live cd but can't seem to find how to connect to the internet. My setup is Ethernet card and DSL modem, no routers, no wireless. How do I set this up?
What is the Linux command to clear IP address of an interface without bringing it down and/or restarting network services. Seems strange ifconfig is able to change IP address but has no option to clear it, or am I wrong?
EDIT:As simple as ifconfig eth0 0.0.0.0. They should have put it in the man
I now have 2 desktops running debian. I have virtual servers running in desktop 1, and I am hosting my photos using Gallery2. I have copied Gallery2 and the mysql over to desktop 2. I have entered port forward to desktop 1 using port 80 (using my router), and desktop 2 using port 1000. I can only access Gallery2 in desktop1. If I tried to access Gallery2 in desktop 2, I got re-directed to desktop1.
Questions:
1. Are home routers capable of port forward to more than one computers in a home network behind the firewall of the router? It is Belkin N+ router.
2. Can multiple virtual servers be setup in 2 desktops?
I recently installed Ubuntu Server 9.10 with the intent of using it as a platform for running a couple of Windows XP virtual machines along with Linux/Ubuntu.
I had no problems getting the server installed. Had no problems getting the network up and running so that I had access to both my internal network as well as external connectivity to the internet. Had no problems getting a VM installed and putting Windows XP inside of it. Had no problems setting up a bridge between the WinXP virtual machine and the physical ethernet card (eth0).
What Im having trouble with is figuring out how to bridge from multiple VMs AND Ubuntu natively through one physical ethernet card.
When I set up the bridge, it knocks out the static IP address of the ethernet card that was set up initially with Ubuntu when first installed before the VM was created and installed. Therefore, connectivity within Ubuntu natively is lost.
Similarly, am having trouble figuring out how the second VM (also going to be running WinXP) is going to get its connectivity since it doesnt seem to like me setting up 2 bridges to the same physical ethernet interface card.
I need all 3 machines to have static IP addresses and be visible/accessible from the external network for either web/mail/dns/etc servers on the Ubuntu side and for remote PC control functionality on the VM side.
I have tried setting up alias ethernet interfaces (eth0:1, eth0:2, eth0:3) with static addresses which work fine from native Ubuntu in presenting multiple IP addressees, but it seems that Im not permitted to bridge to these alias interfaces.
I need to share internet connection through wired-ethernet with another computer which does not have a wifi card.
However, no eth* interface shows up on ifconfig. Even more surprinsingly, neither lshw nor lspci shows anything related to wired ethernet controller/adapter:
Why isn't my laptop's wired ethernet not showing? I have a Toshiba Satellite PSAG8U-04001W.
The installation of Debian wasn't originally on this system: it was on an older laptop whose motherboard fried, so I rescued the hard drive as well as the Debian installation. However, I doubt this should have anything to do with lspci not even detecting the wired eth controller.
My laptop was working fine on wireless till the userinterface changed and it defaulted to ethernet and now it won't let me go back on wireless How do i disable ethernet?
I have question about the UNIX sockets. my goal is to connect multiple sockets from a single client to a single server and keep them open...I'm not sure if that is possible to create or not. Do you have any suggestion or an example of code?
Recently I was forced to "downgrade" my AMD64 Squeeze installation to 32 bit Squeeze. The installation was (obviously) made from scratch. Everything else seems to be working fine, but there is only one cpu core out of four detected. On AMD64 kernel all four cores were functional. Now what?
$ uname -srv Linux 2.6.32-5-686 #1 SMP Mon Jun 13 04:13:06 UTC 2011 $ cat /etc/debian_version 6.0.2 $ cat /proc/cpuinfo
lspci reports 07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) 08:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) eth0 is picked up (light when I plug n the cable lights up). nothing for eth1.
other OSes on the same machine pick up both. My /etc/network/interfaces file looks like auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp iface eth1 inet static
[Code]...
For those who are interested, I have an adsl modem and a router is connected to the modem. eth1 is a connection to the modem. eth0 to the router.
I've got a Dell Optiplex Desktop here, the CPU is a Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz. The integrated ethernet here is from intel also, it's a 82579LM Gigabit Network Connection. This computer is running a Debian Squeeze 64bits, distrib sid, kernel 2.6.39-2-amd64.Well, here goes the story. I had a lot of trouble with the ethernet card, being very slow, and it just didn't work when i was using tftp. So I downloaded and compiled the latest driver available on Intel website. Currently with debian sid, the version for the driver ( e1000e ) is version: 1.3.10-k2. From Intel I got the version 1.3.17-NAPI.Alright, so I build it, and move the module manually to the right place, replacing the previous version at the same time ie :
So, which one should I trust ? Is there something I didn't do properly when installing the module ? Or maybe I just don't understand ethtool and modinfo enough.
Is is possible, via iptables or something similar, to bind a service running on a specific port to a specific interface? My case: I use a VPN service for privacy. I would like to have all traffic except ftp and ssh to run over tun0. Ports 21 and 22 will need to be accessible to the outside world (eth0) while the VPN is running.
I'm restoring an old TI Silent 700 terminal [URL] ... and have connected it to an RPi running the debian based Jessie release using a serial converter. After learning more than I wanted to about serial settings and support I now have it interfaced and communicating bidirectionally but have one last hurdle - proper support for a single case (uppercase only) terminal in agetty.
With the -U flag on it seems like the the login name is detected as needing conversion because lowercase login names work - but lower case passwords do not and once I get a bash prompt all input comes in as upper case. So the -U agetty flag only seems to apply to login name and is then forgotten (not passed on to login process or bash?) and various settings in stty like iuclc, xcase, iexten don't seem to work.
I'd really like to get this terminal working with native support but I'll also take a kludge of some kind (I've tried a tr pipe for example).
Here is what I think is the relevant portion of my systemd generator:
I'm running Debian Lenny. When I exit run level 1 (single user mode), the system automatically continues into run level 2. I have browsed the init scripts and have yet to determine how this "magic" is performed. I would be grateful if a local guru would point me to how the scripts automatically proceed into run level 2 when exiting run level 1
atheros-firmware and firmware-realtek are installed from repo.
ifconfig does not show the network devices:
ifconfig -a does show them, i ran the commands ifconfig eth1 up and ifconfig wlan1 up, which resulted in them showing when typing ifconfig, however both still are not working.
(ifconfig)Also eth1 is only showing an inet6 address not an inet/ipv4 address and wlan1 doesn't show any.
Checked the bios and noticed that network devices were enabled so i don't think its my bios.
Also ran a SystemRescueCd which i got from here: [URL] .... With this live cd, the networking was working.
i install devian squeeze with the netinstall iso, all work fine except for the auto-detect of my ethernet card.i have a mother asrock p4i45gv with an onboard ethernet card realtek rtl8139/810x family fast ethernet NIC.i try everithing, the ifconfig shows only lo, but ifconfig -a shows a eth0 any ideas?
Go to "/lib/modules/2.6.32-5-amd64/kernel/drivers/net/e1000e/" and delete the e1000e.ko-file
Then download [URL]
Take the newly downloaded e1000e.ko-file and move it to "/lib/modules/2.6.32-5-amd64/kernel/drivers/net/e1000e/"
And finally load the module with either: "# modprobe e1000e" or "# insmod e1000e".
You should now have a working ethernet connection.
If connection is lost on system restart try rmmod e1000e; modprobe e1000e
I've for the first time installed linux (debian) to my computer. And I have a problem with ethernet that I can't solve.
I have a Asus Sabertooth P67 motherboard with built in ethernet card, I cant find any drivers for linux, I've tried google, Asus support page etc, but can't anything that says it will work with my computer, just a alot of windows drivers.
where I can find the drivers? Or if there's another way to solve the problem. When installing Debian i could choose between different drivers but no one worked, I've also tried with my motherboard CD but there was just windows drivers...
I just updated my Squeeze install now the current kernel version is now 3.0.0-1-686-pae. I now no longer have any internet connection.I have tried the failsafe boots with no luck. I have tried the 2.6 kernels and have had no luck.I have tried to manually start the connections with no luck.I have booted off of a Squeeze Live CD and the connection works just fine.
After updating and subsequently restarting today, I can no longer bring up my wireless interface:
ifup wlan0 SIOCSIFFLAGS: Unknown error 132 Could not set interface 'wlan0' UP SIOCSIFFLAGS: Unknown error 132 SIOCSIFFLAGS: Unknown error 132 Failed to bring up wlan0
iwconfig lo no wireless extensions. eth0 no wireless extensions.
wlan0IEEE 802.11abg ESSID: off/any Mode: Managed Access Point: Not-AssociatedTx-Power=off Retry long limit:7RTS thr: offFragment thr:off Encryption key:off Power Management:off
Suppose I have both a hardwired and a wireless network connection active on the same system at the same time. Can I tell my browser which one to use? Can I tell other programs which one to use? Or do they choose for themselves> Or does some automatic system protocol select which one to use for them?
My laptop only has a 100Mbit ethernet port, so I bought two external USB gigabit ethernet dongles in the hope of getting faster ethernet speeds. I have never had trouble with Linux supporting ethernet before, but neither of these devices are working. One is an ASIX AX88179 (by TrendNet) and the other is a Realtek RT8153 (by Anker). When I plug these devices in, I get network devices called enx00e04ca82300 or enxd8eb97b61e4d (instead of eth0/eth1 as I would expect).
I can manually set an IP address with "ifconfig enx00e04ca82300 x.x.x.x up" and manually add a route and my network connection works at gigabit speeds. However, the long enx... network device name does not appear to be valid in some sense: tools like dhclient or iptraf or network-manager fail with messages like "no such device" (well, network-manager just hangs). I don't know if it's because the name is so long or because they are not fully registered inside the kernel.
I have vmware workstation installed, and it does some strange things with network devices (setting up bridges for everything). I have disabled its services and see the same behaviour. This looks like a kernel bug to me but it's possible it is a vmware issue. vmware works fine with my wireless and 100Mbit ethernet (eth0 and wlan0).
Realtek device Some dmesg for the Realtek device: Code: Select all[10264.619420] usb 4-3.1.1: reset SuperSpeed USB device number 4 using xhci_hcd [10264.634651] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c4221a00 [10264.634653] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c4221a48 [10264.634655] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c4221a90 [10264.647842] r8152 4-3.1.1:1.0 eth0: v1.06.0 (2014/03/03) [10264.647902] usbcore: registered new interface driver r8152 [10271.452198] IPv6: ADDRCONF(NETDEV_UP): enx00e04ca82300: link is not ready [10275.094334] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04ca82300: link becomes ready
The Realtek device often crashes after just a few gigabytes have been transferred, with dmesg like this:
Code: Select all[10485.761603] net_ratelimit: 10 callbacks suppressed [10485.761618] r8152 4-3.1.1:1.0 enx00e04ca82300: Tx status -71 [10488.694340] r8152 4-3.1.1:1.0 enx00e04ca82300: Tx status -71 [10488.711352] r8152 4-3.1.1:1.0 enx00e04ca82300: Tx status -71
[code]...
I have not investigated the ASIX device as much. However, my original 100Mbit ethernet has an ASIX chipset (AX88772) and that works perfectly. I have not observed the ASIX device crashing yet so I am using that for now (haven't used it for long yet though). But as before the device name appears to be invalid and I cannot run tools like dhclient. why two gigabit adapters with completely different chipsets would show up with long device names and support low-level stuff like ARP, ping, and static IPs, but fail with dhclient & network-manager? And the Realtek device seems to like crashing too.
I upgraded testing today on my intel laptop. During the upgrade I got the message that the new kernel would require additional firmware, see attached. Is the solution for this to install the driver from Realtek? [URL] If so, the instructions said to check if the driver was already installed, but what does the output below mean?
I have a debian-powered NAS (Buffalo LinkStation) and I want to configure the following behaviour: When ethernet (eth0) is plugged in, connect and get a static ip address (ie. 192.168.0.11) When a wireless usb-adapter (wlan0) is plugged in, connect to a wireless router (ie. "Ankkanet") get another static ip address (192.168.0.12)
My /etc/network/interfaces :
auto lo iface lo inet loopback auto eth0 iface eth0 inet static
[code]....
what could be causing wireless to disconnect when ethernet cable is unplugged?
