syndicate-lang
/
syndicate-2017
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
The version of Syndicate current at the conclusion of Tony Garnock-Jones's PhD research, end-of-2017/start-of-2018.
68 Commits 30 Branches 3 Tags 44 MiB
Racket 79.4%
JavaScript 15.8%
Haskell 1.7%
JetBrains MPS 1.5%
HTML 0.9%
Other 0.7%
Go to file
Tony Garnock-Jones e400c1703a stockholm no longer has vboxnet0. 2016-01-28 15:30:41 -05:00
.gitignore Initial commit 2014-06-15 21:16:14 -04:00
Makefile Friendlier makefile contents 2016-01-27 22:06:24 -05:00
README.md README 2015-10-17 21:11:55 -04:00
TODO.md A bug 2015-07-09 14:04:40 -04:00
arp.rkt Initial work towards migration from minimart to prospect-monolithic 2016-01-23 20:14:31 -05:00
checksum.rkt Tweaks to logging 2014-06-16 17:51:37 -04:00
configuration.rkt Initial work towards migration from minimart to prospect-monolithic 2016-01-23 20:14:31 -05:00
demo-config.rkt stockholm no longer has vboxnet0. 2016-01-28 15:30:41 -05:00
dump-bytes.rkt Initial commit 2014-06-15 21:16:14 -04:00
ethernet.rkt Initial work towards migration from minimart to prospect-monolithic 2016-01-23 20:14:31 -05:00
fetchurl.rkt Update fetchurl.rkt for prospect-monolithic. 2016-01-27 22:15:14 -05:00
idle.rkt Entrypoint for simply idling the stack 2015-10-17 20:33:51 -04:00
ip.rkt Name process behaviour procedures. 2016-01-27 21:46:09 -05:00
main.rkt Enable "webserver" 2016-01-27 21:51:51 -05:00
port-allocator.rkt Name process behaviour procedures. 2016-01-27 21:46:09 -05:00
tcp.rkt Implement TCP_USER_TIMEOUT, ish. 2016-01-28 14:24:05 -05:00
udp.rkt UDP. 2016-01-23 21:59:33 -05:00

README.md

TCP/IP Stack

Linux Firewall Configuration

Imagine a setup where the machine you are running this code has IP 192.168.1.10. This code claims 192.168.1.222 for itself. Now, pinging 192.168.1.222 from some other machine, say 192.168.1.99, will cause the local kernel to receive the pings and then forward them on to 192.168.1.222, which because of the gratuitous ARP announcement, it knows to be on its own Ethernet MAC address. This causes the ping requests to repeat endlessly, each time with one lower TTL.

One approach to solving the problem is to prevent the kernel from forwarding packets addressed to 192.168.1.222. To do this,

sudo iptables -I FORWARD -d 192.168.1.222 -j DROP