NAT is modelled but unreachable, and a ping is not translated even with rules #1366
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1366
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NAT is modelled end to end and no lab can use it. Two defects, one behind the other.
engine/nat.jsmodels static one-to-one, dynamic pools and PAT, with a live translation table and ageing.Simulatorcalls it on the way out and back in and emitsnat-dropwhen a rule cannot translate. Butconfig.nathad no writer anywhere — not the CLI, not the UI, not the server, not a catalogue spec — so_isNat()was always false.docs/SIMULATION.mdrecorded it plainly: "There is noip nat inside/outside, noip nat inside source. Rules come fromconfig.nat.rulesin the topology JSON."Behind that, the data path had its own hole. Both hooks began:
An ICMP echo has no
l4— the engine keeps it inframe.icmp— so a ping crossed a NAT router untouched evenwith rules in the file. The docs carried this as "Absent — important": "a ping across a NAT box is not
translated". That is the first test anybody runs.
What must be true instead
validateRule()so the console and the wire cannot disagree;show ip nat rules | translations | statisticsreading the engine's own state, distinguishing nothing hascrossed from traffic crossed and nothing needed translating;
show running-config, pools before the rules that use them.