I created a Fedora machine and could replicate this and have created a [github issue for it][1]
@philip_rhoades if we could move the conversation on this bug to this issue it would help tracking and resolution of this issue - thanks again for finding and flagging it up. Cheers.
[1]: Fedora - 'test_avoid_beacon seek_peers 2' panicked · Issue #257 · maidsafe-archive/crust · GitHub
I just got up and was about to create a third test Fedora 22 x86_64 machine (kvm) to confirm that it wasn’t some problem that I had somehow duplicated on both my current working machines - you beat me to it! I will join the github discussion . .
Thanks,
Phil.
You should NEVER use curl with sudo. Curl itself is completely insecured and easily hijack.
Same goes for sudo pip install pythonwhatever.
Yeah, I was on the first nightly 1.4 I updated to the latest build and now it work fine.
Tested Crust on Linux Mint 17.2 Cinnamon 64-bit, after updating rust nightly, pulling, cleaning, updating, building, exporting, and testing ( 
), success:
running 20 tests
test beacon::test::test_avoid_beacon … ok
test beacon::test::test_beacon … ok
test bootstrap_handler::test::duplicates … ok
test bootstrap_handler::test::max_contacts … ok
test bootstrap_handler::test::oldest … ok
test bootstrap_handler::test::prune … ok
test bootstrap_handler::test::serialisation … ok
test config_utils::test::read_config_file_test … ok
test connection_manager::test::bootstrap … ok
test connection_manager::test::bootstrap_off_list_connects … ok
test connection_manager::test::bootstrap_off_list_connects_multiple … ok
test connection_manager::test::connection_manager … ok
test connection_manager::test::connection_manager_start … ok
test connection_manager::test::network … ignored
test getifaddrs::test::test_filter_loopback … ok
test getifaddrs::test::test_getifaddrs … ok
test tcp_connections::test::test_multiple_nodes_small_stream … ok
test tcp_connections::test::test_small_stream … ok
test test::check_rust_unit_testing_is_not_parallel … ok
test transport::test::test_ord … ok
test result: ok. 19 passed; 0 failed; 1 ignored; 0 measured
Thanks everyone for keeping up the work!
It seems that:
Fedora-Live-Xfce-x86_64-22-3.iso
might be the problem that I have . . :
P.
Running Arch Linux with Rust 1.4 nightly.
CRUST
cargo test export RUST_TEST_THREADS=1
Compiling crust v0.2.3 (file:///run/media/Andromedia/git/maidsafe/crust)
src/beacon.rs:199:17: 199:36 error: no method namedset_broadcastfound for typestd::net::udp::UdpSocketin the current scope
src/beacon.rs:199 try!(socket.set_broadcast(true));
^~~~~~~~~~~~~~~~~~~
:1:1: 6:48 note: in expansion of try!
src/beacon.rs:199:5: 199:38 note: expansion site
src/beacon.rs:199:17: 199:36 error: no method namedset_broadcastfound for typestd::net::udp::UdpSocketin the current scope
src/beacon.rs:199 try!(socket.set_broadcast(true));
^~~~~~~~~~~~~~~~~~~
:1:1: 6:48 note: in expansion of try!
src/beacon.rs:199:5: 199:38 note: expansion site
error: aborting due to previous error
Build failed, waiting for other jobs to finish…
error: aborting due to previous error
Could not compilecrust.
When I do the exercise on a Docker image instead of the VM built from the XFCE spin (Desktop) - things work as they are supposed to (as people have found with other spins) - I have no idea why a different Desktop should cause a problem when prepending “cargo test” with "RUST_TEST_THREADS=1 " . .
P.
Not related to above posts, but I noticed some changes in the crust master branch today and I have to come here to shout that
Large scale test of the network has never been closer 
Thanks for the hard work and good week-end to the team !
It’s actually in place now, so we need to just slip in hole punching and a couple of tidy ups to upnp (add igd v2) and external endpoint detection and we are set there. 
That doable before the end of this month?
We moved away from timescales, so it’s up to what we can get in planning this week (spring planning) really. There is a broad range of things happening at the moment with devs in nearly every lib. So the balance of resource’s is tight and it’s not easy to say what works in what time, but sprints are now more accurate (he says after coming out of an extended sprint delayed by a week ). In saying that this is not a huge next step, it’s more tidy up.
Been meaning to ask.
Is there any issues with having 2 routers with nat (1 on ISP connection and one behind that)
Would routing work if one has VPN at the router level. (Slow I know, but would it work)
Hole punching will work through this with some luck (unless there are lots of symmetric nat devices there). Networking is a science full of tricks and changes that can make anything work and make anything break Generally it should be OK unless there is some layer 2 switching with broadcasts across lans or crazy stuff like that (kind thing corporates do a lot).
In terms of VPN, I think that would be OK, but could also be less secure as a vpn is easier to track.
Tell me about it 
Thats cool, a lot of people in Australia have started to use VPNs because of data retention surveillance by the government. I expect that SAFE will remove the need.
I really hope so, it’s madness, soon they will ddt the mossies, that’s how bonkers it is. I hope SAFE will end this crazy holding back education kinda thing.
We used to do that all those years ago.
But yes our government is really quite crazy, they know nothing about the internet, but introduce these half arse laws that raise costs and turn us into a police state that the old USSR would love to have had. They now are trying to take legislative control over the ISP infrastructure and dictate how these private companies (ISP) are to build their networks. Yet the idiot trying to legislate admits he never has used a computer.