Use our hostname/TID port when sending a request, not our next_hop
authorJennifer Richards <jennifer@painless-security.com>
Fri, 25 May 2018 15:59:57 +0000 (11:59 -0400)
committerJennifer Richards <jennifer@painless-security.com>
Fri, 25 May 2018 15:59:57 +0000 (11:59 -0400)
commit3ac8884f3c6f6562211484ef469e15a3be1c565c
treee9e43b8fb4d1770d0a0b8032a892761bf99723b3
parentfe3b5cb31ab0d19c2ead6465f82ceb749bf05b75
Use our hostname/TID port when sending a request, not our next_hop

Before this, we set the next_hop to ourselves for local routes, then
simply forwarded the next_hop to our peers in update messages. That is
incorrect - we need to fill in our own hostname/TID port every time, not
send the next_hop we forward to.

Also fixes a few port name / signed int changes that really belonged in
the previous commit.
tr/tr_main.c
tr/tr_trp.c
trp/trp_route.c
trp/trps.c