OpenBSD router +netbios forwarding

I have 2 subnets

10.69.69.0/24
192.168.0.0/24

the OBSD box is acting as a router between the 2.
But it doesn't forward netbios over tcp/ip broadcasts to opposite subnets. Its not supposed to by default. But this is what I need.
I've tried using pf to rdr udp ports 137 138 139 over the subnets.
That didn't work :)

Any ideas? This is easy to do with cisco routers so it shouldn't be too hard with obsd.

here are some of my PF rule attempts


rdr on hme0 proto udp from 192.168.0.0/24 to any port { 137, 138, 139 } -> 10.69.69.255
rdr on hme1 proto udp from 10.69.69.0/24 to any port { 137, 138, 139 } -> 192.168.0.255

#rdr on hme0 proto udp from any to any -> 10.69.69.255      
#rdr on hme1 proto udp from any to any -> 192.168.0.255
deadlastAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
NO.
You need shared WINS server like samba nmbd or windows PDC, and select it on all workstations.
Starting from Windows2000 it uses port 445 and maybe 80+443 for NetBIOS too, and you forgot nameservice - port 135... check out netstat -na just in case.
Easy if you have got DHCP, or somebody should attend all workstations ( and maybe switch to DHCP, so you get central workstations configuration in one place )
0
deadlastAuthor Commented:
no I don't need any of that. I did this yesterday with a cisco router no prob on another section of my network.
All I need forwarded is;
UDP  137  NETBIOS Name Service
UDP  138  NETBIOS Datagram Service
UDP  139  NETBIOS Session Service

This is netbios over tcp/ip with windows 2000.

btw
UDP  135  DCE endpoint resolution - not nameservice
Thanks though :)
0
gheistCommented:
135 is important anyway...
check out www.sysinternals.com to see who binds where and why.
WINS is preferred way, or bridge for IPX or NetBEUI(not acttually routing anymore)
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

deadlastAuthor Commented:
with these 2 things on in sysctl.conf broadcast routing should be taking place.

net.inet.ip.forwarding=1 -- allow routing
net.inet.ip.directed-broadcast=1 -- allow broadcast routing

its not.
0
gheistCommented:
and second parameter must be set on all involved machines...
0
gheistCommented:
No problem. I hope asker found answer somewhere else on the web
0
Computer101Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.