At 09:22 PM 12/14/2006 +0100, Erik Wikstrvm wrote:
I've get an box laying in my basement running OpenBSD 3.7 (probably
should upgrade that some time but I've never taken the time) acting
as gateway for both wired and wireless networks. Everything has
been working flawlessly except one thing; I can not access
computers on the wireless network from the wired one or vice versa.
This has not been much of a problem since I'm mostly connecting via
the wired network but now my mother has gotten herself a laptop and
she wishes to be able to access another computer to print. Most
computers (are not mine) and run Windows.
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. Obviously I did
something wrong, so I'd hope that someone might be able to explain
to me how to set up the network.
I've put copies of all files I thought might be of relevance on the
web at http://www.chalmers.it/~eriwik/obsd/
Thanks for your time
Hello Eric,
Check the print server to which your mum is attempting to send her
document isn't filtering packets to 137/udp (Windows name resolution)
and/or 139/tcp (Windows file/print sharing).
Since your wired (192.168.0.0/24) and wireless (192.168.1.0/24)
networks are on different subnets this would be the default behaviour
for the Windows XP native firewall, for example - it will block
anything from 192.168.1.0/24 since Windows thinks anything outside of
192.168.0.0/24 is the big, bad internet.
I have a similar home network configuration to yours [except I have
IPsec on the wireless interface which complicates things a
little ;-) ] and i ran into exactly the same problem.
I found the simplest solution in the end was to manually reconfigure
the Windows XP firewall to accept connections from the other subnet.
As that's outside the scope of this list I won't elaborate but you're
welcome to contact me off-list if you require assistance.
You can also use a pf NAT rule to translate the source address, i.e...
# make packets from your wireless subnet 192.168.1.0/24 look like
they're coming from 192.168.0.1
nat on rl0 from ath0:network to rl0:network -> rl0
# make packets from your wired subnet 192.168.0.0/24 look like
they're coming from 192.168.1.1
nat on ath0 from ral0:network to ath0:network -> ath0
...but it's very kludgy :-(
Best wishes,
Damon
