Re: Install OpenBSD without physical access
On Fri, 17 Aug 2007 21:46:02 -0600 Chris 'Xenon' Hanson <[EMAIL PROTECTED]> wrote: > Jona Joachim wrote: > >>I'm pretty sure Virtuozzo/OpenVZ only support Linux, and not > >> *BSD virtual machines. > > Oh, that would be really sad. The guy from the support told us "you > > can run almost anything on it" when we called several months ago. > > I does support Windows but that's not much of a surprise. > > We're going to call tomorrow and see what they answer. I hope the > > answer will not be "What is BSD?". > > http://en.wikipedia.org/wiki/Virtuozzo#Comparison_to_other_technologies > http://wiki.openvz.org/Introduction_to_virtualization Yeah, sorry, seems like I didn't do my homework. I know that they also offer Windows so they must have other solutions than Virtuozzo/OpenVZ. Thanks for all your replies! Jona
Re: VPN Connection from 4.1 to WatchGuard
Hello again, Am 15.08.2007 um 23:20 schrieb James Lepthien: Hi there, Am 15.08.2007 um 22:24 schrieb Hans-Joerg Hoexer: On Thu, Aug 09, 2007 at 02:22:31AM +0200, James Lepthien wrote: Hi, I have set up a vpn from my OpenBSD Box (4.1-current) to our company WatchGuard X700. My problem is that the re-keying isn't always working and my tunnel does not come up if I send traffic to the destination network. I must manually restart the isakmpd and then start the tunnel by using ipsecctl -f /etc/ipsec.conf. I see some strange errors in my /var/log/messages even when the tunnel is up. What do these errors mean?: Aug 9 01:52:40 voldemort isakmpd[20491]: attribute_unacceptable: ENCRYPTION_ALGORITHM: got 3DES_CBC, expected AES_CBC ... My ipsec.conf looks like this: ike esp from $ext_IP to $peer_GW ike esp from $ext_IP to $peer_LAN peer $peer_GW ike esp from $int_LAN to $peer_LAN \ peer $peer_GW \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "" this enables 3des/sha1/modp1024 only for the third rule. The first and second rule will both use the default values (aes/sha1/modp1024 for phase 1 and aes/sha2-256 for phase 2). try this: ike esp from $ext_IP to $peer_GW \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "" ike esp from $ext_IP to $peer_LAN peer $peer_GW \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "" ike esp from $int_LAN to $peer_LAN peer $peer_GW \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "" it is not stated in the ipsec.conf manual that you need to do this for all the entries. Just for the one ike statement which connects the to LANs. I can not see any difference in this way. The tunnel comes up fine but at sometime the connection gets down and I net to manually kill the isakmpd process and start the ipsec again. In my messages there are always a lot of those lines: Aug 15 23:16:00 voldemort isakmpd[19600]: transport_send_messages: giving up on exchange IPsec-MYEXTIP-PEERIP, no response from peer PEERIP:500 What does this mean? The tunnel is ip and working but I still see those lines... Cheers James Now it seems to be working fine with my OpenBSD and the WatchGuard X700. I now tried again the way that you described but have only two ike statements. My working ipsec.conf looks like this: ike esp from $ext_IP to $peer \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "SHAREDKEY" ike esp from $int_LAN to $peer_LAN \ peer $peer \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "SHAREDKEY" I still get messages like this all the time: "Aug 18 13:20:49 voldemort isakmpd[19600]: transport_send_messages: giving up on exchange IPsec-MY_EXT_IP-PEER_IP, no response from peer PEER_IP:500" But it works. Does anybody know why I get these messages? Cheers James
Re: Problems installing OpenBSD to Soekris
Still having problems. I can't get the soekris to boot as far as I can tell. I used fdisk and created slice for OpenBSD and then used disklabel to create the partitions inside it. After that I extracted sets (base,etc,man) to the disk. I used "fdisk -u sd1" to update the MBR. I modified the /etc/ttys to: tty00 "/usr/libexec/getty std.19200" vt220 on secure I added following to boot.conf: set tty com0 I connected the card to soekris and put the DB9 cable between soekris and my laptop. Before turning power to soekris I gave command "tip -19200 tty00" on my laptop and it replied "connected". After I turn on Soekris nothing happens. I wait a while, turn it off and mount the CF again with the reader. I mounted the partitions again and check the /var/log/messages and it's empty. Shouldn't here be some info if the OpenBSD itself would have booted? Any idea what to do next?
Re: Problems installing OpenBSD to Soekris
On Saturday, August 18, 2007 at 16:33:52 +0300, Timo Myyrd wrote: >Still having problems. I can't get the soekris to boot as far as I can tell. > >I used fdisk and created slice for OpenBSD and then used disklabel to >create the partitions inside it. >After that I extracted sets (base,etc,man) to the disk. >I used "fdisk -u sd1" to update the MBR. >I modified the /etc/ttys to: >tty00 "/usr/libexec/getty std.19200" vt220 on secure > >I added following to boot.conf: >set tty com0 Don't forget to set the speed to 19200 here as well. The default for the kernel is 9600 bps and the getty is only started at the end of the boot process. Until then, you see nothing or rubbish at best at the serial console. >I connected the card to soekris and put the DB9 cable between soekris >and my laptop. >Before turning power to soekris I gave command "tip -19200 tty00" on my >laptop and it replied "connected". >After I turn on Soekris nothing happens. If there's no output at all, then you might have the wrong serial cable (there are quite a few types of serial null-modem cables) or the Soekris is dead. You should at least see the Soekris powering up, counting memory and so on. I suggest to get this part working first. >I wait a while, turn it off >and mount the CF again with the reader. >I mounted the partitions again and check the /var/log/messages and it's >empty. Shouldn't here be some info if the OpenBSD itself would have booted? If the system had booted OK, the boot log should be there. Perhaps there's a problem with the disk geometry (the card reader might use a different translation then your Soekris), perhaps something went wrong during the install with the bootblock? I find it much easier to use pxeboot and let the installer handle all of this. But in either case, I think you should get the serial console working first. HTH, Maurice
Re: Problems installing OpenBSD to Soekris
Maurice Janssen wrote: On Saturday, August 18, 2007 at 16:33:52 +0300, Timo Myyrd wrote: Still having problems. I can't get the soekris to boot as far as I can tell. I used fdisk and created slice for OpenBSD and then used disklabel to create the partitions inside it. After that I extracted sets (base,etc,man) to the disk. I used "fdisk -u sd1" to update the MBR. I modified the /etc/ttys to: tty00 "/usr/libexec/getty std.19200" vt220 on secure I added following to boot.conf: set tty com0 Don't forget to set the speed to 19200 here as well. The default for the kernel is 9600 bps and the getty is only started at the end of the boot process. Until then, you see nothing or rubbish at best at the serial console. Ok, I will add the "stty com0 19200" to boot.conf I connected the card to soekris and put the DB9 cable between soekris and my laptop. Before turning power to soekris I gave command "tip -19200 tty00" on my laptop and it replied "connected". After I turn on Soekris nothing happens. If there's no output at all, then you might have the wrong serial cable (there are quite a few types of serial null-modem cables) or the Soekris is dead. You should at least see the Soekris powering up, counting memory and so on. I suggest to get this part working first. Any suggestions on how? I have Belkin null-modem serial cable which I bought from the same place as that soekris so it would be quite silly for a european soekris distributor to sell a null modem cables that won't work with soekrises. Should Soekrisises error led lit up if there would be some problem or something. Now the only light that stays on is the 'power'. I wait a while, turn it off and mount the CF again with the reader. I mounted the partitions again and check the /var/log/messages and it's empty. Shouldn't here be some info if the OpenBSD itself would have booted? If the system had booted OK, the boot log should be there. Perhaps there's a problem with the disk geometry (the card reader might use a different translation then your Soekris), perhaps something went wrong during the install with the bootblock? I find it much easier to use pxeboot and let the installer handle all of this. But in either case, I think you should get the serial console working first. HTH, Maurice
Re: Problems installing OpenBSD to Soekris
On Saturday, August 18, 2007 at 18:35:37 +0300, Timo Myyrd wrote: >Maurice Janssen wrote: >>If there's no output at all, then you might have the wrong serial cable >>(there are quite a few types of serial null-modem cables) or the Soekris >>is dead. You should at least see the Soekris powering up, counting >>memory and so on. I suggest to get this part working first. >> >Any suggestions on how? I have Belkin null-modem serial cable which I >bought from the same place as that soekris so it would be quite silly >for a european soekris distributor to sell a null modem cables that >won't work with soekrises. OK, should be fine then. How do you make the connection? I use something like: soekris|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty00:tc=direct:tc=unixhost: in /etc/remote and 'tip soekris' to connect to it. >Should Soekrisises error led lit up if there would be some problem or >something. Now the only light that stays on is the 'power'. On the 4501, it's on when you turn it on and it goes off during the POST. Maurice
Re: Problems installing OpenBSD to Soekris
Maurice Janssen wrote: On Saturday, August 18, 2007 at 18:35:37 +0300, Timo Myyrd wrote: Maurice Janssen wrote: If there's no output at all, then you might have the wrong serial cable (there are quite a few types of serial null-modem cables) or the Soekris is dead. You should at least see the Soekris powering up, counting memory and so on. I suggest to get this part working first. Any suggestions on how? I have Belkin null-modem serial cable which I bought from the same place as that soekris so it would be quite silly for a european soekris distributor to sell a null modem cables that won't work with soekrises. OK, should be fine then. How do you make the connection? I use something like: soekris|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty00:tc=direct:tc=unixhost: in /etc/remote and 'tip soekris' to connect to it. I just have tried to use the command "tip -19200 tty00". So I should make those additions to /etc/remote and re-try? Should Soekrisises error led lit up if there would be some problem or something. Now the only light that stays on is the 'power'. On the 4501, it's on when you turn it on and it goes off during the POST. Maurice
Diese seite musst du unbedingt mal ausprobieren
Hi hier kannst du sofort die gelsten Videos die Anschaun, voll der Hammer! Hier klicken! Bis Bald, Andi This message has been scanned for malware by SurfControl plc. www.surfcontrol.com
Re: Install OpenBSD without physical access
On 8/18/07, Jona Joachim <[EMAIL PROTECTED]> wrote: > Yeah, sorry, seems like I didn't do my homework. > I know that they also offer Windows so they must have other solutions > than Virtuozzo/OpenVZ. > > Thanks for all your replies! > Jona > > Virtuozzo supports Linux and Windows NT, but on different physical machines.
Re: Problems installing OpenBSD to Soekris
On Saturday, August 18, 2007 at 19:40:49 +0300, Timo Myyrd wrote: >Maurice Janssen wrote: >>OK, should be fine then. How do you make the connection? I use >>something like: >>soekris|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ >>:dv=/dev/tty00:tc=direct:tc=unixhost: >>in /etc/remote and 'tip soekris' to connect to it. > >I just have tried to use the command "tip -19200 tty00". So I should >make those additions to /etc/remote and re-try? I think the defaults for tty00 in /etc/remote are the same as I use. So if you use the defaults, then I don't expect that it makes a difference. Is the red error LED on for a couple of seconds when you connect the power supply? Do you have another system to test the null modem cable? Maurice
Re: Problems installing OpenBSD to Soekris
Maurice Janssen wrote: On Saturday, August 18, 2007 at 19:40:49 +0300, Timo Myyrd wrote: Maurice Janssen wrote: OK, should be fine then. How do you make the connection? I use something like: soekris|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty00:tc=direct:tc=unixhost: in /etc/remote and 'tip soekris' to connect to it. I just have tried to use the command "tip -19200 tty00". So I should make those additions to /etc/remote and re-try? I think the defaults for tty00 in /etc/remote are the same as I use. So if you use the defaults, then I don't expect that it makes a difference. Is the red error LED on for a couple of seconds when you connect the power supply? Do you have another system to test the null modem cable? Maurice Yes, the error led is on for a few seconds.
Re: Problems installing OpenBSD to Soekris
Timo Myyrd wrote: > Still having problems. I can't get the soekris to boot as far as I can tell. > > I used fdisk and created slice for OpenBSD and then used disklabel to > create the partitions inside it. > After that I extracted sets (base,etc,man) to the disk. > I used "fdisk -u sd1" to update the MBR. You didn't install the PBR. installboot(8), FAQ 14. > I modified the /etc/ttys to: > tty00 "/usr/libexec/getty std.19200" vt220 on secure Personally, I'd rather slow the Soekris ROM down to 9600. That's a more standard speed. The OS and the HW default to two different speeds, so one will have to move from default. If this is the only serial device in your life, you may not care. It's far from my only serial device, however. Everything else seems to default to 9600. > I added following to boot.conf: > set tty com0 > > I connected the card to soekris and put the DB9 cable between soekris > and my laptop. > Before turning power to soekris I gave command "tip -19200 tty00" on my > laptop and it replied "connected". > After I turn on Soekris nothing happens. Then you have serial cable problems, IN ADDITION TO the PBR problem. Using cua00 instead of tty00 may help some of your serial problems. > I wait a while, turn it off > and mount the CF again with the reader. > I mounted the partitions again and check the /var/log/messages and it's > empty. Shouldn't here be some info if the OpenBSD itself would have booted? > > Any idea what to do next? install the boot code properly and fix your serial problems. :) Nick.
Re: ipsec vpn?
Following the advice from Hans-Joerg and Markus I changed the ipsec.con file back to the default transforms sent by Greenbow, ran ipsecctl -f /eetc/ipsec.conf, changed the permissions on the policy file and started isakmpd without the "-K". Greenbow logging shows I did not even get past the Phase 1 negotiation # cat /etc/ipsec.conf ike dynamic esp tunnel from any to 192.168.1.0/24 \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des \ psk abc123 # ipsecctl -f /etc/ipsec.conf # chmod 600 /etc/isakmpd/isakmpd.policy # ls -al /etc/isakmpd/isakmpd.policy -rw--- 1 root wheel 40 Aug 16 12:20 /etc/isakmpd/isakmpd.policy # ps ax |grep isakmpd 17575 ?? Is 0:00.02 isakmpd: monitor [priv] (isakmpd) 12021 ?? I 0:00.60 isakmpd # echo "p on" > /var/run/isakmpd.fifo # echo "p off" > /var/run/isakmpd.fifo # tcpdump -r /var/run/isakmpd.pcap -vvn tcpdump: WARNING: snaplen raised from 96 to 65536 13:18:38.973099 64.119.40.170.500 > 64.119.37.74.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: 8c3f9c08dbcbb765-> msgid: len: 160 payload: SA len: 52 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 40 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 32 transform: 0 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = 3DES_CBC attribute HASH_ALGORITHM = SHA attribute AUTHENTICATION_METHOD = PRE_SHARED attribute GROUP_DESCRIPTION = MODP_1024 attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 3600 payload: VENDOR len: 20 (supports v1 NAT-T, draft-ietf-ipsec-nat-t-ike-00) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 (supports v3 NAT-T, draft-ietf-ipsec-nat-t-ike-03) payload: VENDOR len: 20 (supports DPD v1.0) [ttl 0] (id 1, len 188) 13:18:38.974019 64.119.37.74.500 > 64.119.40.170.500: [udp sum ok] isakmp v1.0 exchange INFO cookie: 39af4dec2463f320-> msgid: len: 40 payload: NOTIFICATION len: 12 notification: NO PROPOSAL CHOSEN [ttl 0] (id 1, len 68) Greenbow log: [VPNCONF] TGBIKESTART received 20070818 131838 Default (SA Home_Network-P1) SEND phase 1 Main Mode [SA] [VID] [VID] [VID] [VID] 20070818 131838 Default (SA ) RECV Informational [NOTIFY] with NO_PROPOSAL_CHOSEN error 20070818 131845 Default (SA Home_Network-P1) SEND phase 1 Main Mode [SA] [VID] [VID] [VID] [VID]
Re: ipsec vpn?
l 0] (id 1, len 116) 13:29:25.410330 64.119.37.74.4500 > 64.119.40.170.4500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: c283bb96 len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE seq 23112 [ttl 0] (id 1, len 116) 13:29:25.466349 64.119.40.170.4500 > 64.119.37.74.500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 8f49389a len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE_ACK seq 23112 [ttl 0] (id 1, len 116) 13:29:30.486598 64.119.37.74.4500 > 64.119.40.170.4500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 3fa0fe90 len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE seq 23113 [ttl 0] (id 1, len 116) 13:29:30.539491 64.119.40.170.4500 > 64.119.37.74.500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 6c62fcc6 len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE_ACK seq 23113 [ttl 0] (id 1, len 116) 13:29:35.556146 64.119.37.74.4500 > 64.119.40.170.4500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 7a7f89a3 len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE seq 23114 [ttl 0] (id 1, len 116) 13:29:35.612233 64.119.40.170.4500 > 64.119.37.74.500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 4408b08b len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE_ACK seq 23114 [ttl 0] (id 1, len 116) 13:29:40.625802 64.119.37.74.4500 > 64.119.40.170.4500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 58a07d6a len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE seq 23115 [ttl 0] (id 1, len 116) 13:29:40.681990 64.119.40.170.4500 > 64.119.37.74.500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 80482c26 len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE_ACK seq 23115 [ttl 0] (id 1, len 116) 13:29:45.685449 64.119.37.74.4500 > 64.119.40.170.4500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO cookie: 14a9d793fabd9a1b->40a39c778bcbd5eb msgid: 0816db3b len: 84 payload: HASH len: 24 payload: NOTIFICATION len: 32 notification: STATUS_DPD_R_U_THERE seq 23116 [ttl 0] (id 1, len 116) 13:29:45.741452 64.119.40.170.4500 > 64.119.37.74.500: [bad udp cksum 280!] udpencap: isakmp v1.0 exchange INFO >From Greenbow logs: [VPNCONF] TGBIKESTART received 20070818 132904 Default (SA Home_Network-P1) SEND phase 1 Main Mode [SA] [VID] [VID] [VID] [VID] 20070818 132904 Default (SA Home_Network-P1) RECV phase 1 Main Mode [SA] [VID] [VID] [VID] [VID] [VID] 20070818 132904 Default (SA Home_Network-P1) SEND phase 1 Main Mode [KEY_EXCH] [NONCE] [NAT_D] [NAT_D] 20070818 132904 Default (SA Home_Network-P1) RECV phase 1 Main Mode [KEY_EXCH] [NONCE] [NAT_D] [NAT_D] 20070818 132904 Default (SA Home_Network-P1) SEND phase 1 Main Mode [HASH] [ID] [NOTIFY] 20070818 132904 Default (SA Home_Network-P1) RECV phase 1 Main Mode [HASH] [ID] [NOTIFY] 20070818 132904 Default phase 1 done: initiator id 192.168.11.109, responder id gateway.home.lan 20070818 132904 Default (SA Home_Network-Home_Network-P2) SEND phase 2 Quick Mode [HASH] [SA] [NONCE] [ID] [ID] 20070818 132905 Default (SA Home_Network-Home_Network-P2) RECV phase 2 Quick Mode [HASH] [SA] [NONCE] [ID] [ID] 20070818 132905 Default (SA Home_Network-Home_Network-P2) SEND phase 2 Quick Mode [HASH] 20070818 132909 Default (SA Home_Network-P1) RECV Informational [HASH] [NOTIFY] type DPD_R_U_THERE 20070818 132909 Default (SA Home_Network-P1) SEND Informational [HASH] [NOTIFY] type DPD_R_U_THERE_ACK 20070818 132915 Default (SA Home_Network-P1) RECV Informational [HASH] [NOTIFY] type DPD_R_U_THERE 20070818 132915 Default (SA Home_Network-P1) SEND Informational [HASH] [NOTIFY] type DPD_R_U_THERE_ACK 20070818 132915 Default (SA ) RECV phase 2 Quick Mode [HASH] [SA] [KEY_EXCH] [NONCE] [ID] [ID] 20070818 132915 Default message_negotiate_incoming_sa: no compatible proposal found 20070818 132920 Default (SA Home_Network-P1) RECV Informational [HASH] [NOTIFY] type DPD_R_U_THERE 20070818 132920
Re: corrupt locate.database
>> My Problem is, that locate tells me: locate database header corrupt, bigram char outside 0, 32-127: 14 << This has been discussed a couple of times here. Search the archives for "problem with locate", e.g. http://marc.info/?l=openbsd-misc&w=2&r=1&s=problem+with+locate&q=b I had the same issue; Otto's patch fixed it. Steve http://www.fivetrees.com
10G cards for 4.2
I'm looking at the possibility of helping get a 10G speed network running. This is new territory to me--for OpenBSD purposes, are there more solid drivers out there? I'm told that the machine would want to exchange a lot of data, constantly (video stuff). Part of my consideration would also be what 10G companies have been open source friendly with hardware, etc. If I can I'd like to spend money somewhere that deserves it. Ideas? Thanks, STeve Andre'
OT: recommendations for a serial/USB UPS?
Hi List. I am about to buy UPS, but would really appreciate your opinions to make sure I throw money away in the right direction. 1. Can I just assume that device will work reliably if it is listed as supported in nut, upsd or apc-upsd? What should I avoid buying? (All machines involved are running -stable) 2. Are there any problems with the ones that use serial port for accessing status information? What might be the problems with the USB ones? 3. Is the status information reliability/responsiveness decreasing over time as device is getting old or the device just dies at once? 4. What are the ways the UPS device notifies about the fact that it is becoming too old to use and that I should get a new one? 5. Are there ways to monitor the UPS from two (or more) machines? (self-made, three-head serial cable, right ;) ? 6. Which monitoring daemon should I prefer? I do not want my network to get down due to unreliable UPSes, hence all the questions. Google does not include production line experiences, that is why I am asking you. Would be grateful for any input. Thank you for your time. vladas
installing jdk-1.5 on 4.1 (i386) error
I downloaded all the packages & put them in /usr/ports/distfiles. I had to change the Sha1 checksum for xalan-j_2_7_0-bin.tar.gz as make(1) was exiting with a signature mismatch error. (File: /usr/ports/devel/jdk/1.5/distinfo) I go to /usr/ports/devel/jdk/1.5 and type "make install" and it exits with an error: Unexpected EOF in archive. Any help would be much appreciated. Here's the make output - ===> Checking files for jdk-1.5.0p28 `/usr/ports/distfiles/jdk-1_5_0-src-scsl.zip' is up to date. `/usr/ports/distfiles/jdk-1_5_0-bin-scsl.zip' is up to date. `/usr/ports/distfiles/bsd-jdk15-patches-4.tar.bz2' is up to date. `/usr/ports/distfiles/jdk-1_5_0-solaris-i586.tar.Z' is up to date. `/usr/ports/distfiles/xalan-j_2_7_0-bin.tar.gz' is up to date. >> Checksum OK for jdk-1_5_0-src-scsl.zip. (sha1) >> Checksum OK for jdk-1_5_0-bin-scsl.zip. (sha1) >> Checksum OK for bsd-jdk15-patches-4.tar.bz2. (sha1) >> Checksum OK for jdk-1_5_0-solaris-i586.tar.Z. (sha1) >> Checksum OK for xalan-j_2_7_0-bin.tar.gz. (sha1) ===> Extracting for jdk-1.5.0p28 /usr/local/bin/gtar: Unexpected EOF in archive /usr/local/bin/gtar: Unexpected EOF in archive /usr/local/bin/gtar: Error is not recoverable: exiting now *** Error code 2 Stop in /usr/ports/devel/jdk/1.5 (line 1912 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/devel/jdk/1.5 (line 1892 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/devel/jdk/1.5 (line 1373 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/devel/jdk/1.5 (line 1861 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/devel/jdk/1.5 (line 1400 of /usr/ports/infrastructure/mk/bsd.port.mk).
route command
Hi,
It must have been too long ago since I built routers under BSD. I got three
subnets in a series below the internet connection and cannot add a proper
route between subnet 1 and 3.
The subnets are as follows:
{Internet}
|
Subnet 1: 10.1.1
|
Subnet 2: 192.168.1
|
Subnet 3: 192.168.0
Router 1: int if = 10.1.1.1
Router 2: ext if = 10.1.1.2 int if = 192.168.1.254
Router 3: ext if = 192.168.1.253 int if = 192.168.0.254
On the second router I have these routes up:
(Note the H in 192.168.0.0 but I need a -net.)
DestinationGatewayFlagsRefs UseMtu Interface
default 10.1.1.1 UGS 0 6014 - xl0
10.1.1/24 link#2 UC 00 - xl0
10.1.1.1 00:00:00:00:00:f1 UHLc00 - xl0
127/8 127.0.0.1 UGRS00 33224 lo0
127.0.0.1 127.0.0.1 UH 0 30 33224 lo0
192.168.0.0192.168.1.254 UGHS00 - dc0
192.168.1/24 link#1 UC 00 - dc0
224/4 127.0.0.1 URS 00 33224 lo0
Sitting on the second router (above), I cannot get it to route to subnet
192.168.0. As you can see below.
route get 192.168.0.1
route to: 192.168.0.1
destination: default
mask: default
gateway: 10.1.1.1
interface: xl0
if address: 10.1.1.2
flags:
recvpipe sendpipe ssthresh rtt,msecrttvar hopcount mtu
expire
0 0 0 0 0 0 0 0
I've tried numerous route commands but it never results in routing it down to
198.168.0. My last routing commands looks like this:
route add 192.168.0 192.168.1.253
route add 192.168.0.254 192.168.1.253
What is the route command supposed to look like to route down to 192.168.0?
--
Steve
"They that would give up essential liberty for temporary safety
deserve neither liberty nor safety."
Benjamin Franklin
permission for /var/mail
fetchmail was complaining that procmail cannot create /var/mail/me while fetching mail. The permission on /var/mail/ directory was set to - drwxr-xr-x 2 root wheel 512 Aug 19 12:16 /var/mail/ I changed it to - drwxrwxr-x 2 root wheel 512 Aug 19 12:16 /var/mail/ It's working fine now since user "me" is in wheel group. Do I need to make /var/mail world-writable to get mail for other users? Is there any other way of doing this - fetching mail in /home/username? Any suggestions would be much appreciated. Thanks.
Re: route command
On Saturday 18 August 2007 22:19, steve wrote: Hmm, I had added the route commands to rc.local and with each edit executed sh netstart which of course does not read rc.local. -- Steve Szmidt "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." Benjamin Franklin
Re: route command
On 8/18/07, steve <[EMAIL PROTECTED]> wrote: > It must have been too long ago since I built routers under BSD. I got three > subnets in a series below the internet connection and cannot add a proper > route between subnet 1 and 3. > I've tried numerous route commands but it never results in routing it down to > 198.168.0. My last routing commands looks like this: > > route add 192.168.0 192.168.1.253 > route add 192.168.0.254 192.168.1.253 > > What is the route command supposed to look like to route down to 192.168.0? One way is with an explicit CIDR mask on the network: # route add 192.168.0.0/24 10.0.1.1 add net 192.168.0.0/24: gateway 10.0.1.1 # route -n show | grep ^192 192.168.0/24 10.0.1.1 UGS 00 - fxp0 DS
Re: route command
On 8/18/07, steve szmidt <[EMAIL PROTECTED]> wrote: > On Saturday 18 August 2007 22:19, steve wrote: > > Hmm, I had added the route commands to rc.local and with each edit executed > sh netstart which of course does not read rc.local. See hostname.if(5), and particularly the description for '!command-line' in that manual. DS
Re: OT: recommendations for a serial/USB UPS?
> I am about to buy UPS, but would really appreciate your > opinions to make sure I throw money away in the right > direction. Time is not on my side. I have got OMRON BX35F's. (4.2 GENERIC #338) /bsd: uhidev1 at uhub3 port 1 configuration 1 interface 0 /bsd: /bsd: uhidev1: OMRON BX35F, rev 1.10/0.07, addr 2, iclass 3/0 /bsd: uhid0 at uhidev1: input=64, output=16, feature=0 Could please somebody enlighten me if usb upses need any special treatment from kernel or it is all just about libusb (like bluetooth afaik)? > 1. Can I just assume that device will work reliably if it is > listed as supported in nut, upsd or apc-upsd? What should > I avoid buying? (All machines involved are running -stable) I am looking forward to hear from nut-upsdev soon if there is interest in the hw from their side. > 5. Are there ways to monitor the UPS from two (or more) machines? > > (self-made, three-head serial cable, right ;) ? What I have meant here is that I do _NOT_ want to run any not-in-the-baseXX.tgz TCP services. Whether or not it is practical - that is another question :) Sorry for the noise if any.
Re: OT: recommendations for a serial/USB UPS?
On Sun, 19 Aug 2007 14:42:31 +0900, vladas wrote: >> I am about to buy UPS, but would really appreciate your >> opinions to make sure I throw money away in the right >> direction. > >Time is not on my side. I have got OMRON BX35F's. > >(4.2 GENERIC #338) > >/bsd: uhidev1 at uhub3 port 1 configuration 1 interface 0 >/bsd: >/bsd: uhidev1: OMRON BX35F, rev 1.10/0.07, addr 2, iclass 3/0 >/bsd: uhid0 at uhidev1: input=64, output=16, feature=0 > >Could please somebody enlighten me if usb upses need any >special treatment from kernel or it is all just about libusb (like >bluetooth afaik)? > >> 1. Can I just assume that device will work reliably if it is >> listed as supported in nut, upsd or apc-upsd? What should >> I avoid buying? (All machines involved are running -stable) > >I am looking forward to hear from nut-upsdev soon if there is >interest in the hw from their side. > >> 5. Are there ways to monitor the UPS from two (or more) machines? >> >> (self-made, three-head serial cable, right ;) ? > >What I have meant here is that I do _NOT_ want to run any >not-in-the-baseXX.tgz TCP services. Whether or not it is practical - >that is another question :) You really should do a bit more reading of the readily available information. e.g. http://ports.openbsd.nu/sysutils/nut says: " Nut also has a network communications layer that allows other machines to coordinate shutdowns with the machine that is physically attached to the UPS." Of course you would also look at the nut website and find: http://www.networkupstools.org/client-projects/ which you can do your own research on. Let your fingers do the walking... on your keyboard before you ask more questions. This isn't really a misc@ question. ports@ or at the nut mail-list would be best IMNSHO. Rod/ >From the land "down under": Australia. Do we look from up over?
