17 Nov
2021
17 Nov
'21
3:34 p.m.
Well, it's in doc/config.txt. And actually it says something I had forgotten. If you
don't specify a cert it defaults to decnet.pem. So it has a cert name either way.
I assume that file decnet.pem doesn't actually exist. So you should get an error
message, and "cert decnet.pem doesn't exist" would be a lot clearer.
Meanwhile, the configuration file details are described pretty carefully in
doc/config.txt; reviewing that can be useful.
On the subject of the qmax spec, yes, for the moment that's a good idea. I need to
implement congestion control one of these days, the algorithms are documented but I
haven't gotten around to that yet.
paul
On Nov 17, 2021, at 9:28 AM, Brian Hechinger <wonko
at 4amlunch.net> wrote:
Yeah, I agree that if no cert is specified it shouldn't enable HTTPS. That's what
I assumed would happen. :)
-brian
On 17/11/21 14:26, Paul Koning wrote:
> I think so. It will obviously fail later on, but it looks like the bind happens
before it realizes that it has no cert. If you don't want https, add --https-port 0.
>
> I suppose I should force that if no cert is specified, that would be logical.
>
> paul
>
>> On Nov 17, 2021, at 9:23 AM, Brian Hechinger <wonko at 4amlunch.net
<mailto:wonko at 4amlunch.net>> wrote:
>>
>> Even without a cert specified?
>>
>> -brian
>>
>> On 17/11/21 14:06, Paul Koning wrote:
>>> You have both http and https enabled (both are enabled by default) so it will
try to bind ports 8000 and 8443.
>>>
>>> paul
>>>
>>>> On Nov 17, 2021, at 8:09 AM, Brian Hechinger <wonko at 4amlunch.net
<mailto:wonko at 4amlunch.net>> wrote:
>>>>
>>>> Oops, I knew I forgot something. Trying to rush the email out.
>>>>
>>>> router.conf:
>>>>
>>>> system --identification "PyDECnet, A52RTR - Quarteira,
Portugal"
>>>> routing 52.1023 --type l2router
>>>> logging console
>>>> @nodes.conf
>>>> circuit mul-29-2 Multinet --mode connect --destination 82.70.71.174
--dest-port 9608 --cost 4 --t3 180
>>>> #circuit eth-0 Ethernet internal --mode pcap --cost 1
>>>>
>>>> http.conf:
>>>>
>>>> http --api --insecure-api
>>>>
>>>> -brian
>>>>
>>>> On 17/11/21 13:06, Wilm Boerhout wrote:
>>>>> Config file please ?
>>>>>
>>>>> From: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at
Update.UU.SE> <owner-hecnet at Update.UU.SE> <mailto:owner-hecnet at
Update.UU.SE> On Behalf Of Brian Hechinger
>>>>> Sent: Wednesday, November 17, 2021 2:02 PM
>>>>> To: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
>>>>> Subject: [HECnet] PyDECnet setup
>>>>>
>>>>> That other thread is getting out of hand so I'll start a new
one.
>>>>>
>>>>> I've started getting this error:
>>>>>
>>>>> Exception in thread https:
>>>>> Traceback (most recent call last):
>>>>> File "/usr/lib/python3.8/threading.py", line 932, in
_bootstrap_inner
>>>>> self.run()
>>>>> File "/usr/lib/python3.8/threading.py", line 870, in run
>>>>> self._target(*self._args, **self._kwargs)
>>>>> File
"/usr/local/lib/python3.8/dist-packages/decnet-1.0.592-py3.8.egg/decnet/http.py",
line 103, in serverstart
>>>>> httpd = DECnetMonitor (server_addr, DECnetMonitorRequest,
>>>>> File
"/usr/local/lib/python3.8/dist-packages/decnet-1.0.592-py3.8.egg/decnet/http.py",
line 126, in __init__
>>>>> self.socket = source_addr.create_server ()
>>>>> File
"/usr/local/lib/python3.8/dist-packages/decnet-1.0.592-py3.8.egg/decnet/host.py",
line 399, in create_server
>>>>> sock = self.bind_socket (self.listen_family)
>>>>> File
"/usr/local/lib/python3.8/dist-packages/decnet-1.0.592-py3.8.egg/decnet/host.py",
line 387, in bind_socket
>>>>> sock.bind (self.sockaddr)
>>>>> OSError: [Errno 98] Address already in use
>>>>>
>>>>> Neither lsof nor netstat show that port in use. Doesn't matter if
I use the default 8000 or set something different, I get that every time.
>>>>>
>>>>> I didn't always though. This was running fine before I tried
adding the circuit for ethernet access.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> -brian
>>>>>
>>>
>