Option to enable dnsmasq default gateway without adding 0.0.0.0/1 and 128.0.0.0/1 routes #250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, it is possible to enable default gateway in dnsmasq and add two routes by using
ROUTE_SPOOF
option, or to disable default gateway completely. I feel that there should be an option to define a default gateway and not to push out any other routes. That's what this pull request is about.I moved this part of a functionality out of
ROUTE_SPOOF
to aDEFAULT_GATEWAY
option.At the same time it remains backward compatible. If anyone enables
ROUTE_SPOOF
it also pushes default gateway.Also, I attached a payload
net_over_wifi.txt
. It doesn't do anything besides forwarding all the trafic through P4wnP1 and WiFi. It's not hard to add some meaningful network MitM attacks on top of it.