[HECnet] PyDECnet setup

[Brian Hechinger]

Yes, I name them reasonable things so that I don't need to remember 
stupid crap like enp0s2 is networkA and enp0s04 is networkB. :-D

-brian

On 17/11/21 14:05, Wilm Boerhout wrote:
>
> I see. It is your privilege to name your network devices 😊
>
> So then it must be one of the other lines, most suspect is the 
> multinet line of course. I have no experience with that, I’m using 
> DDCMP lines for my point-to-point connections to other areas.
>
> But you say it has worked before? New version? Then we must wait until 
> Paul finds the time to respond.
>
> *Wilm*
>
> *From:* owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> *On 
> Behalf Of *Brian Hechinger
> *Sent:* Wednesday, November 17, 2021 2:42 PM
> *To:* hecnet at Update.UU.SE
> *Subject:* Re: [HECnet] PyDECnet setup
>
> All the processes are stopped. I don't see anything listening on those 
> ports.
>
> internal is the name of the interface., but that line is commented out 
> currently because I thought that was the cause (the only thing I added 
> between it working and it not working) but even commented out that 
> doesn't seem to have fixed it.
>
> -brian
>
> On 17/11/21 13:31, Wilm Boerhout wrote:
>
>     Are you sure all PyDECnet processes are stopped at the point where
>     you trying to start?
>
>     Other thing, where is the internal argument for the ETH-0 circuit
>     documented? Shouldn’t that be the Linux device name where you run
>     pcap?
>
>     Assuming that the error occurs when you uncomment the “circuit” line
>
>     *Wilm*
>
>     *From:* 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:09 PM
>     *To:* hecnet at Update.UU.SE
>     *Subject:* Re: [HECnet] PyDECnet setup
>
>     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 <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
>         *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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20211117/dcd57d8b/attachment-0001.htm>