Hi Greg,
On Wed, Sep 25, 2019 at 3:33 PM George Neuner wrote:
>
> Hi David,
>
> On 9/25/2019 1:08 AM, David Storrs wrote:
> What you are overlooking is that UDP is a level 4 [end-to-end] protocol,
> but you are trying to get level 3 [routing] information.
>
> Neither UDP nor TCP normally
Hi David,
On 9/25/2019 1:08 AM, David Storrs wrote:
udp-receive! is giving me unexpected results when my local machine ->
router -> server shows the UDP port of the process running on the
local machine instead of the one from the router. I'm not sure how to
get the router's port instead.
NAT
udp-receive! is giving me unexpected results when my local machine ->
router -> server shows the UDP port of the process running on the
local machine instead of the one from the router. I'm not sure how to
get the router's port instead.
The AWS server does this:
(define-values (len
3 matches
Mail list logo
