Re: [tor-relays] TransPort: Convert iptables to pf

2016-12-28 Thread diffusae
Hi! On 29.12.2016 00:16, grarpamp wrote: > On Wed, Dec 28, 2016 at 5:07 PM, diffusae wrote: >> I needed the buildworld to create a jail with ezjail. > > If you break some of these down all they do is lay down > an installworld in DESTDIR and run jail on it. Too heavy > for some who tar up / and

Re: [tor-relays] TransPort: Convert iptables to pf

2016-12-28 Thread grarpamp
On Wed, Dec 28, 2016 at 5:07 PM, diffusae wrote: > I needed the buildworld to create a jail with ezjail. If you break some of these down all they do is lay down an installworld in DESTDIR and run jail on it. Too heavy for some who tar up / and /usr and lay them down instead. Or bsdinstall into th

Re: [tor-relays] TransPort: Convert iptables to pf

2016-12-28 Thread diffusae
Hi! Thanks a lot for your hint. On 28.12.2016 19:52, grarpamp wrote: > Need to buildworld is rare and usually noted in UPDATING > and kernel config files. make buildkernel will be much faster, > and even faster if you strip out junk you don't need from the > kernel config, which also speeds boot

Re: [tor-relays] TransPort: Convert iptables to pf

2016-12-28 Thread grarpamp
On Wed, Dec 28, 2016 at 11:07 AM, diffusae wrote: > If you try a "build world" an the RPi itself, it took more that three > days. ;-) Need to buildworld is rare and usually noted in UPDATING and kernel config files. make buildkernel will be much faster, and even faster if you strip out junk you d

Re: [tor-relays] TransPort: Convert iptables to pf

2016-12-28 Thread diffusae
Hi! On 26.12.2016 18:17, Corl3ss wrote: > diffusae: >> I've tried the same configuration with FreeBSD11 for armv6 (RPI-B), with >> and without a jail and it only works locally and also dropped all other >> network connections. I am not sure, if something is missing in RPI >> ISO-Images Snapshots

Re: [tor-relays] Relay is missing Running flag in the consensus

2016-12-28 Thread demfloro
Hello again, Bwauths started voting again for my exit relay[1], looks like the problem disappeared. Though longclaw is still inaccessible from relay[1]: 10:16:14-root@bsd1 ~ # traceroute 199.254.238.53 traceroute to 199.254.238.53 (199.254.238.53), 64 hops max, 40 byte packets 1 192.168.240.102