okay heres the problem =
i got 2 router, the first router with ip (10.10.1.1) and my second router is (10.10.1.1). the ip will be conflict and the router will disconnect.......my question is how to avoid the ip conflict....???
Ehm, there's no sensible way for this to work. Don't use the same ip address for two devices - this will not work and that's good so.
The only way is to make sure that those two devices don't see each other network wise. But I would refrain from doing so in a normal network...
What's the intention behind this?
Best regards,
Christian Meis
The only way is to make sure that those two devices don't see each other network wise. But I would refrain from doing so in a normal network...
What's the intention behind this?
Best regards,
Christian Meis
once again thx for quick respons cmit, okay ive got this problem on friday and its make all the internet connection goes crazy:evil: and i was trying to found out what in the hell went wrong with my network, after 3 hours figuring out then i found the mystery of it , some one in my office was using the same ip with the mikrotik router... 
thats why i want to know how to avoid ip conflict.....is there anyway..????
thx
thats why i want to know how to avoid ip conflict.....is there anyway..????
thx
I don't think this can reliably be avoided in an office environment with sensible amount of work.
The only thing I could think of is to use static ARP on every device in the network or using a managed switch with some severy security settings/MAC binding.
In any other situation there will always be some possibility to create problems with duplicate ip addresses.
But having a static-ARP only network would be an admins' nightmare. And if saying "static-ARP only" I DO mean EVERYTHING (routers, workstations, print servers, ...)...
Best regards,
Christian Meis
The only thing I could think of is to use static ARP on every device in the network or using a managed switch with some severy security settings/MAC binding.
In any other situation there will always be some possibility to create problems with duplicate ip addresses.
But having a static-ARP only network would be an admins' nightmare. And if saying "static-ARP only" I DO mean EVERYTHING (routers, workstations, print servers, ...)...
Best regards,
Christian Meis
hmm....this is a very classic problems...
its true that using a manageable switch will help to solve this problem, but this will yield to a high investment cost...
using a hotspot with universal client is also will not work (at least that's what i thought) coz what his talking here is an office environment where not everybody using the internet
is this the basic failiure of IPv4 ?
is this problems gonna be solve if we use IPv6 ?
its true that using a manageable switch will help to solve this problem, but this will yield to a high investment cost...
using a hotspot with universal client is also will not work (at least that's what i thought) coz what his talking here is an office environment where not everybody using the internet
is this the basic failiure of IPv4 ?
is this problems gonna be solve if we use IPv6 ?
-
-
virtualmystic
Frequent Visitor
- Posts: 77
- Joined:
- Location: Lahore, pakistan
well, im not sure its a good idea, but here it goes,subnet your network department wise..say 6 departments and 6 subnets.. then have 6 different lan interfaces on you MT for each department..keeping subnets and lans saperate will make it manageable and conflict in one subnet will not disturb other..
regds,
Asad
regds,
Asad
-
-
virtualmystic
Frequent Visitor
- Posts: 77
- Joined:
- Location: Lahore, pakistan
the *only* way to avoid IP conflicts is to give each user their own physical or virtual lan. A router can only block what goes through it, it can never block what goes on between the hosts on the same physical lan. For that you need some way to separate them so the packets cannot flow directly between them. So either a dedicated physical or virtual lan will work.
he's right , but im talking about another metter , sometimes one from ur client put the server ip so that well make conflict if u want to resolve this problem put that chain=postrouting src-address=217.65.150.5 action=change-ttlthe *only* way to avoid IP conflicts is to give each user their own physical or virtual lan. A router can only block what goes through it, it can never block what goes on between the hosts on the same physical lan. For that you need some way to separate them so the packets cannot flow directly between them. So either a dedicated physical or virtual lan will work.
new-ttl=set:128 that what i was talking about