yacy on openbsd
Dear group, is anyone running yacy on a openbsd box? I tested the latest one yacy on a 5.3 amd64 but didn't succeed. The only resource I found was: http://ventejuy.es/cgi-bin/post?p=11051522005289 (in Spanish!) but was unable to connect to localhost:8090 Thanks
Re: yacy on openbsd
On Sun, Aug 04, 2013 at 11:08:39AM +0300, Tony Berth wrote: > Dear group, > > is anyone running yacy on a openbsd box? > > I tested the latest one yacy on a 5.3 amd64 but didn't succeed. The only > resource I found was: > > http://ventejuy.es/cgi-bin/post?p=11051522005289 (in Spanish!) > > but was unable to connect to localhost:8090 > > Thanks > I did play with it from time to time, and it worked fine. Haven't looked at it recently. The main problem is that it's a ridiculous, ineffective piece of Java bloatware that will suck the life out of any machine. It's pretty sad, had they implemented it with something sane (and by that I'm more talking about the style of software development, than the language), I guess it would see quite some use...
ifconfig(8) --frontend
Is there some GUI-front-end for (at least) the wlan related functionality of ifconfig? (No need to argue here, about the flexability of ifconfig and the restrictions of any GUI-approach) The point is, that using OBSD as a workstation on a laptop, requires a lot of authentification at different WPA/WEP encrypted wlan networks, some with PSK, some in enterprise mode and whoknowswhatelse ... Doing this on the terminal is simply a waste of time and it would be rational to have a GUI for at least this subset of the full ifconfig functionality. Does anyone know of an approach here? For now dependencies like GTK || qt doesn't matter /mirco
Re: ifconfig(8) --frontend
"Mirco Richter" writes: > Is there some GUI-front-end for (at least) the wlan related functionality of > ifconfig? http://www.undeadly.org/cgi?action=article&sid=20110420080633 hints that M:tier (http://www.mtier.org/) has something of that sort, but I can't specifically remember whether they've made it available to the general public. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: ifconfig(8) --frontend
On Sun, Aug 04, 2013 at 12:07:29PM +0200, Mirco Richter wrote: > Is there some GUI-front-end for (at least) the wlan related functionality of > ifconfig? > > (No need to argue here, about the flexability of ifconfig and the > restrictions of > any GUI-approach) > > The point is, that using OBSD as a workstation on a laptop, requires a lot of > authentification at different WPA/WEP encrypted wlan networks, some with PSK, > some in enterprise mode and whoknowswhatelse ... > > Doing this on the terminal is simply a waste of time and it would be rational > to have a GUI for at least this subset of the full ifconfig functionality. > > Does anyone know of an approach here? For now dependencies like GTK || qt > doesn't matter > > /mirco I've looked into porting network manager and wcid some time back. It's horrid. They both rely on Linux-specific features like udev so it's not trivial to port them. Also, not everyone running OpenBSD will be willing to trust these tools. I think it would be better to spend time on making the kernel join known encrypted wireless networks just like it joins non-encrypted ones. After all, the real issue lies with configuring the link layer. As soon as there is a link people can use DHCP/autoconf as usual. So you would have hostname.if files such as: nwid mynet wpakey mysecretkey nwid some-other-net nwkey wepkey -nwid The last line switches back to "any essid" mode, and the interface would now join any of the listed networks within range, even if encrypted. Or it could be forced to a particular network without requiring the password again, e.g. 'ifconfig ral0 nwid mynet'. Right now the kernel discards the previously used key when a new key is set. So this would require a password cache in the kernel, which would have to be limited in size. But in practice that should be enough to automatically connect to a set of commonly used networks. I've got a rough start of a proof-of-concept patch for this but there are some bugs I need to figure out before sharing my patch becomes useful. If you'd like to help hacking on it please let me know. Perhaps the idea is stupid and won't really work as I imagine it. But I believe it's worth trying, I also find it annoying to manually configure wireless all the time. WPA enterprise is another story because keys aren't known in advance. But it's not supported out of the box in the base system anyway right now.
Re: ifconfig(8) --frontend
> Doing this on the terminal is simply a waste of time and it would be rational > to have a GUI for at least this subset of the full ifconfig functionality. Care to elaborate on that? What makes it slow for you on the terminal? What would a GUI need to have to be faster? Don't tell me you want 3D-accelerated kitty pics.
Re: ifconfig(8) --frontend
I don't use a GUI but I hacked together a little Python script that basically calls `ifconfig wpi0 scan` to obtain a list of available networks, filters out the known ones, sorts them by priority and signal strength and then configures the one on the top of the list with ifconfig and if need be, with wpa supplicant. The priority and strength sorting is done so I can have multiple wireless networks in the same location configured and readily available. Then I have a script that pings the current IPv4 gateway, or, if that is not available, IPv6 gateway, and once 5 or more packets are missed, just calls /etc/netstart. The /etc/hostname.if file for wpi0 calls the Python script and the /etc/hostname.if for trunk0 configures everything for DHCP. I do this because I have a wireless + wired trunk for transparent switchover. If there's a demand, I can upload the scripts somewhere. There is also some "Set up VPNs if I am in an untrusted location"-stuff in there but it relies on some way to identify the network one is currently attached to. This is currently done by a shell script that checks for things like known wireless ESSIDs, known gateway MAC addresses and known network topologies, for example "When I'm at home, my gateway is 192.168.2.1, there's a host named Zim and one named Gir and my public IP address resolves back to Unity Media". That's probably unportable and needs to be reimplemented for every user. -- Gregor Best
Re: ifconfig(8) --frontend
On Sun, Aug 4, 2013 at 2:04 PM, Stefan Sperling wrote: > I've looked into porting network manager and wcid some time back. > It's horrid. They both rely on Linux-specific features like udev > so it's not trivial to port them. Maybe porting the one below could be easier: https://github.com/pcbsd/pcbsd/tree/master/src-qt4/pc-netmanager ciao, David
Re: Sector offset values for softraid volumes
Erling Westenvik [erling.westen...@gmail.com] wrote: > > physical disks: > sd0a: 64 + N-64 > sd1a: 64 + N-64 > RAID 1 volume: > sd2a: 64 + 64 + N-128 > CRYPTO volume: > sd3a: 64 + 64 + 64 + N-196 > > The space wasted on large disks is negligible but I would really like to > know at which level the 64 sector offset may be set to 0. > I believe the offset is for fdisk to store the MBR and first stage boot loader. The BIOS uses it, OpenBSD does not. I bet you'll be ok with a 0 offset on raid sd2a and sd3a (and only a disklabel, no fdisk). The softraid manual shows using fdisk -i on the raid volumes, and I hope that's just a mistake. The sparc/sparc64 platforms are good places to look because they don't get touched by the BIOS (sounds like softraid) and therefore use don't use fdisk, mbr, BIOS. They're slso good because these platforms were designed ground-up to run BSD, boots a fourth interpreter as its first program (OBP), and know how to charge up the old boot blocks without compatibility glue in-between. Here's a disklabel from my Sun Fire T1000. Unlike fdisk, no space needs to be cut out for disklabel, which already owns the first 16 sectors in the FFS layout. # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST31000524AS duid: 6f7f7705c7253071 flags: vendor bytes/sector: 512 sectors/track: 127 tracks/cylinder: 16 sectors/cylinder: 2032 cylinders: 36366 total sectors: 1953525168 boundstart: 0 boundend: 1953525168 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 20990560 4.2BSD 2048 163841 # / b: 17040352 2099056swap # none c: 19535251680 unused d: 8390128 19139408 4.2BSD 2048 163841 # /tmp e: 41420288 27529536 4.2BSD 2048 163841 # /var f: 4196080 68949824 4.2BSD 2048 163841 # /usr g: 2099056 73145904 4.2BSD 2048 163841 # /usr/X11R6 h: 20972272 75244960 4.2BSD 2048 163841 # /usr/local i: 4196080 96217232 4.2BSD 2048 163841 # /usr/src j: 4196080100413312 4.2BSD 2048 163841 # /usr/obj k: 1848914768104609392 4.2BSD 8192 655361 # /home
poptop on OpenBSD 5.3
Hi, I am trying to configure poptop on OpenBSD 5.3 without success. I've installed the package and configured the files as the /usr/local/share/doc/pkg-readmes/poptop-1.3.4p4 says but didn't work so I started to change things here and there without success. These are the facts: /etc/pptpd.conf: stimeout 10 noipparam logwtmp localip 5.5.5.1 remoteip 5.5.5.2-102 /etc/ppp/options: lock auth usehostname proxyarp +MSChap-V2 mppe-128 mppe-stateless /etc/ppp/ppp.conf: default: set log Phase Chat LCP IPCP CCP tun command set speed 115200 pptp: set log phase tun enable proxy set dns 8.8.8.8 8.8.4.4 set ifaddr 5.5.5.1 5.5.5.0/0 255.255.255.0 set timeout 0 enable chap enable MSChapV2 And here the error: pptpd[25764]: CTRL: Starting call (launching pppd, opening GRE) ppp[14716]: Phase: Using interface: tun0 ppp[14716]: Phase: deflink: Created in closed state ppp[14716]: tun0: Command: default: set speed 115200 ppp[14716]: tun0: Command: pptp: set log phase tun ppp[14716]: tun0: Phase: PPP Started (direct mode). ppp[14716]: tun0: Phase: bundle: Establish ppp[14716]: tun0: Phase: deflink: closed -> opening ppp[14716]: tun0: Phase: deflink: Connected! ppp[14716]: tun0: Phase: deflink: opening -> carrier ppp[14716]: tun0: Phase: deflink: carrier -> lcp ppp[14716]: tun0: Phase: bundle: Authenticate ppp[14716]: tun0: Phase: deflink: his = none, mine = CHAP 0x81 ppp[14716]: tun0: Phase: Chap Output: CHALLENGE ppp[14716]: tun0: Phase: Chap Input: RESPONSE (49 bytes from testuser) ppp[14716]: tun0: Phase: Chap Output: SUCCESS ppp[14716]: tun0: Phase: deflink: lcp -> open ppp[14716]: tun0: Phase: bundle: Network ppp[14716]: tun0: Phase: deflink: open -> lcp ppp[14716]: tun0: Warning: ff01:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Phase: bundle: Terminate pptpd[25764]: CTRL: EOF or bad error reading ctrl packet length. pptpd[25764]: CTRL: couldn't read packet header (exit) pptpd[25764]: CTRL: CTRL read failed ppp[14716]: tun0: Phase: deflink: read (0): Got zero bytes ppp[14716]: tun0: Phase: deflink: Disconnected! ppp[14716]: tun0: Phase: deflink: Connect time: 1 secs: 354 octets in, 364 octets out ppp[14716]: tun0: Phase: deflink: 7 packets in, 11 packets out ppp[14716]: tun0: Phase: total 718 bytes/sec, peak 0 bytes/sec on Sun Aug 4 18:23:07 2013 ppp[14716]: tun0: Phase: deflink: lcp -> closed ppp[14716]: tun0: Phase: bundle: Dead ppp[14716]: tun0: Phase: PPP Terminated (normal). pptpd[25764]: CTRL: Client control connection finished So far I think is not an authentication problem (the authentication process seems to be "success") and it is a network related issue. However, I do not how to fix it according to the three lines on the output: ppp[14716]: tun0: Warning: ff01:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable I enabled and applied on sysctl.conf: net.inet.gre.allow=1 net.inet.gre.wccp=1 Also, I added the pf.conf lines needed to allow traffic from 1723 and GRE connections and, to be sure, let all traffic from 5.5.5.0 network pass through the firewall on tun0. Any help? What I am missing? Thanks in advance, Alvaro
Re: poptop on OpenBSD 5.3
Hi, Why not use the embedded package in OpenBSD 5.3 : npppd ?? conf files : /etc/npppd/npppd.conf and npppd-users Below a link that will help you on : http://fr.slideshare.net/GiovanniBechis/npppd-easy-vpn-with-openbsd Cheers, Wesley Le 2013-08-05 4:48, Alvaro Mantilla Gimenez a écrit : Hi, I am trying to configure poptop on OpenBSD 5.3 without success. I've installed the package and configured the files as the /usr/local/share/doc/pkg-readmes/poptop-1.3.4p4 says but didn't work so I started to change things here and there without success. These are the facts: /etc/pptpd.conf: stimeout 10 noipparam logwtmp localip 5.5.5.1 remoteip 5.5.5.2-102 /etc/ppp/options: lock auth usehostname proxyarp +MSChap-V2 mppe-128 mppe-stateless /etc/ppp/ppp.conf: default: set log Phase Chat LCP IPCP CCP tun command set speed 115200 pptp: set log phase tun enable proxy set dns 8.8.8.8 8.8.4.4 set ifaddr 5.5.5.1 5.5.5.0/0 255.255.255.0 set timeout 0 enable chap enable MSChapV2 And here the error: pptpd[25764]: CTRL: Starting call (launching pppd, opening GRE) ppp[14716]: Phase: Using interface: tun0 ppp[14716]: Phase: deflink: Created in closed state ppp[14716]: tun0: Command: default: set speed 115200 ppp[14716]: tun0: Command: pptp: set log phase tun ppp[14716]: tun0: Phase: PPP Started (direct mode). ppp[14716]: tun0: Phase: bundle: Establish ppp[14716]: tun0: Phase: deflink: closed -> opening ppp[14716]: tun0: Phase: deflink: Connected! ppp[14716]: tun0: Phase: deflink: opening -> carrier ppp[14716]: tun0: Phase: deflink: carrier -> lcp ppp[14716]: tun0: Phase: bundle: Authenticate ppp[14716]: tun0: Phase: deflink: his = none, mine = CHAP 0x81 ppp[14716]: tun0: Phase: Chap Output: CHALLENGE ppp[14716]: tun0: Phase: Chap Input: RESPONSE (49 bytes from testuser) ppp[14716]: tun0: Phase: Chap Output: SUCCESS ppp[14716]: tun0: Phase: deflink: lcp -> open ppp[14716]: tun0: Phase: bundle: Network ppp[14716]: tun0: Phase: deflink: open -> lcp ppp[14716]: tun0: Warning: ff01:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Phase: bundle: Terminate pptpd[25764]: CTRL: EOF or bad error reading ctrl packet length. pptpd[25764]: CTRL: couldn't read packet header (exit) pptpd[25764]: CTRL: CTRL read failed ppp[14716]: tun0: Phase: deflink: read (0): Got zero bytes ppp[14716]: tun0: Phase: deflink: Disconnected! ppp[14716]: tun0: Phase: deflink: Connect time: 1 secs: 354 octets in, 364 octets out ppp[14716]: tun0: Phase: deflink: 7 packets in, 11 packets out ppp[14716]: tun0: Phase: total 718 bytes/sec, peak 0 bytes/sec on Sun Aug 4 18:23:07 2013 ppp[14716]: tun0: Phase: deflink: lcp -> closed ppp[14716]: tun0: Phase: bundle: Dead ppp[14716]: tun0: Phase: PPP Terminated (normal). pptpd[25764]: CTRL: Client control connection finished So far I think is not an authentication problem (the authentication process seems to be "success") and it is a network related issue. However, I do not how to fix it according to the three lines on the output: ppp[14716]: tun0: Warning: ff01:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: Network is unreachable I enabled and applied on sysctl.conf: net.inet.gre.allow=1 net.inet.gre.wccp=1 Also, I added the pf.conf lines needed to allow traffic from 1723 and GRE connections and, to be sure, let all traffic from 5.5.5.0 network pass through the firewall on tun0. Any help? What I am missing? Thanks in advance, Alvaro
Re: poptop on OpenBSD 5.3
I approve Wesley, if you use OpenBSD 5.3 you should use npppd it's simpler than poptop and have nearly the same functionalities -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 05 août 2013 à 08:46 +0400, Wesley MOUEDINE ASSABY a écrit : > Hi, > > Why not use the embedded package in OpenBSD 5.3 : npppd ?? > conf files : /etc/npppd/npppd.conf and npppd-users > > Below a link that will help you on : > http://fr.slideshare.net/GiovanniBechis/npppd-easy-vpn-with-openbsd > > > Cheers, > > Wesley > > Le 2013-08-05 4:48, Alvaro Mantilla Gimenez a écrit : > > Hi, > > > > I am trying to configure poptop on OpenBSD 5.3 without success. > > I've > > installed the package and configured the files as > > the /usr/local/share/doc/pkg-readmes/poptop-1.3.4p4 says but didn't > > work so > > I started to change things here and there without success. These are > > the > > facts: > > > > /etc/pptpd.conf: > > > >stimeout 10 > >noipparam > >logwtmp > >localip 5.5.5.1 > >remoteip 5.5.5.2-102 > > > > > > /etc/ppp/options: > > > >lock > >auth > >usehostname > >proxyarp > >+MSChap-V2 mppe-128 mppe-stateless > > > > > > /etc/ppp/ppp.conf: > > > >default: > > set log Phase Chat LCP IPCP CCP tun command > > set speed 115200 > > > >pptp: > > set log phase tun > > enable proxy > > set dns 8.8.8.8 8.8.4.4 > > set ifaddr 5.5.5.1 5.5.5.0/0 255.255.255.0 > > set timeout 0 > > enable chap > > enable MSChapV2 > > > > > > And here the error: > > > >pptpd[25764]: CTRL: Starting call (launching pppd, opening GRE) > >ppp[14716]: Phase: Using interface: tun0 > >ppp[14716]: Phase: deflink: Created in closed state > >ppp[14716]: tun0: Command: default: set speed 115200 > >ppp[14716]: tun0: Command: pptp: set log phase tun > >ppp[14716]: tun0: Phase: PPP Started (direct mode). > >ppp[14716]: tun0: Phase: bundle: Establish > >ppp[14716]: tun0: Phase: deflink: closed -> opening > >ppp[14716]: tun0: Phase: deflink: Connected! > >ppp[14716]: tun0: Phase: deflink: opening -> carrier > >ppp[14716]: tun0: Phase: deflink: carrier -> lcp > >ppp[14716]: tun0: Phase: bundle: Authenticate > >ppp[14716]: tun0: Phase: deflink: his = none, mine = CHAP 0x81 > >ppp[14716]: tun0: Phase: Chap Output: CHALLENGE > >ppp[14716]: tun0: Phase: Chap Input: RESPONSE (49 bytes from > > testuser) > >ppp[14716]: tun0: Phase: Chap Output: SUCCESS > >ppp[14716]: tun0: Phase: deflink: lcp -> open > >ppp[14716]: tun0: Phase: bundle: Network > >ppp[14716]: tun0: Phase: deflink: open -> lcp > >ppp[14716]: tun0: Warning: ff01:4::: Change route failed: errno: > > Network > > is unreachable > >ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: > > Network > > is unreachable > >ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: > > Network > > is unreachable > >ppp[14716]: tun0: Phase: bundle: Terminate > >pptpd[25764]: CTRL: EOF or bad error reading ctrl packet length. > >pptpd[25764]: CTRL: couldn't read packet header (exit) > >pptpd[25764]: CTRL: CTRL read failed > >ppp[14716]: tun0: Phase: deflink: read (0): Got zero bytes > >ppp[14716]: tun0: Phase: deflink: Disconnected! > >ppp[14716]: tun0: Phase: deflink: Connect time: 1 secs: 354 octets > > in, > > 364 octets out > >ppp[14716]: tun0: Phase: deflink: 7 packets in, 11 packets out > >ppp[14716]: tun0: Phase: total 718 bytes/sec, peak 0 bytes/sec on > > Sun > > Aug 4 18:23:07 2013 > >ppp[14716]: tun0: Phase: deflink: lcp -> closed > >ppp[14716]: tun0: Phase: bundle: Dead > >ppp[14716]: tun0: Phase: PPP Terminated (normal). > >pptpd[25764]: CTRL: Client control connection > > finished > > > > > > So far I think is not an authentication problem (the authentication > > process > > seems to be "success") and it is a network related issue. However, I > > do not > > how to fix it according to the three lines on the output: > > > > ppp[14716]: tun0: Warning: ff01:4::: Change route failed: errno: > > Network > > is unreachable > > ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: > > Network > > is unreachable > > ppp[14716]: tun0: Warning: ff02:4::: Change route failed: errno: > > Network > > is unreachable > > > > I enabled and applied on sysctl.conf: > > > > net.inet.gre.allow=1 > > net.inet.gre.wccp=1 > > > > Also, I added the pf.conf lines needed to allow traffic from 1723 and > > GRE > > connections and, to be sure, let all traffic from 5.5.5.0 network > > pass > > through the firewall on tun0. > > > > Any help? What I am missing? > > > > Thanks in advance, > > > > Alvaro [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
