search for: eth10

Displaying 9 results from an estimated 9 matches for "eth10".

Did you mean: eth0
2005 Feb 11
0
SNAT and multiply real addresses ?
...nat those behind eth0 to go out as y.y.y.0/24 (eth1 is with another address different gw and address, so that i''m using eth1:0 and separate rule&table) I''m currently tring to do it this way : ifconfig eth1:0 y.y.y.2 netmask 255.255.255.0 ip route add default via y.y.y.1 table eth10-net ip rule from x.x.x.0/24 lookup eth10-net iptables -t nat -A POSTROUTING -s x.x.x.0/24 -j SNAT --to-source y.y.y.3-y.y.y.254 doesn''t seem to work.. the problem is that the eth1 interface have y.y.y.2 but not the all the addresses i need to have on eth1 interface... Probably I can set ~...
2009 Aug 17
2
[PATCHv3 0/4] qemu-kvm: vhost net support
This adds support for vhost-net virtio kernel backend. This is RFC, but works without issues for me. Still needs to be split up, tested and benchmarked properly, but posting it here in case people want to test drive the kernel bits I posted. Changes since v2: - minor fixes - added patch to build on RHEL5.3 Changes since v1: - rebased on top of 9dc275d9d660fe1cd64d36102d600885f9fdb88a Michael
2009 Aug 17
2
[PATCHv3 0/4] qemu-kvm: vhost net support
This adds support for vhost-net virtio kernel backend. This is RFC, but works without issues for me. Still needs to be split up, tested and benchmarked properly, but posting it here in case people want to test drive the kernel bits I posted. Changes since v2: - minor fixes - added patch to build on RHEL5.3 Changes since v1: - rebased on top of 9dc275d9d660fe1cd64d36102d600885f9fdb88a Michael
2007 Jun 11
24
multiple routing tables for internal router programs
Maybe a strange request, I''ll try to explain this as clearer as I can (forgive my bad english, please :-) ). I''m setting a linux box as a router. My router uses multiple routing tables, so I can address the traffic from specific ip addresses of my lan to distinct ISPs providers (specifying a different default gateway fo r each table), marking packets with iptables
2011 Aug 11
1
[PATCH] fix augtool calls
parse input augtool strings to oper,key,value --- scripts/network.py | 32 ++++++++++++++++---------------- 1 files changed, 16 insertions(+), 16 deletions(-) diff --git a/scripts/network.py b/scripts/network.py index f51ee7c..65b551c 100644 --- a/scripts/network.py +++ b/scripts/network.py @@ -165,11 +165,11 @@ class Network: ntpconf = ntpconf.split("\n") for line
2009 Aug 06
0
No subject
...omisc mode? What if you disable promisc mode? No, I'm using the physical MAC in the guest to avoid promisc. > Also, it seems that you have an external bridge that sends your outgoing > packets back to you. Is that right? Not that I'm aware of. My config is simply: eth0 - host nic eth10 - vhost nic I can ifdown eth0 and switch the host to eth10 and don't get duplicate packets on host<->external pings. Thanks, Alex
2009 Aug 06
0
No subject
...omisc mode? What if you disable promisc mode? No, I'm using the physical MAC in the guest to avoid promisc. > Also, it seems that you have an external bridge that sends your outgoing > packets back to you. Is that right? Not that I'm aware of. My config is simply: eth0 - host nic eth10 - vhost nic I can ifdown eth0 and switch the host to eth10 and don't get duplicate packets on host<->external pings. Thanks, Alex
2013 Jun 13
3
"Multiple Internet Connections" with four interfaces
Hi, I was reading document http://shorewall.net/MultiISP.html#idp3634200. Inspired by the document I was trying to establish the following changes: * one additional interface: COMA_IF * COM[A,B,C]_IF interfaces request IP address via DHCP * all non-RFC 1918 destined trafic is NATed from INT_IF to COMA_IF * all non-RFC 1918 destined trafic from GW is routed via COMB_IF by default * non-RFC 1918
2023 Aug 01
12
Bug#1042842: network interface names wrong in domU (>10 interfaces)
...rsion: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are sorted primarily by the leftmost digit. so for 11 interfaces we will end up with: vifX.0 <> eth0 vifX.1 <> eth1 vifX.10 <> eth2 vifX.2 <> eth3 vifX.3 <> eth4 .... This was observed with linux-kernel ve...