Package Details: core 9.1.0-2

Git Clone URL: https://aur.archlinux.org/core.git (read-only, click to copy)
Package Base: core
Description: Tool for building virtual network simulations
Upstream URL: https://github.com/coreemu/core/
Keywords: emulator
Licenses: BSD
Submitter: tom5760
Maintainer: caier
Last Packager: caier
Votes: 10
Popularity: 0.000022
First Submitted: 2010-10-27 16:52 (UTC)
Last Updated: 2024-11-07 00:26 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

TrialnError commented on 2024-07-06 17:39 (UTC)

Will push the updated PKGBUILD.
But it still fails for me with

ERROR Missing dependencies:
    poetry>=0.12
    poetry-plugin-export<2.0.0,>=1.6.0 -> poetry<3.0.0,>=1.8.0 -> keyring<25.0.0,>=24.0.0
    poetry>=0.12
    keyring<25.0.0,>=24.0.0
    poetry>=0.12
    dulwich<0.22.0,>=0.21.2
    poetry>=0.12
    poetry-plugin-export<2.0.0,>=1.6.0 -> poetry<3.0.0,>=1.8.0 -> dulwich<0.22.0,>=0.21.2

And I don't currently understand why. python-poetry, python-poetry-plugin-export, python-keyring and python-dulwich are declared in the PKGBUILD. With versions fitting the range?

vedranmiletic commented on 2024-07-05 11:26 (UTC)

FWIW, upstream released version 9.1.0 with fixes for Python 3.11+.

TrialnError commented on 2024-06-09 21:20 (UTC)

PKGBUILD got adjusted in some parts (PEP 517 and new deps), but has one big problem. Upstream is rather restrictive about version pinning. And some of the Arch packages are above.

MarsSeed commented on 2023-08-11 22:05 (UTC)

Also don't use the deprecated dephell to make a deprecated executable setup.py.

Instead, make the build follow the PEP 517 conformant build and install procedure outlined in Arch Wiki.

MarsSeed commented on 2023-08-11 22:02 (UTC)

Please add a meaningful description in pkgdesc instead of pasting the misleading expansion of the CORE acronym.

kadotux commented on 2022-04-05 17:02 (UTC)

Fixed with the help from CORE development @ Discord!

Problem was two servers I had previously configured via GUI in session -> servers. Removing them fixed the problem, the session runs now as expected. Thank you all.

kadotux commented on 2022-04-05 15:54 (UTC) (edited on 2022-04-05 15:55 (UTC) by kadotux)

@Splork I don't think so, but I'm not entirely sure.

This is my /etc/nftables.conf:

#!/usr/bin/nft -f
# vim:set ts=2 sw=2 et:

# IPv4/IPv6 Simple & Safe firewall ruleset.
# More examples in /usr/share/nftables/ and /usr/share/doc/nftables/examples/.

table inet filter
delete table inet filter
table inet filter {
  chain input {
    type filter hook input priority filter
    policy drop

    ct state invalid drop comment "early drop of invalid connections"
    ct state {established, related} accept comment "allow tracked connections"
    iifname lo accept comment "allow from loopback"
    ip protocol icmp accept comment "allow icmp"
    meta l4proto ipv6-icmp accept comment "allow icmp v6"
    tcp dport ssh accept comment "allow sshd"
    pkttype host limit rate 5/second counter reject with icmpx type admin-prohibited
    counter
  }
  chain forward {
    type filter hook forward priority filter
    policy drop
  }
}

And iptables -L -vn:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination       
29799 29M LIBVIRT_INP all -- * * 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination
0 0 LIBVIRT_FWX all -- * * 0.0.0.0/0 0.0.0.0/0
0 0 LIBVIRT_FWI all -- * * 0.0.0.0/0 0.0.0.0/0
0 0 LIBVIRT_FWO all -- * * 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination
26837 3038K LIBVIRT_OUT all -- * * 0.0.0.0/0 0.0.0.0/0

Chain LIBVIRT_FWI (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- * virbr0 0.0.0.0/0 192.168.122.0/24 ctstate RELATED,ESTABLISHED 0 0 REJECT all -- * virbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable

Chain LIBVIRT_FWO (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- virbr0 * 192.168.122.0/24 0.0.0.0/0
0 0 REJECT all -- virbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable

Chain LIBVIRT_FWX (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- virbr0 virbr0 0.0.0.0/0 0.0.0.0/0

Chain LIBVIRT_INP (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67

Chain LIBVIRT_OUT (1 references) pkts bytes target prot opt in out source destination
0 0 ACCEPT udp -- * virbr0 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- * virbr0 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- * virbr0 0.0.0.0/0 0.0.0.0/0 udp dpt:68 0 0 ACCEPT tcp -- * virbr0 0.0.0.0/0 0.0.0.0/0 tcp dpt:68

/etc/hosts:

# Static table lookup for hostnames.

See hosts(5) for details.

127.0.0.1 localhost 127.0.1.1 LostArch

some random stuff, trying to make core working

::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters

And "ip link":

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

Is there anywhere else I could look?

Splork commented on 2022-04-05 15:37 (UTC)

@kadotux

so, to me this looks like the GUI is attempting to communicate with the daemon via port 50051 (that would go through the loopback interface), but for some reason they get a timeout.

Is you system configured in any way that would prevent connections between local processes on the loopback interface?

kadotux commented on 2022-04-05 15:31 (UTC)

Hi @tom5760:

Thank you! Installing inetutils actually fixed the issue for core-gui-legacy! The legacy interface is totally functional now. :)

Although I'm content with using the legacy interface, the problem persists on Python/Tk interface. Connection times out regardless if I run "core-daemon" with or without sudo, or run the systemd service "sudo systemctl start core-daemon". The do have different config folders (.coregui and .core) but I think I have similiar settings in both, that shouldn't be the issue.

Justo to recap, the when starting the session in Python interface I get an error popup titled "GRPC Exception", and terminal output from core-daemon is:

2022-04-05 18:23:40,266 - INFO - core-daemon:banner - CORE daemon v.8.2.0 started Tue Apr  5 18:23:40 2022
2022-04-05 18:23:40,796 - INFO - coreemu:_load_emane - using emane: 1.3.3
2022-04-05 18:23:40,866 - INFO - server:listen - CORE gRPC API listening on: localhost:50051
2022-04-05 18:23:40,867 - INFO - core-daemon:cored - CORE TLV API TCP/UDP listening on: localhost:4038
2022-04-05 18:23:45,939 - INFO - coreemu:create_session - created session: 1
2022-04-05 18:23:57,351 - INFO - session:set_state - changing session(1) to state CONFIGURATION_STATE
2022-04-05 18:26:06,421 - ERROR - _server:_call_behavior - Exception calling application: [Errno 110] Connection timed out
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/grpc/_server.py", line 443, in _call_behavior
    response_or_iterator = behavior(argument, context)
  File "/usr/lib/python3.10/site-packages/core/api/grpc/server.py", line 267, in StartSession
    session.distributed.add_server(server.name, server.host)
  File "/usr/lib/python3.10/site-packages/core/emulator/distributed.py", line 143, in add_server
    server.remote_cmd(f"which {requirement}")
  File "/usr/lib/python3.10/site-packages/core/emulator/distributed.py", line 72, in remote_cmd
    result = self.conn.run(
  File "/usr/lib/python3.10/site-packages/decorator.py", line 232, in fun
    return caller(func, *(extras + args), **kw)
  File "/usr/lib/python3.10/site-packages/fabric/connection.py", line 29, in opens
    self.open()
  File "/usr/lib/python3.10/site-packages/fabric/connection.py", line 636, in open
    self.client.connect(**kwargs)
  File "/usr/lib/python3.10/site-packages/paramiko/client.py", line 349, in connect
    retry_on_signal(lambda: sock.connect(addr))
  File "/usr/lib/python3.10/site-packages/paramiko/util.py", line 283, in retry_on_signal
    return function()
  File "/usr/lib/python3.10/site-packages/paramiko/client.py", line 349, in <lambda>
    retry_on_signal(lambda: sock.connect(addr))
TimeoutError: [Errno 110] Connection timed out

And from core-gui:

2022-04-05 18:23:45,915 - INFO - manager:add_canvas - creating canvas(1)
2022-04-05 18:23:45,940 - INFO - coreclient:create_new_session - created session: 1
2022-04-05 18:23:45,940 - INFO - coreclient:join_session - joining session(1)
2022-04-05 18:23:45,946 - INFO - manager:join - cleared canvases
2022-04-05 18:23:45,948 - INFO - manager:add_canvas - creating canvas(1)
2022-04-05 18:23:50,752 - INFO - coreclient:create_node - add node(n1) to session(1), coordinates(231.0, 349.0)
2022-04-05 18:23:53,360 - INFO - coreclient:create_node - add node(n2) to session(1), coordinates(396.0, 198.0)
2022-04-05 18:23:56,291 - INFO - interface:create_iface - create node(n1) interface(Interface(id=0, name='eth0', mac=None, ip4='10.0.0.20', ip4_mask=24, ip6=None, ip6_mask=64, net_id=None, flow_id=None, mtu=None, node_id=None, net2_id=None))
2022-04-05 18:23:56,291 - INFO - interface:create_iface - create node(n2) interface(Interface(id=0, name='eth0', mac=None, ip4='10.0.0.1', ip4_mask=24, ip6=None, ip6_mask=64, net_id=None, flow_id=None, mtu=None, node_id=None, net2_id=None))
2022-04-05 18:23:56,292 - INFO - interface:create_link - added link between n1 and n2
2022-04-05 18:26:06,425 - ERROR - app:show_grpc_exception - app grpc exception
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/core/gui/coreclient.py", line 425, in start_session
    result, exceptions = self.client.start_session(self.session, definition)
  File "/usr/lib/python3.10/site-packages/core/api/grpc/client.py", line 239, in start_session
    response = self.stub.StartSession(request)
  File "/usr/lib/python3.10/site-packages/grpc/_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/usr/lib/python3.10/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
    status = StatusCode.UNKNOWN
    details = "Exception calling application: [Errno 110] Connection timed out"
    debug_error_string = "{"created":"@1649172366.425347645","description":"Error received from peer ipv4:127.0.0.1:50051","file":"src/core/lib/surface/call.cc","file_line":905,"grpc_message":"Exception calling application: [Errno 110] Connection timed out","grpc_status":2}"

Nevertheless, thank you for help! I'm content with using the legacy interface but if anyone would like chip in as to why this error in Python interface is happening I would of course greatly appreciate!

tom5760 commented on 2022-04-05 13:59 (UTC)

Hey @kadotux:

started core-daemon service (tried via sudo sysctl start core-daemon and with core-daemon and with sudo core-daemon)

Just in case, can you also try systemctl start core-daemon.service?

This also jumped out at me:

stderr: vnoded[3]: 13:46:13.384703 forkexec[vnode_cmd.c:417]: execvp() failed for 'hostname': No such file or directory

Do you have a /usr/bin/hostname binary? If not, can you try installing the inetutils package?