Re: serial port usage
Craig Skinner wrote: Darren Spruell wrote: For the scenario where you have two openbsd hosts, one connected to the second with a serial null modem cable, what is the right device to use when connecting using tip(1) from the first to a console on the second? [snip] Then, on either box, I can do this to get to the console on its neighbour: $ sudo tip tty01 Replying to myself here for the archives: In another recent thread (operator permissions: a wish-list) started by Douglas Tutty; dialout: so I can use minicom to access the modem directly When I saw that, I added myself to the dialer group so that I can tip to another box over the serial line without sudo: $ ls -l /dev/tty01 crw-rw 1 uucp dialer8, 1 Sep 20 08:20 /dev/tty01 $ groups staff wheel operator dialer $ tip tty01 connected Nice one, thanks for the idea!
Re: serial port usage
* Stuart Henderson [EMAIL PROTECTED] [2007-09-14 21:39]: USB - the number of boxes I've had to disable USB on to stabilise, this would not usually be my first choice. ymmv, as they say (-: wtf? out of the about 180 i control i don't have a simgle one with usb disabled... -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: serial port usage
* L. V. Lammert [EMAIL PROTECTED] [2007-09-14 18:33]: At 12:00 PM 9/14/2007 -0400, Trash Compactor wrote: Alternatively, you can put puc(4) cards into an OpenBSD box or hook up a tangle of ucom(4) adapters to a tree of powered USB hubs There are several multi-port USB-serial adapters available. You can get bus-powered ones up to around 8 DB9 *OR* you can save yourself a ton of heacaches and get a 'Terminal Server' I'd say an openbsd box with a coulke of 8-port usb-cereal (or a couple of puc(4)s) saves a ton of headaches over any so-called terminal server (translation to english: little stupid very limited box that either is is old and runs something weird proprietary or is somewhat recent and expensive and runs something weird proprietary they call linux and sucks in any case). -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: serial port usage
On Fri, Sep 14, 2007 at 09:40:44AM +0200, Raimo Niskanen wrote: Can someone clarify the difference between /dev/tty00 and /dev/cua00? to some extent these are documented in tty(4). jmc
Re: serial port usage
On 2007/09/14 09:40, Raimo Niskanen wrote: But for local non-modem connect you want to use tip tty00 that uses /dev/tty00, direct connect, no phone number. I use cu -l cua00. Can someone clarify the difference between /dev/tty00 and /dev/cua00? tty(4) explains all.
Re: serial port usage
* Daniel Ouellet [EMAIL PROTECTED] [2007-09-14 07:02]: As we are on the subject and I do not want to deviate from the original question, I would however appreciate suggestions as to how I can have a one server witch can actually have up to 32 serial console to control LOM on Sun server. I may need up to 48 in one case, but instead of using a bunch of Cisco 2509 and 2511, I would much prefer using one good OpenBSD server with proper PF, etc to have the same console control on legacy Sun boxes. there are multiport usb-serial adapters. and of course you can use multiple of them. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: serial port usage
Darren Spruell wrote: For the scenario where you have two openbsd hosts, one connected to the second with a serial null modem cable, what is the right device to use when connecting using tip(1) from the first to a console on the second? This works very well for me on i386; 2 null modem serial cables, cross connected thusly: box-a pccom0 connected to box-b pccom1 box-b pccom0 connected to box-a pccom1 This on both: $ cat /etc/boot.conf stty com0 9600 set tty com0 And this too on both boxes: $ rcsdiff -r1.1 /etc/remote === RCS file: /etc/RCS/remote,v retrieving revision 1.1 diff -r1.1 /etc/remote 67a68,70 tty01|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty01:tc=direct:tc=unixhost: Then, on either box, I can do this to get to the console on its neighbour: $ sudo tip tty01
Re: serial port usage
Henning Brauer wrote: there are multiport usb-serial adapters. and of course you can use multiple of them. This may be really really stupid, but for Mac minis that have no serial ports listed in their dmesg (e.g: http://erdelynet.com/tech/openbsd/openbsd-on-intel-mac-mini/) could you use a USB-Serial adapter and place that directive in /etc/boot.conf to redirect the console output? Nowt about that in boot.conf's man page: set [varname [value]] .. .. tty Active console device name (e.g., com0, com1, pc0). I see that there are several mac mini colo outfits, such as http://www.mythic-beasts.com/macminicolo.html, and a remote console is a very handy thing to have.
Re: serial port usage
On Fri, Sep 14, 2007 at 11:16:46AM +0100, Craig Skinner wrote: | Henning Brauer wrote: | there are multiport usb-serial adapters. and of course you can use | multiple of them. | | | This may be really really stupid, but for Mac minis that have no serial | ports listed in their dmesg (e.g: | http://erdelynet.com/tech/openbsd/openbsd-on-intel-mac-mini/) could you | use a USB-Serial adapter and place that directive in /etc/boot.conf to | redirect the console output? Nowt about that in boot.conf's man page: | | set [varname [value]] | .. | .. | tty Active console device name (e.g., com0, com1, pc0). | I'm afraid not. It must be a real serial port, supported by the BIOS and all that stuff. You can run a getty on a USB-serial adapter, but console must be the real thing. Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: serial port usage
Paul de Weerd wrote: I'm afraid not. It must be a real serial port, supported by the BIOS and all that stuff. You can run a getty on a USB-serial adapter, but console must be the real thing. That makes perfect sense with the BIOS, thanks!
Re: : serial port usage
Thank you! On Fri, Sep 14, 2007 at 09:05:06AM +0100, Jason McIntyre wrote: On Fri, Sep 14, 2007 at 09:40:44AM +0200, Raimo Niskanen wrote: Can someone clarify the difference between /dev/tty00 and /dev/cua00? to some extent these are documented in tty(4). jmc -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: serial port usage
Daniel Ouellet [EMAIL PROTECTED] wrote: As we are on the subject and I do not want to deviate from the original question, I would however appreciate suggestions as to how I can have a one server witch can actually have up to 32 serial console to control LOM on Sun server. I may need up to 48 in one case, but instead of using a bunch of Cisco 2509 and 2511, I would much prefer using one good OpenBSD server with proper PF, etc Put the access servers in a private network and an OpenBSD box in front. We use such a setup for the ports.openbsd.org machines. There is a little Soekris that can be accessed by ssh and that runs ports/comms/conserver, and on a separate interface it is connected to an access server. Alternatively, you can put puc(4) cards into an OpenBSD box or hook up a tangle of ucom(4) adapters to a tree of powered USB hubs. -- Christian naddy Weisgerber [EMAIL PROTECTED]
Re: serial port usage
Christian Weisgerber wrote: Daniel Ouellet [EMAIL PROTECTED] wrote: As we are on the subject and I do not want to deviate from the original question, I would however appreciate suggestions as to how I can have a one server witch can actually have up to 32 serial console to control LOM on Sun server. I may need up to 48 in one case, but instead of using a bunch of Cisco 2509 and 2511, I would much prefer using one good OpenBSD server with proper PF, etc Put the access servers in a private network and an OpenBSD box in front. We use such a setup for the ports.openbsd.org machines. There is a little Soekris that can be accessed by ssh and that runs ports/comms/conserver, and on a separate interface it is connected to an access server. Alternatively, you can put puc(4) cards into an OpenBSD box or hook up a tangle of ucom(4) adapters to a tree of powered USB hubs There are several multi-port USB-serial adapters available. You can get bus-powered ones up to around 8 DB9 ports. Beyond that, they have their own power supplies Here are a few that have good prices. I am not sure how good they are, but I did just order the PL-8COM one at $159USD for exactly this application... http://www.byterunner.com/byterunner/new_frontpage=usbserialadapters /Jason
Re: serial port usage
At 12:00 PM 9/14/2007 -0400, Trash Compactor wrote: Alternatively, you can put puc(4) cards into an OpenBSD box or hook up a tangle of ucom(4) adapters to a tree of powered USB hubs There are several multi-port USB-serial adapters available. You can get bus-powered ones up to around 8 DB9 *OR* you can save yourself a ton of heacaches and get a 'Terminal Server' (as many ports as you wish) at the surplus store for $10-$50US. Route it's traffic through an OBSD machine with - problem solved. In case memory is short, in the old days users HAD actual ASCII terminals ON their desk to do work g, which got done quickly efficiently! None of this network stuff, virii, spam, Internet Exploder, or other Windoze attack-atracting tools. Lee
Re: serial port usage
On 9/14/07, Craig Skinner [EMAIL PROTECTED] wrote: Darren Spruell wrote: For the scenario where you have two openbsd hosts, one connected to the second with a serial null modem cable, what is the right device to use when connecting using tip(1) from the first to a console on the second? This works very well for me on i386; 2 null modem serial cables, cross connected thusly: box-a pccom0 connected to box-b pccom1 box-b pccom0 connected to box-a pccom1 This on both: $ cat /etc/boot.conf stty com0 9600 set tty com0 And this too on both boxes: $ rcsdiff -r1.1 /etc/remote === RCS file: /etc/RCS/remote,v retrieving revision 1.1 diff -r1.1 /etc/remote 67a68,70 tty01|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty01:tc=direct:tc=unixhost: Then, on either box, I can do this to get to the console on its neighbour: $ sudo tip tty01 Is this just for boot messages? It's my understanding (minimal, at that) that you can't do this for logins both directions because getty will tie up the port? Greg -- Ticketmaster and Ticketweb suck, but everyone knows that: http://ticketmastersucks.org Dethink to survive - Mclusky
Re: serial port usage
On 9/14/07, Trash Compactor [EMAIL PROTECTED] wrote: Greg Thomas wrote: On 9/14/07, Craig Skinner [EMAIL PROTECTED] wrote: Darren Spruell wrote: For the scenario where you have two openbsd hosts, one connected to the second with a serial null modem cable, what is the right device to use when connecting using tip(1) from the first to a console on the second? This works very well for me on i386; 2 null modem serial cables, cross connected thusly: box-a pccom0 connected to box-b pccom1 box-b pccom0 connected to box-a pccom1 This on both: $ cat /etc/boot.conf stty com0 9600 set tty com0 And this too on both boxes: $ rcsdiff -r1.1 /etc/remote === RCS file: /etc/RCS/remote,v retrieving revision 1.1 diff -r1.1 /etc/remote 67a68,70 tty01|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty01:tc=direct:tc=unixhost: Then, on either box, I can do this to get to the console on its neighbour: $ sudo tip tty01 Is this just for boot messages? It's my understanding (minimal, at that) that you can't do this for logins both directions because getty will tie up the port? Greg But he has hostA:tty01 connected to hostB:tty00 and hostB:tty01 connected to hostA:tty00. Each system has two com ports, one for console and one for connecting to the the system's console. Ah, bueno, thanks for pointing that out. I missed the 1s. Greg -- Ticketmaster and Ticketweb suck, but everyone knows that: http://ticketmastersucks.org Dethink to survive - Mclusky
Re: serial port usage
L. V. Lammert wrote: At 12:00 PM 9/14/2007 -0400, Trash Compactor wrote: Alternatively, you can put puc(4) cards into an OpenBSD box or hook up a tangle of ucom(4) adapters to a tree of powered USB hubs There are several multi-port USB-serial adapters available. You can get bus-powered ones up to around 8 DB9 *OR* you can save yourself a ton of heacaches and get a 'Terminal Server' (as many ports as you wish) at the surplus store for $10-$50US. Route it's traffic through an OBSD machine with - problem solved. In case memory is short, in the old days users HAD actual ASCII terminals ON their desk to do work g, which got done quickly efficiently! None of this network stuff, virii, spam, Internet Exploder, or other Windoze attack-atracting tools. Lee I still like keeping machine count and power usage to a minimum. I am close to my cabinet's power allotment and if I install some older, power-hungry terminal server I will have to add another circuit. That $25 terminal server could wind up causing me an additional $100/month for the extra power circuit. Acquisition costs are only a small fraction of overall operating costs. /Jason
Re: serial port usage
On 2007/09/14 13:48, Trash Compactor wrote: L. V. Lammert wrote: At 12:00 PM 9/14/2007 -0400, Trash Compactor wrote: Alternatively, you can put puc(4) cards into an OpenBSD box or hook up a tangle of ucom(4) adapters to a tree of powered USB hubs There are several multi-port USB-serial adapters available. You can get bus-powered ones up to around 8 DB9 *OR* you can save yourself a ton of heacaches and get a 'Terminal Server' (as many ports as you wish) at the surplus store for $10-$50US. Route it's traffic through an OBSD machine with - problem solved. In case memory is short, in the old days users HAD actual ASCII terminals ON their desk to do work g, which got done quickly efficiently! None of this network stuff, virii, spam, Internet Exploder, or other Windoze attack-atracting tools. Lee I still like keeping machine count and power usage to a minimum. I am close to my cabinet's power allotment and if I install some older, power-hungry terminal server I will have to add another circuit. That $25 terminal server could wind up causing me an additional $100/month for the extra power circuit. Acquisition costs are only a small fraction of overall operating costs. an old 2509/11 and a soekris 4801 draw under 0.2A here (nominally 240v, more like 230 in reality). 1U for the cisco, the soekris will squeeze in anywhere, and it's an easy 1-man job to rack (and easy to carry in a rucksack which makes things easier if you're, say, travelling by train) multiple low-density puc(4) you'd need a bigger PC which I bet would draw more power than this. if you can get multiport puc(4) (Wim has them) you can get 8 ports out of a soekris which is probably about the most power-efficient way. USB - the number of boxes I've had to disable USB on to stabilise, this would not usually be my first choice. ymmv, as they say (-:
Re: serial port usage
On Fri, Sep 14, 2007 at 10:03:00AM -0700, Greg Thomas wrote: $ sudo tip tty01 Is this just for boot messages? It's my understanding (minimal, at that) that you can't do this for logins both directions because getty will tie up the port? Nope, full access as connecting from tty01 on one box to tty00 on the other. As the cables are crossed it is the same for each box: 2 null modem serial cables, cross connected thusly: box-a pccom0 connected to box-b pccom1 box-b pccom0 connected to box-a pccom1 $ hostname teak.kepax.co.uk $ sudo tip tty01 Password: connected OpenBSD/i386 (birch.kepax.co.uk) (tty00) login: root Password: Last login: Thu Sep 13 20:43:05 on ttyp0 from teak.kepax.co.uk OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. You have new mail. Terminal type? [vt220] # tip tty01 connected OpenBSD/i386 (teak.kepax.co.uk) (tty00) login: wonkey-donkey Password: Last login: Fri Sep 14 20:42:34 on ttyp2 from 192-168-253-150.dhcp.kepax.co.uk OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. You have new mail. $ Nice eh? -- Craig Skinner | http://www.kepax.co.uk | [EMAIL PROTECTED]
Re: serial port usage
Darren Spruell wrote: ... If cua00 is the right device to use when connecting out, why the missing phone number error? That means your /etc/remote file is still at its defaults (which perhaps should change): tty00|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/tty00:tc=direct:tc=unixhost: cua00|For hp300,i386,mac68k,macppc,mvmeppc,vax:\ :dv=/dev/cua00:tc=dialup:tc=unixhost: See, when you do tip tty00, you aren't actually saying, use port tty00, you are saying, use /etc/remote entry tty00, which just so happens to point to port tty00. It doesn't need to. You could really mess with someone. :) Try doing this: # tip tty01 tip: unknown host tty01 unknown HOST, not unknown port (this machine has a second com port). The tc=dialup is what is hurting you. Just change it to direct. Depending upon your cable and needs, you may not ever care, but cua is more forgiving. Nick.
Re: serial port usage
As we are on the subject and I do not want to deviate from the original question, I would however appreciate suggestions as to how I can have a one server witch can actually have up to 32 serial console to control LOM on Sun server. I may need up to 48 in one case, but instead of using a bunch of Cisco 2509 and 2511, I would much prefer using one good OpenBSD server with proper PF, etc to have the same console control on legacy Sun boxes. I have been looking for some time and still the best way I found was to still use old Cisco routers for that. Any clue stick would be nice if any ideas are better then this. Thanks Daniel
