We have several PCs on the 192.168.0.x net and some others on 10.0.100.x. The two networks are SEPARATED, no cables, switches, etc. connect twe two nets.
We want to put a MT Router in the middle to connect the two.
We want to use bridging and we don't want any of the PC users to have to touch any setting to see the new connected PCs.

PCs 192.168.0.x must see PCs 10.0.100.x as 192.168.0.x and vice versa, with braodcast working (MS Sharing /smb/;Games,etc.)

e.g. we need the bridge to mask? the 192.168.0.x hosts as 10.0.100.x hosts when looking from 10.0.100.x side and mask 10.0.100.x hosts as 192.168.0.x hosts when looking from 192.168.0.x side. All this, if possible, with broadcast woking.

How can we do this Thanks. If this is not implemended please developers implemend it, thanks.


Also, we have a problem with one of the ADSL lines here - it's some kind of ADSL modem, that has a builtin NAT but whenever upload goes up either the net connection stops working and we have to restart the ADSL modem, or the download goes down to zero. How can we fix these problems

THANK YOU in advance and long live MikroTik

I think it is possible to do that using ip firewall nat, although this would only apply to IP traffic (if that SMB is not nun on NetBEUI, which nowadays is very unlikely; and if you do not have any IPX/SPX equipment, like legacy Novell Netware products (I think the new NetWare abandoned the IPX/SPX), then everything should work quite fine)

We are running TCP/IP only. We also need our TCP/IP braodcasts(packets with funny destination such as 255.255.255.255, etc. destined to ALL hosts in the network).

I tried the NAT of course but id dind't work (Bridge mode) (p firewall nat).

I managed to make it ALMOST work by disabling the Bridhe and adding IP addresses to the Router and then NAT-ing them but THE VERY NEEDED BRAODCASTS couldn't get through !! PLEAZE HELP.

I've found something about this when I searched "braodcast":

http://forum.mikrotik.com//viewtopic.ph ... =broadcast
(Broadcast traffic in routed network)

there sten suggests something like this:

No idea if it will work, i havent really tested it.

Say you have 192.168.1.0/24 on ether1 and 192.168.2.0/24 on ether2.
Server is connected on ether1, desktop on ether2.

Something along the lines of :

/ ip firewall dst-nat add dst-address=192.168.2.255/32 dst-port=137 protocol=udp in-interface=ether2 action=nat to-dst-address=192.168.1.255

/ ip firewall dst-nat add dst-address=192.168.1.255/32 dst-port=137 protocol=udp in-interface=ether1 action=nat to-dst-address=192.168.2.255

Add for all necessary ports of course.
Please let me know if it works or not

I'll try it...

hello,

The two networks are SEPARATED, no cables, switches, etc. connect twe two nets.

Why not just put a switch between the two networks?

Sam

hello,

The two networks are SEPARATED, no cables, switches, etc. connect twe two nets.

Why not just put a switch between the two networks?

Sam

Becouse IP addresses ranges used by clients are different and I don't want to touch any client configuration that's already established (by their ISP) (because internet will stop working for them).

Are you talking about the clients ip, dns, and gateway configuration? Can you just add a gateway on both networks on the same MT box? You can have more than 1 IP on an interface. Maybe im missing something...

Sam

Are you talking about the clients ip, dns, and gateway configuration? Can you just add a gateway on both networks on the same MT box? You can have more than 1 IP on an interface. Maybe im missing something...

Sam

I don't want to bother people with adding configs, besides their ISP admins will come to their home and see the configs and I don't want that. Adding IP addresses will work without routing. Adding Gateways will work without a bridge between the two nets. What we need is a bridge that translates IP addresses. For some reason I could NOT make it work with ip firewall nat. Later I may post the configs I tried... I have to go through them some more times. Im using VMWare as a test host+bridge+network. Also we need those braodcast packets translated along with the direct host2host ones.