-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karotu Tannang escreveu:
| Hi all,
|
| I have just created a bridge on a Linux Mandrake server but then realised
| after boot that I have lost it!
|
| Does anyone know how to get the bridge to work after boot-up?
|
| Any suggestion will be greatly
It would be easier to say what is wrong if you had not left out all those
error messages from insmod; however the most likely problem is that the
running kernel was compiled without bridge support. I am also running
RedHat 8.0, and since it came with kernel 2.4.18, I presume you have
upgraded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eduardo Bejar wrote:
| Chuck,
|
| Recompile your kernel with
|
| Network packet filtering debugging = N
|
| Perhaps you set it as Y.
|
| Eduardo
|
Thanks Eduardo -
Yep, that was it. In the immortal word of Homer Simpson:
Doh!!!
Thanks
Chuck
-
Chuck,
Recompile your kernel with
Network packet filtering debugging = N
Perhaps you set it as Y.
Eduardo
- Mensaje original -
De: Chuck R. Bell [EMAIL PROTECTED]
Para: [EMAIL PROTECTED]
Enviado: Miércoles, 11 de Junio de 2003 21:30
Asunto: [Bridge] Bridging: syslog running amok.
Thank you Lucas, that did work!
Now I'm wondering if the server can remember all the MAC addresses and IPs the
bridge learnt before rebooting.
Everytime I restart the server, the bridge has to learn all the MACs and IPs
all over again which takes a while with only 3 PCs connected to the
Karotu Tannang wrote:
Now I'm wondering if the server can remember all the MAC addresses and IPs the
bridge learnt before rebooting.
No. That's why it's called a 'learning' bridge.
Everytime I restart the server, the bridge has to learn all the MACs and IPs
all over again which takes a while
OK - I managed to get bridge support working in my kernel, not to sure
what was going on when I rebuilt it the first time.but it was the end
of a long day :)
I've currently got the Bridge working fine using a GigE interface and some
10/100 interfaces. Is there an easy way to save the current
hello.
i have been playing/learing about bridging. i had set up an old laptop
running a kernel 2.4.20 with the appropriate ebtables patch as a bridge.
everying was going fine. i configured the bridge/routes, wrote a startup
script, filled in iptables appropriately, and it worked. i could
Francois Prowse wrote:
I've currently got the Bridge working fine using a GigE interface and some
10/100 interfaces. Is there an easy way to save the current config so it
will survive a reboot?
Write a script to set it up at boot time - Put it in /etc/rc.d/rc.local
or another appropriate
Theodore Wynnychenko wrote:
after some trial and error, this is what i found.
IF i reboot the bridge when i have the interface cables connected to the
network and external gw, then NOTHING gets through the bridge (except ssh to
the bridge from internal net).
What state is the bridge in when you do
Sorry.
after some trial and error, this is what i found.
IF i reboot the bridge when i have the interface cables connected to the
network and external gw, then NOTHING gets through the bridge (except ssh to
the bridge from internal net).
IF i reboot the bridge when it is NOT CONNECTED TO
Theodore Wynnychenko wrote:
eth0 Link encap:Ethernet HWaddr 00:30:BD:12:31:20
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth1 Link encap:Ethernet HWaddr 00:30:BD:01:2C:E1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Neither of those are 'promisc' -
12 matches
Mail list logo
