Just a quick bump on my issue as I've not found a solution as yet.
On Mon, 25 Oct 2021, 11:41 am Cameron Murray,
wrote:
> Hi Team,
>
>
>
> Having difficulties creating a bridge between a VXLAN interface and a
> child vlan of a bonded interface pair.
>
> br0
> --- bond0.142
> --- vx142
>
>
Hi Team,
Having difficulties creating a bridge between a VXLAN interface and a
child vlan of a bonded interface pair.
br0
--- bond0.142
--- vx142
https://pastebin.com/ynpRf3jf
It appears from my searching that it’s possible that as vlan 142 is
part of a bond/bridge already it will not
Hi
Im trying to setup a VM with aqemu and i would like my vm to connect to
the local network via dhcp.
I followed the instructions at
https://wiki.debian.org/QEMU
> my /etc/network/interfaces is
>
>
> # This file describes the network interfaces available on your system
> # and how to
# no forwarding delay
#bridge_ports none # if you do not want to bind to any ports
#Bridge_ports regex eth* # use a regular expression to define ports
# To restart the service after update:
# /etc/init.d/procps restart
One of my challenges is that bridging to a wireless NIC requires 4addr
I have an issue where my bridging firewall no longer drops traffic. Everything
looks like it should be working but I can still access things I shouldn't. I
am wondering if my use case is no longer supported.
This system worked well for years. When I updated from Debian 6 to Debian 7
The use case is that I need to bridge eth0 with eth0.2, allowing layer
two traffic to pass seamlessly between interfaces, yet still leave
eth0.3 in a usable state. The switch this system is connected to is
for all intents and purposes outside of my control, which is the
reason for the odd
Greetings-
I have an interesting situation that requires bridging some VLAN enabled
interfaces together on a Debian 7.x x86 system. On the host, there is a single
physical interface passing traffic natively (eth0), and two tagged VLANs also
passing traffic (eth0.2 and eth0.3).
The use case
On 12/11/2014 03:45 PM, Tim Nelson wrote:
Greetings-
I have an interesting situation that requires bridging some VLAN enabled
interfaces together on a Debian 7.x x86 system. On the host, there is a
single physical interface passing traffic natively (eth0), and two
tagged VLANs also passing
Tim Nelson tnel...@rockbochs.com wrote:
The use case is that I need to bridge eth0 with eth0.2, allowing layer
two traffic to pass seamlessly between interfaces, yet still leave
eth0.3 in a usable state. The switch this system is connected to is
for all intents and purposes outside of my
On 10/11/14 12:50 AM, Christian Seiler wrote:
Am 10.11.2014 01:33, schrieb Gary Dale:
On 09/11/14 03:30 PM, Christian Seiler wrote:
Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following
Hi
On Sat, Nov 08, 2014 at 05:57:41PM -0500, Gary Dale wrote:
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
address
Am 08.11.2014 23:57, schrieb Gary Dale:
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.1.14
On 09/11/14 05:27 AM, Christian Seiler wrote:
Am 08.11.2014 23:57, schrieb Gary Dale:
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
On 09/11/14 05:09 AM, Karl E. Jorgensen wrote:
Hi
On Sat, Nov 08, 2014 at 05:57:41PM -0500, Gary Dale wrote:
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto
the required options in the
host configuration for this.
So, for example, I have completely disabled the default.xml network
configuration in libvirt (no link in autostart/), and bridging still
works because libvirt detects the bridge set up by Debian's network
configuration; in the NIC settings
detect that setup and provide the required options in the
host configuration for this.
So, for example, I have completely disabled the default.xml network
configuration in libvirt (no link in autostart/), and bridging still
works because libvirt detects the bridge set up by Debian's network
Am 09.11.2014 21:13, schrieb Gary Dale:
You're right. Here's my default.xml (I only changed the addresses):
root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml
network
namedefault/name
bridge name=br0 /
forward/
ip address=192.168.1.14
On 09/11/14 03:30 PM, Christian Seiler wrote:
Am 09.11.2014 21:13, schrieb Gary Dale:
You're right. Here's my default.xml (I only changed the addresses):
root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml
network
namedefault/name
bridge name=br0 /
forward/
Am 10.11.2014 01:33, schrieb Gary Dale:
On 09/11/14 03:30 PM, Christian Seiler wrote:
Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following settings (which are default):
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.1.14
netmask 255.255.255.0
broadcast
Mon, 11 Aug 2014 05:44:18 +
Any tips on using SEM India DNA-A201 modem in bridge mode?
Modem has adsl and ppp commands. No man pages.
All attempts lead to dangling IP address (wan IP) reachable only from
localhost.
adsl
Usage: adsl start [--up] [--mod a|d|l|t|2|p|e|m] [--lpair
Jean Baptiste FAVRE a écrit :
On 11/05/2014 06:02, Gaël wrote:
Mouais. L'OP a dit qu'il avait 5 adresses IP publiques. Si elles
sont contigües ça me fait bougrement penser à un /29, bloc de 8
adresses dont 3 sont réservées comme adresses de réseau (la
première), passerelle et broadcast (la
On 11/05/2014 06:02, Gaël wrote:
Je n'ai jamais appliqué ça, mais je l'ai vu chez un hébergeur du
côté de Rennes.
:) Ça doit être le même, alors :)
Oui, je pense :)
Du coup le host est obligé de causer à la gateway, y compris
pour joindre son voisin de rack. Ça peut présenter un intérêt
Le 09/05/2014 20:07, Jean Baptiste FAVRE a écrit :
J'avoue que moi aussi, ça me laisse perplexe. D'autant que je ne
vois pas comment la passerelle A.B.C.D peut être atteinte depuis le
'réseau' A.B.C.D/32 (avec D différent de 1, sinon ce n'est pas du jeu).
C'est juste un lien point à
Bzzz a écrit :
On Fri, 09 May 2014 15:24:40 +0200
Francois Lafont mathsatta...@free.fr wrote:
C'est une drôle de config, je n'avais jamais vu encore.
Je pensais que la passerelle par défaut se trouvait
toujours dans le même réseau IP que celui de l'interface
eth0 (je suppose qu'il n'y a
Je n'ai jamais appliqué ça, mais je l'ai vu chez un hébergeur du côté de
Rennes.
:)
Ça doit être le même, alors :)
Du coup le host est obligé de causer à la gateway, y compris pour
joindre son voisin de rack.
Ça peut présenter un intérêt en terme de sécurité car tout le trafic
transite
Hello !
Merci de vos réponses !
Le masque de sous-réseau en /32, c'est normal ?
C'est pas pour ça que ça ne fonctionne pas comme espéré ?
Sur l'hôte, il est évident que ce n'est pas normal.
Bah, sur ma config d'origine, fournie par l'hébergeur lors de
l'install de l'OS, c'est bien ça.
On Fri, 9 May 2014 14:38:59 +0200
Gaël gag...@gmail.com wrote:
Wa, je pensais vraiment pas que ça puisse résoudre le soucis, mais
en effet, là ça marche niquel !
Je comprends pas exactement à quoi sert cette ligne.
up route add -host A.B.C.1 dev eth0
Quand le réseau passe up, ajouter aux
Bonjour,
Tant mieux si tu as pu résoudre ton problème.
Du coup, je me permets de réagir et de digresser
quelque peu sur ce point là :
Le 09/05/2014 14:38, Gaël a écrit :
Bah, sur ma config d'origine, fournie par l'hébergeur lors de
l'install de l'OS, c'est bien ça.
#auto eth0
#iface eth0
Le 09/05/2014 15:24, Francois Lafont a écrit :
Bonjour,
Tant mieux si tu as pu résoudre ton problème.
Du coup, je me permets de réagir et de digresser
quelque peu sur ce point là :
Le 09/05/2014 14:38, Gaël a écrit :
Bah, sur ma config d'origine, fournie par l'hébergeur lors de
l'install de
On Fri, 09 May 2014 15:24:40 +0200
Francois Lafont mathsatta...@free.fr wrote:
C'est une drôle de config, je n'avais jamais vu encore.
Je pensais que la passerelle par défaut se trouvait
toujours dans le même réseau IP que celui de l'interface
eth0 (je suppose qu'il n'y a qu'une interface en
On 09/05/2014 15:30, Joël BERTRAND wrote:
Le 09/05/2014 15:24, Francois Lafont a écrit :
Bonjour,
Tant mieux si tu as pu résoudre ton problème.
Du coup, je me permets de réagir et de digresser
quelque peu sur ce point là :
Le 09/05/2014 14:38, Gaël a écrit :
Bah, sur ma config d'origine,
Hello,
Le 04/05/2014 21:18, Jean Baptiste FAVRE a écrit :
Hello,
Le masque de sous-réseau en /32, c'est normal ?
C'est pas pour ça que ça ne fonctionne pas comme espéré ?
JB
Sur l'hôte, il est évident que ce n'est pas normal.
Par contre à l'intérieur d'une VM et si les IP
configurer le réseau.
J'ai 5 adresses IPs, j'en veux une pour le host, et les 4 autres iront
pour 4 des VMs, plus tard.
Je veux faire du bridge, afin d'avoir, en gros, 5 machines accessibles
depuis l'extérieur.
Voilà ma config de base, avant d'essayer le bridging (je ne mets pas lo) :
auto eth0
On Sun, 4 May 2014 19:53:29 +0200
Gaël gag...@gmail.com wrote:
auto eth0
iface eth0 inet static
address A.B.C.D
netmask 255.255.255.255
network A.B.C.D
broadcast A.B.C.D
dns-nameservers A.B.C.1
dns-search monHebergeur.fr
#Route statique
faire du bridge, afin d'avoir, en gros, 5 machines
accessibles depuis l'extérieur.
Voilà ma config de base, avant d'essayer le bridging (je ne mets
pas lo) :
auto eth0 iface eth0 inet static address A.B.C.D netmask
255.255.255.255 network A.B.C.D broadcast A.B.C.D dns-nameservers
A.B.C.1
d'essayer le bridging (je ne mets pas
lo) :
auto eth0
iface eth0 inet static
address A.B.C.D
netmask 255.255.255.255
network A.B.C.D
broadcast A.B.C.D
dns-nameservers A.B.C.1
dns-search monHebergeur.fr
#Route statique vers la passerelle
up route
On Wed, Oct 2, 2013 at 3:05 AM, Ross Boylan r...@biostat.ucsf.edu wrote:
I setup bridging on my system for kvm, but on restart of the host system
(no guest VM's running) could not ping outside my local network.
Bringing the bridge down corrected the problem, but I'm trying to
understand
On Wed, Oct 2, 2013 at 3:40 PM, Ross Boylan rossboy...@stanfordalumni.org
wrote:
Arun made a suggestion that
Your 'physical' device eth0/eth2 or whatever needs to be added to the
bridge.
I believe that is done by the /etc/kvm/kvm-ifup script that is executed
when I
launch the virtual machine.
On Thu, Oct 3, 2013 at 8:14 PM, Bob Proulx b...@proulx.com wrote:
Arun made a suggestion that
Your 'physical' device eth0/eth2 or whatever needs to be added to the
bridge.
I believe that is done by the /etc/kvm/kvm-ifup script that is executed
when I launch the virtual machine.
I think
I removed network manager and have this in /etc/network/interaces:
# eth2 managed by bridge and not otherwise mentioned
auto br0
iface br0 inet dhcp
bridge_ports eth2
That seems to work with the kvm-ifup script provided by wheezy qemu-kvm.
Note I have not rebooted since setting this up, and
On Sun, Oct 6, 2013 at 2:14 PM, Ross Boylan
rossboy...@stanfordalumni.org wrote:
I removed network manager and have this in /etc/network/interaces:
# eth2 managed by bridge and not otherwise mentioned
auto br0
iface br0 inet dhcp
bridge_ports eth2
That seems to work with the kvm-ifup
On Thu, Oct 03, 2013 at 09:44:31AM -0700, Ross Boylan wrote:
Greg, thanks for explaining this. I'm still puzzled about one point, below.
On Wed, Oct 2, 2013 at 4:10 PM, Gregory Nowak g...@gregn.net wrote:
On Wed, Oct 02, 2013 at 12:40:26PM -0700, Ross Boylan wrote:
Can anyone explain
for
everything to be functioning correctly. But in general it should work
okay.
This is not the long-run plan. The router keeps flaking out,
perhaps in part because of some interaction with the bridging:
The router should not care that you are using a bridge on your client
or not. Using a bridge
On Thu, Oct 3, 2013 at 5:14 PM, Bob Proulx b...@proulx.com wrote:
Greg has made some excellent explanation and answers. I wanted to
comment on a few other things.
Ross Boylan wrote:
Arun made a suggestion that
Your 'physical' device eth0/eth2 or whatever needs to be added to the
Ross Boylan wrote:
Bob Proulx wrote:
I think that file must have been removed at some point. I have
the qemu-kvm package (which owns that file) installed but do not have
that file on my system. The qemu-kvm.postinst script in the current
package removes the conffile. So just a note
I setup bridging on my system for kvm, but on restart of the host system
(no guest VM's running) could not ping outside my local network.
Bringing the bridge down corrected the problem, but I'm trying to
understand what is going on, and how I can make networking from the VM's
work.
/etc/network
How did you configured eth2? dhcp too? why you tap as bridge port intend of
eth2?
2013/10/2 Ross Boylan r...@biostat.ucsf.edu
I setup bridging on my system for kvm, but on restart of the host system
(no guest VM's running) could not ping outside my local network.
Bringing the bridge down
On Wed, Oct 2, 2013 at 12:35 PM, Ross Boylan r...@biostat.ucsf.edu wrote:
I setup bridging on my system for kvm, but on restart of the host system
(no guest VM's running) could not ping outside my local network.
Bringing the bridge down corrected the problem, but I'm trying to
understand
Ross Boylan wrote:
/etc/network/interfaces has (on the advice of a wiki page on Debian and
kvm)
Which page is a wiki page? I didn't find a wiki.debian.org one that
had an example like it.
How about this one? It has good working examples.
http://wiki.libvirt.org/page/Networking
auto br0
router is currently serving as a dhcp server; it has a reserved
IP for the system under discussion. This is not the long-run plan. The
router keeps flaking out, perhaps in part because of some interaction with
the bridging: I've had 2 or 3 problems since I started the bridging, and
none since I took
) to be on the eth2 network. So, a bridge
would look something like this:
...
iface br0 inet dhcp
bridge_ports eth2 tap0
...
Once you do that, the virtual machine configured to use tap0 would be
able to talk to all computers on the network to which eth2 is
connected. Since you are bridging eth2, you don't want
Hello, merry christmas at all,
after setting aup my laptop on wheezy now I got back to the
konfiguration of my server.
I have running there 3 dom0 with bridged IPv4.
I have an subnet for IPv6 with a lot of adresses and i want to use them
(my home system has tunneled IPv6)
An IPv4 subnet is too
On Fri, Jun 29, 2012 at 11:47:29PM +0100, Chris Davies wrote:
Steve Dowe s...@warpuniversal.co.uk wrote:
The issue I'm having, using wheezy, is that if I set up a bridged
ethernet interface for eth0 (br0), as per instructions on the Debian
wiki etc, NetworkManager can no longer manage my
Jon Dowland j...@debian.org wrote:
You don't need to remove NM. I have it managing my wifi and 3G connections,
but manage eth0 via ifupdown (and attach it to a bridge).
That's what I have at the moment, and NM gets itself in a tizzy when I
want to use eth0 as my primary connection and borks my
I'm sorry for the tardy response - IceDove hid a load of Debian list
mail in Junk.
On 29/06/12 18:06, Camaleón wrote:
Maybe is time now for you to tell us more about the kind of VM you are
planning to use...
Testing on the same subnet :)
I still don't see the relation of using N-M and the
On 29/06/12 17:34, Neal Murphy wrote:
(...)
another program running whose sole purpose is to slurp CPU cycles, take up
screen real estate
I'm all for machine efficiency, but I don't find NM to do either of
those. On a laptop, I find it sacrifices my human efficiency to /not/
have it.
and
On Mon, 02 Jul 2012 17:14:02 +0100, Steve Dowe wrote:
I'm sorry for the tardy response - IceDove hid a load of Debian list
mail in Junk.
On 29/06/12 18:06, Camaleón wrote:
Maybe is time now for you to tell us more about the kind of VM you are
planning to use...
Testing on the same
On 29/06/12 23:47, Chris Davies wrote:
Steve Dowe s...@warpuniversal.co.uk wrote:
The issue I'm having, using wheezy, is that if I set up a bridged
ethernet interface for eth0 (br0), as per instructions on the Debian
wiki etc, NetworkManager can no longer manage my wired ethernet connection.
On 02/07/12 17:34, Camaleón wrote:
Testing on the same subnet :)
Yes but what solution? KVM, VMware, Xen, VirtualBox...
Oh heck, sorry. It's KVM. I thought I'd mentioned that. Oops.
Basically, you need eth0 bridged (using br0) to allow other virtual
machines to pick up an IP address on
. It just
works.
Granted, I mix decimal and hex; but some things are hard to avoid.
And I really don't know why Squeeze assigns IPv6 LL addresses to NIC/taps that
are members of a bridge, but dutifully erases IPv4 addresses from same.
Bridging isn't exactly rocket science, but the documentation
/network/interfaces:
# The loopback network interface
auto lo br0
iface lo inet loopback
# bridging
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
I must be missing something simple here. Could anyone point me in the
right direction please
Arun Khan a écrit :
When you use bridge: To the best of my knowledge - the IP is assigned
to the bridge and *not* eth0 the physical interface. eth0 should
*not* have any IP assigned to it.
Except in some very specific situations.
Exemple : you want the box act as a bridge with some
# bridging
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
NM's now doing bridging but has it been patched to understand Debian's
/etc/network/interfaces? (It understands Fedora's ifcfg-style
network configuration.)
Does bridging work without
# bridging
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
I must be missing something simple here. Could anyone point me in the
right direction please? Has anyone got a working config?
TIA...
Steve
--
Steve Dowe
Warp Universal Limited
http
that any bridge
needs at least two end points.
This is my current /etc/network/interfaces:
# The loopback network interface
auto lo br0
iface lo inet loopback
# bridging
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
I must be missing
interface
auto lo br0
iface lo inet loopback
# bridging iface br0
inet dhcp
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
I must be missing something simple here. Could anyone point me in
the right direction please? Has anyone got a working config
as necessary to service the virtual machines I'm
running. The bridge, in this case, is a virtual-to-physical one.
Ah, then maybe you don't need a bridge but a virtual addressing layout:
http://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_One_Interface
There are some bridging samples
the virtual network interfaces of virtual
machines the chance to pick up an IP address using DHCP whatever local
network they're on.
There are some bridging samples here:
http://wiki.debian.org/BridgeNetworkConnections#Configuring_bridging_in_.2BAC8-etc.2BAC8-network.2BAC8-interfaces
Thanks. I did
On 29/06/12 17:19, Steve Dowe wrote:
On 29/06/12 16:54, Camaleón wrote:
Ah, then maybe you don't need a bridge but a virtual addressing layout:
http://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_One_Interface
But that fixes the IP addresses both to my local network. The
On Friday 29 June 2012 10:02:57 Steve Dowe wrote:
Hello,
I have absolutely no doubt that someone reading this list knows more
than I do on this.. :)
The issue I'm having, using wheezy, is that if I set up a bridged
ethernet interface for eth0 (br0), as per instructions on the Debian
wiki
On Fri, 29 Jun 2012 17:19:27 +0100, Steve Dowe wrote:
On 29/06/12 16:54, Camaleón wrote:
Ah, then maybe you don't need a bridge but a virtual addressing layout:
http://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_One_Interface
But that fixes the IP addresses both to my
Steve Dowe s...@warpuniversal.co.uk wrote:
The issue I'm having, using wheezy, is that if I set up a bridged
ethernet interface for eth0 (br0), as per instructions on the Debian
wiki etc, NetworkManager can no longer manage my wired ethernet connection.
You can't do that :-(
If you need a
On Sb, 14 mai 11, 22:14:44, peasth...@shaw.ca wrote:
What are the greatest advantages in bridging eth0 and eth1 rather
than routing through Dalton to Carnot? Bridging will need some
additional software, bridge-utils; routing should be possible
without adding software.
AFAIK
[eth2 in the Proposed Network].
That's all.
What are the greatest advantages in bridging eth0 and eth1 rather
than routing through Dalton to Carnot? Bridging will need some
additional software, bridge-utils; routing should be possible
without adding software.
It's been a long time
the MAC address from the frame header. From this superficial thinking,
packet routing is more efficient than frame forwarding. Is that true?
For you different IP networks setup you will need to properly configure
both
NAT and routing which it's a bit more difficult than bridging.
OK, to see
in bridging eth0 and eth1 rather
than routing through Dalton to Carnot? Bridging will need some
additional software, bridge-utils; routing should be possible
without adding software.
Thanks, ... Peter E.
--
Telephone 1 360 450 2132. bcc: peasthope at shaw.ca
Shop pages http
Good evening,
I’m using NetworkManager to automatically connect to a number of wifi
networks as well as to ethernet networks at home and in university.
I’m also using the dispatcher to run custom scripts depending on the
network to which the computer just connected.
Now it would be nice if I
on adding
network bridge support.
The last ETA I read was late 2010 from there website [1] ... I was just
wondering if anyone knew this was still the case.
Network bridging support would be very useful to me for running Xen on my
Debian system.
[1] http://projects.gnome.org/NetworkManager
Bonjour Pascal
et merci de cette réponse qui va plus loin que ce que je pensais..
Je m'attendais naivement à trouver une page listant le support éventuel de
cette fonctionnalité mais rien trouvé de tel..
Il faut qu'il permette d'émettre des trames avec une adresse MAC source
autre que celle de
Bonsoir a tous,
je reviens vers vous pour savoir comment connaitre le support éventuel de
mon driver wireless (iwlagn) du bridging?
je voudrai eventuellement bridge l'interface wlan0 pour une utilisation de
kvm
merci d'avance
PS:
rien vu sur le site intel, iwlwifi et autres
--
Jerome Moliere
Salut,
jerome moliere a écrit :
je reviens vers vous pour savoir comment connaitre le support éventuel de
mon driver wireless (iwlagn) du bridging?
Il faut qu'il permette d'émettre des trames avec une adresse MAC source
autre que celle de l'adaptateur. Je pense que modifier l'adresse MAC de
Works like a charm:
auto br0
iface br0 inet static
address 192.168.0.113
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
bridge_ports eth0
auto wlan0
iface wlan0 inet dhcp
wpa-ssid MySSID
wpa-pskMyPlaintextPassword
post-up
Bob van der Moezel wrote:
I am trying to bridge a wireless channel with a wired channel (and some KVM
tap/tun channels for virtual servers).
I am running Debian Testing, bridge-utils 1.4-5 and wpasupplicant 0.6.4-3.
Any ideas to get this to work? (I sent two days without any luck).
I
I am trying to bridge a wireless channel with a wired channel (and some KVM
tap/tun channels for virtual servers).
/etc/network/interfaces:
auto lo
iface lo inet loopback
auto br0
iface br0 inet static
address 192.168.0.113
network 192.168.0.0
netmask
On Wed, Apr 01, 2009 at 11:45:08PM +0200, Bob van der Moezel wrote:
I am trying to bridge a wireless channel with a wired channel (and some KVM
tap/tun channels for virtual servers).
My understanding is that bridging of wireless devices is very dependant
on the wireless card (chipset
again after finding these
in the logs to see if it would be reproduced, but they were not.
Daryl
Replying to myself...
Turns out above steps for bridging/dhcp still work fine. It seems the
Debian installer was refusing to request an address from the laptop/dhcp
server. However, once I moved
I'm attempting to bridge wlan0 with eth0. I've done this successfully
in the past with firestarter and dhcp3-server. However I'm running into
some issues trying to set this up now.
What I have done in the past is set eth0 static, and enabled internet
connection sharing in firestarter. Which
On Mon, Feb 23, 2009 at 01:25:30PM +0100, Udo Hortian wrote:
Hello all,
I subscribed newly to this list, since I got an bridging problem
after an upgrade from Debian etch to Debian lenny (before
everything worked fine).
The situation is as follows:
# brctl show
bridge name bridge
Hello all,
I subscribed newly to this list, since I got an bridging problem
after an upgrade from Debian etch to Debian lenny (before
everything worked fine).
The situation is as follows:
# brctl show
bridge name bridge id STP enabled interfaces
br0
with my cellphone to share the internet
I don't think bridging of wireless and ethernet works, why not just
route the packets! use iptables to setup nat if you need
Indeed bridging with wireless is not a good idea: I experienced it !
Nevertheless, I have not yet understand in detail the suggested
and wlan0, I tried to bridge them
and use a ad-hoc connection with my cellphone to share the internet
I don't think bridging of wireless and ethernet works, why not just
route the packets! use iptables to setup nat if you need
Indeed bridging with wireless is not a good idea: I experienced
On Sun, Jan 25, 2009 at 12:03:47AM -0500, Wayne Topa wrote:
Deephay wrote:
Greetings all,
I have two NICs on my laptop: eth0 and wlan0, I tried to bridge them
and use a ad-hoc connection with my cellphone to share the internet
I don't think bridging of wireless and ethernet works, why
Hello List !
Alex Samad wrote:
On Sun, Jan 25, 2009 at 12:03:47AM -0500, Wayne Topa wrote:
Deephay wrote:
Greetings all,
I have two NICs on my laptop: eth0 and wlan0, I tried to bridge them
and use a ad-hoc connection with my cellphone to share the internet
I don't think bridging
wlan0
tcpdump will show the ARP request message again and again, this
behavior is different from MS Windows bridging. Could anyone tell me
why?
How did you set up the bridge? Show us your interfaces file.
WT
--
To UNSUBSCRIBE
wlan0
tcpdump will show the ARP request message again and again, this
behavior is different from MS Windows bridging. Could anyone tell me
why?
Deephay
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe
I was thinking of using ethernet bridging to simplify naming and routing on my
system. This system consists of four computers all interconnected. The question
is whether there is any hidden cost, as I need the cards to work at full
throughput (three ethernet cards). So, will this just give me
On Tuesday 09 December 2008, Micha Feigin [EMAIL PROTECTED] wrote
about 'the cost of ethernet bridging':
I was thinking of using ethernet bridging to simplify naming and routing
on my system. This system consists of four computers all interconnected.
The question is whether there is any hidden
Other than sharing the same IP, say wireless interface and ethernet, what
else? In case I missed something. Please share your experience :)
--
Regards,
Umarzuki Mochlis
http://gameornot.net
Umarzuki Mochlis wrote:
Other than sharing the same IP, say wireless interface and ethernet, what
else? In case I missed something. Please share your experience :)
Are you asking how to bridge those interfaces? I don't fully understand
your question.
--
To UNSUBSCRIBE, email to [EMAIL
1 - 100 of 181 matches
Mail list logo
