Originally Posted by pinniped
Don't bridge eth0 to eth1 - that's like unplugging your desktop and plugging only your laptop into the modem. Unless of course you bridged to a virtual interface (eth0:0). Hmm. Well, that's one option - bridge eth1 to eth0:0 and everything should magically work.
Rather than using a virtual interface by the name of eth0:0, I solely use eth0, eth1 and br0. And for the record, with the bridge set up, although not connecting to the notebook, internet is still fully accesible form the desktop. That's because I assign br0 an IP, if I wouldn't then I would suffer what you describe above.
Originally Posted by pinniped
The third option (the best option in the days when virtual interfaces weren't implemented), is to run dhcpd on eth1 to give your laptop an IP. The 'ipmasq' scripts can set up NAT between eth1 and eth0. You can run 'bind9' so that yoru desktop can act as a DNS machine - that allows you to set up dhcpd to tell the laptop to use your computer as a DNS. Alternatively, just set dhcpd to tell the laptop to use the desktop as a gateway and the static LAN IP of the modem as the DNS.
Please forgive me for my ignorance but I've never heard of an ipmasq-script, what distro are you using? Also DHCP is not my concern, I know very well which IPs are available in my subnet. I merely hoped enabling DHCP would somehow wake up my notebook's ethernet port and thus establish a link.
Also my DNS needs are handled by my router, I merely fill out its IP as the default gateway and DNS server and my internet connection (if directly connected like on my desktop) works fine.
Actually I am using that subnetting 'trick' already at a different point in the local network. Like this:
----WWW----|ISP router|--192.168.1.--|hub|--192.168.1.--|my 4-port router|--192.168.2.--|desktop|
Although creating a new subnet for my notebook is fine with me, the reason I'd like to have it on the same subnet is because I am preparing a server to act as a traffic monitor for the entire network. That's why I'd like to have this bridge-problem figured out first so I know how to implement it on that other machine.
UPDATE: (Partial) Victory! Luckily I'm not losing my mind
Just ran some more tests, here are my findings;
The Realtek chip in my notebook was not being correctly initialised by the Backtrack 2.xx/3beta live disc I was using. In other words, after trying several live discs, Slax provided an useful testing platform, ironically enough (Backtrack is based on Slax). The bridge on my desktop to my notebook is functional now but there is still something very strange going on though.
The setup works when the Realtek port of my notebook is connected to the Marvell port of my desktop and the nForce port of my desktop is connected to the router.
When the Realtek port of my notebook is connected to the nForce port of my desktop and the Marvell port of my desktop is connected to the router, there is no link between the notebook and the desktop!
As a sidenote, the DHCP traffic is succesfully forwarded though the bridge, but now that I'm reassured it works I'll go back to static IPs quite soon.