You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My external interface gets a /56 (I changed the example script to use table 16 (dhcp))
2601:646:8301:c500::/56 from :: via fe80::22e5:2aff:feb8:14f dev eth2 metric 512 pref medium
2601:646:8301:c500::/56 from 2601:646:8301:c5f0::/60 via fe80::22e5:2aff:feb8:14f dev eth2 proto dhcp metric 512 pref medium
But I only get a "default from" what the local dhcp-pd server could fetch (a /60 in that range)
default from 2601:646:8301:c5f0::/60 via fe80::22e5:2aff:feb8:14f dev eth2 proto dhcp metric 512 pref medium
And then the /56 is just routable internally, but no default until this or some other dhcp-pd enabled server fetches another /60 AND then if it announced it, it would direct traffic back to itself.
shouldn't the "default from" be the entire /56 for the edge gateway? and an interior box not do source specific at all?
The text was updated successfully, but these errors were encountered:
My external interface gets a /56 (I changed the example script to use table 16 (dhcp))
2601:646:8301:c500::/56 from :: via fe80::22e5:2aff:feb8:14f dev eth2 metric 512 pref medium
2601:646:8301:c500::/56 from 2601:646:8301:c5f0::/60 via fe80::22e5:2aff:feb8:14f dev eth2 proto dhcp metric 512 pref medium
But I only get a "default from" what the local dhcp-pd server could fetch (a /60 in that range)
default from 2601:646:8301:c5f0::/60 via fe80::22e5:2aff:feb8:14f dev eth2 proto dhcp metric 512 pref medium
And then the /56 is just routable internally, but no default until this or some other dhcp-pd enabled server fetches another /60 AND then if it announced it, it would direct traffic back to itself.
shouldn't the "default from" be the entire /56 for the edge gateway? and an interior box not do source specific at all?
The text was updated successfully, but these errors were encountered: