The combination of a /0 CIDR mask and no gateway IP address makes a perfect sense - such a configuration results in adding a "connected" route to 0.0.0.0/0 via ether2 (as /ip route print can show you), so the router sends an ARP request for every IP it wants to send a packet to, except destinations for which more specific routes (with longer destination prefix masks) exist, and the actual gateway device responds with its own MAC address. So the ISP is unlikely to be willing to change this.
The only drawback of such an approach, but a significant one, is that your router needs a huge ARP table to cope with it.
First try whether it indeed works that way, and if it does, we may be able to find a way how to integrate it into your load distribution or failover setup.
How stable is the address you get? Does it change each time you disable and re-enable ether2 or you get the same assignment every time?
The combination of a
/0 CIDR mask and no gateway IP address makes a perfect sense - such a configuration results in adding a "connected" route to 0.0.0.0/0 via ether2 (as
/ip route print can show you), so the router sends an ARP request for every IP it wants to send a packet to, except destinations for which more specific routes (with longer destination prefix masks) exist, and the actual gateway device responds with its own MAC address. So the ISP is unlikely to be willing to change this.
"sorry i cant understand this"
How stable is the address you get? Does it change each time you disable and re-enable
ether2 or you get the same assignment every time?
yes i get same assighment every time
so how to solve this iam so confused?