- Use reliable transaction submission methods where available
- Update text to describe the functions (esp. xrpl.js 2.0 stuff)
- Move Send XRP code samples to subfolders by language for consistency
with other tutorials
- Removes lodash dependecy for web version
- Uses the new generateFaucetWallet() API method
- Make 'issue a token' code capable of running in-browser or in Node.js
without modification
- Make sample code node.js compatible (need to uncomment a few lines)
- Wire up interactive tutorial bits to actually run the relevant code
- Edit instructions slightly, add notes on Require Destination Tags
- Fix bugs in submit and verify helper function
- Tweak tutorial and placement of helper function
- Finish drafting sample code
- Put sample code into tutorial
replacing --forward-port directions with --add-port
I'm new to firewalld, but I think the purpose of the [`--add-forward-port`](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-port_forwarding) is if it's served internally on a different port.
It very well may work as an open-port, maybe if there's a bridged network? (i.e., `docker`); I didn't have luck with it. I came to the page to see what port I needed to open with the command I'm presenting, but tried this approach first. I didn't get any peer connections. When I switched over to just opening the port as `51235/tcp` I quickly saw peers.
I am also new to running a node, and this particular one was running for around 2 weeks without peering which may have caused some difference.
I do also think this file could remain the same name as it's capturing it's intent.
Co-authored-by: Rome Reginelli <mduo13@gmail.com>
typo
Update content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md
Update content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md
`--add-port` not `--add-source-port`
add note for virtual firewall
Co-authored-by: Rome Reginelli <mduo13@gmail.com>
