Timeline for Problem with longest prefix matching
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2018 at 12:52 | comment | added | Tomasz Pala | Serious engineer sometimes simply needs to join two (or more...) networks with colliding address spaces, both administered by someone else. I myself had to provide interconnectibility between 3 (yes, three) separate networks working in single company (sic!). With one uncooperative administrator, second incompetent and third unknown (entirely missing). Their networks used entire 192.168/16 and 10/8 ranges, with no central host management. In such situation you can't do anything more than NAT into 172.16/12 space to get this working ...and leave the problem of 4 networks to someone else. | |
| Jun 6, 2018 at 12:13 | comment | added | Zac67♦ | Sorry, no.This isn't anything that any serious engineer should want to work with. The several ways were referring to the approaches to handle the general ARP problem (proxy ARP, static ARP). | |
| Jun 6, 2018 at 11:42 | comment | added | Tomasz Pala | ARP tables are per-interface, but indeed, querying the appropriate interface needs some attention when these networks are directly attached. As for the several ways - you might want to elaborate them. | |
| Jun 6, 2018 at 11:04 | comment | added | Zac67♦ | There are several ways to work your way around getting this to work, not necessarily using policy-based routing and a stateful firewall (you'd also need to take care of "local" ARP). All of these should be avoided though since sooner or later they drop on your feet. | |
| Jun 6, 2018 at 8:34 | history | answered | Tomasz Pala | CC BY-SA 4.0 |