Add Comment

You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog routing Windows networks


Re: routing Windows networks
Posted by eric (194.2.xx.xx) on Tue 14 Feb 2006 at 08:56
Linux (the kernel), and associated tools, have pretty much one of the best feature sets for building routers

I'm ok with you, I know that linux and all the network stack is ok to do much of the things you need.

But is the kernel really at the same nivel than Cisco IOS (it's an example). Aren't they some features that you can't do ? (I'm thinking about some articles I read, but I can't remember exactly the features in question, maybe something like 'dynamic port opening' - sorry if I say something completely stupid !)

I think the advantage of hardware routers are in the ASICS which are fast, and the realiability of the hardware (compared to a PC-based router). I talked about Cisco, because 1) I work in public administration and we can't buy what we want, we can't buy a soekris hardware to put a linux per example and 2) people here (colleagues and chiefs) are used to rely on well-known-material (hard or soft) (nevermind the price... and i'm really sorry about that too !) and not on an obscure linux/BSD router. It's a little bit 'stupid' but I can't do much on that.

I talked about openbsd because i really like PF, but if necessary i'll dig into the obscure (for me) syntax of iptables one more time. Moreover, i don't really know if PF is as complete as NETFILTER.

Now comes a more detailed explanation of my problem :

we got a 192.168.2.0/23 ip range full of pc, printers with an adsl/intranet connection. Win2000 and 2003 domain controllers, file servers, printing servers and f*%! Exchange 2000 are also in this LAN.
we got a 192.168.1.0/24 ip range for administrative use : an adsl/intranet connection only for the technical team (to join the other sites) and network switches are here.

The problem is : we are going out of ip addresses in the main LAN.

The idea is :put 40-60 machines in the 1.0/24 LAN, but let them continue to access all the services (file sharing, printing, and Outlook in MAPI mode, internet of course) like before. The problem is : services must stay in the 2.0/23 LAN. DNS servers are the DCs so they also stay in the 2.0/23 LAN.

So I have started working on that with an openbsd installation. I got two simple rules that let the traffic go in and out from one subnet to the other. DNS works, Internet works, and even Outlook/MAPI works. But the file sharing (and printing i think) don't work !
I have search for a little bit of documentation about this problem but haven't found anything for the moment. I know the problem with pre-win2000 was Netbios and the use of broadcast, but with win2000/XP i thought it had disappeared.

that's my problem, so if someone got an idea...

:eric: http://blog.sietch-tabr.com


Username:Anonymous
Title:
Your Comment:

Posting Format:

 

Inappropriate comments will be removed.

Some help on entry formatting is available

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search