Hi!

I ping it from the local network.
Yes I setup rc.inet1.conf eth0 and eth1. With eth0 - dhcp eth1 - fix ip.
eth0 works find.

I am beginning to suspect the eth1 is faulty. I will switch it with another card do confirm this.

well, if you setup eth1 in the rc.inet1.conf file but ifconfig shows no settings for that card, why don't you manually set eth1 and see if that works. Have you tried that?
I only asked about ipV6 out of curiosity. I think that might just complicate the issue at this point. I would first get the two cards working, then worry about that. Just my opinion though...

Good NEWS!

eth1 is up and running. ping successful (I assume other protocol as well). What did I do?
1. Use kernel 2.6.4
2. Change the NIC (same model).

The problematic NIC works fine in another comp. Don't know what causes the problem.

So now, to configure the bridge. Still blur about this.

Good work!

Below is the howto I used to get mine up and running. And it hasn't failed me since. You just have to make sure that you point the eth1 and eth0 to the right places. Hope that helps.

http://www.tldp.org/HOWTO/IP-Masquer...FIREWALL-2.4.X

There seems to a lot of changes around the e100 driver in 2.6.4
In the original post I saw "bridge". Bridging is much harder to set up in Linux than routing and I have no idea what is involved in the 2.6.x kernel

Hi!

I read Network Administer Guide 2 (on NAT). And I did download and print IP-Masquerade, haven't get to read it yet. I realise what I need is NAT (IP-Masquerade).

As I was configuring the kernel to support that in 2.6.4, I came across ethernet bridging and wonder what is it.

Alright, I got IP-Masq (SNAT) up and running.

Here is how I did it.

1. Get eth0 and eth1 working
2. Compile kernel to support ip-masq (check ip-masq-howto from tldp.org for the configs)
3. Download rc.firewall from http://www.ecst.csuchico.edu/~dranch...masq/examples/
4. Edit the ip-addresses and remove loading modules if you compile everything into the kernel like I did.
5. Place rc.firewall at /etc/rc.firewall and chmod 700 rc.firewall
6. ./rc.firewall
(I also chmod +x rc.ip_forward; not sure it is needed since rc.firewall will enable ip forward also).
And I am up and away. Tested it, everythign work so far.

But since I used strong firewall script, now I can't ssh or ping my Masq-server from outside. Need to configure the rc.firewall again, later.