[solved] some interfaces in one IP segment

RouterOS General
1 
/ interface vlan
add name="v16" mtu=1500 arp=proxy-arp vlan-id=16 interface=eth1 disabled=no
add name="vlan1049" mtu=1500 arp=proxy-arp vlan-id=1049 interface=eth1 disabled=no

/ ip address
add address=192.168.0.250/24 network=192.168.0.0 broadcast=192.168.0.255 interface=eth1 disabled=no
add address=192.168.16.250/24 network=192.168.16.0 broadcast=192.168.16.255 interface=v16 disabled=no
add address=192.168.16.250/32 network=192.168.16.245 broadcast=192.168.16.245 interface=vlan1049 disabled=no

192.168.16.245 have 192.168.16.250 as its default gateway.

I can ping 192.168.16.245 (on interface vlan1049) from MT and from 192.168.0.0/24, but i can’t ping it from the rest of 192.168.16.0/24.
What is wrong with proxy-arp? What should i do to make the MT answer ARP-requests on other interfaces from the same IP segment?

2

any suggestions?..

3

normis, uldis, help please!..

4

from manual:

The router with enabled proxy ARP always answer with its own MAC address if it has a route to the destination.
This behaviour can be usefull, for example, if you want to assign dial-in (ppp, pppoe, pptp) clients IP addresses from the same address space as used on the connected LAN.

does dial-in and vlan has fundamental differences?..

5

You’re having the same IP address on 2 different interfaces

/Henrik

6

but all works fine, except that users within one IP segment cannot communicate with each other

7

maybe power fault (and next reboot of MT) helped, but now all works fine, proxy arp proxies =)

how to test: on neighbour MT Tools → IP Scan, interface → connected to main MT, address range → addresses behind the router.
the result should be all IP addresses, but with the same MAC address of main MT

Diganet
:stuck_out_tongue: