On Thu, Dec 14, 2006 at 09:22:47PM +0100, Erik Wikstr?m wrote: > I have three NICs in the box, two rl(4) and one ath(4), rl1 is connected > to the Internet and rl0 and ath0 are the local networks. As I understand > things I need to bridge the two local NICs somehow to be able to access > computers on both networks seamlessly, however I recall trying that once > but with no success.
You shouldn't have to do that. One subnet on 192.168.0.x and the other on 192.168.1.x should still be able to route IP between the two. The only thing which won't work is that broadcasts on one network won't be seen by machines on the other network. Limiting broadcast scope in this way is generally considered A Good Thing [TM]. However, Windows machines in their most basic mode of operation rely on broadcasts to find each other in the 'network neighborhood' If this is your problem, then you can fix it by installing a WINS server, a local DNS server with dynamic updates, or by using the LMHOSTS file on each Windows box to hardcode the NetBIOS name to IP address mappings. Don't ask me how to do that - I don't grok Windows :-) But the first thing you need to do is to see if a machine on 192.168.0.x can ping a machine on 192.168.1.y. If they can't, then you have a deeper problem than that - probably pf rules. > I've put copies of all files I thought might be of relevance on the web > at http://www.chalmers.it/~eriwik/obsd/ I can't see anything obviously wrong, but if your machines can't ping between the two subnets, a simple test would be to empty out your pf ruleset (which obviously will stop your local machines from communicating with the Internet because of the lack of nat, but would demonstrate whether they can then ping each other directly) As you say, another solution would be to bridge rl0 and ath0, and run your home LAN as a single subnet. See man brconfig and bridgename.if HTH, Brian.
