Re: USB "null modem" cables and related Linux driver questions
On Monday, June 18, 2018 08:44:20 AM Michael Stone wrote: > He really doesn't want a sensible solution, just let it go. +1
Re: USB "null modem" cables and related Linux driver questions
On 06/18/2018 07:17 AM, David wrote:
On 1 June 2018 at 00:21, Richard Owlett wrote:
I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.
What is the make and model number of each computer?
No longer a relevant question.
I have purchased a cable based on the Prolific PL-25A1 chipset.
Current kernels can make it look like an Ethernet connection.
Once I finish some configuration homework {primary motivation has
shifted to education} I'll be able to have a client-server setup.
Re: USB "null modem" cables and related Linux driver questions
On Mon, Jun 18, 2018 at 10:17:21PM +1000, David wrote: On 1 June 2018 at 00:21, Richard Owlett wrote: I have two computers with USB ports. I wish them to communicate as simply as mid-20th-century computers did. What is the make and model number of each computer? He really doesn't want a sensible solution, just let it go.
Re: USB "null modem" cables and related Linux driver questions
On 1 June 2018 at 00:21, Richard Owlett wrote: > > I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers did. What is the make and model number of each computer?
Re: USB "null modem" cables and related Linux driver questions
On Thu, Jun 07, 2018 at 08:07:15AM +0100, Tixy wrote: On Wed, 2018-06-06 at 22:26 -0600, Joe Pfeiffer wrote: Richard Owlett writes: > I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers > did. > Then we used RS232-C with a null modem &/or appropriate software > software at both ends. > > The underlying problem is that both ends egotistically expect to be > *MASTER*. > > The hardware problem is solvable > [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm]. Given how FTDI does things, I'd be really surprised if this didn't meet your desires. Have you actually tried it? Are you sure there is no driver in the kernel? There is a driver in Linux because, from what the datasheet says, that cable is two of FTDIs standard USB-to-serial chips wired together. I.e. it's equivalent to getting 2 USB to serial cables and connecting them with a null modem cable. Yes, that's right. I have no idea why someone would want to do that, but that's exactly what it is. There are also usb transfer cables which are basically a proprietary FIFO buffer with a usb master on both sides, which allow higher speed networking. (Which at least seems more useful than going through a RS-232 conversion, but much more limited than an actual network. In some cases where you want more than gigabit speeds and will never have more than two computers it might be useful. I'm not sure how many of them can connect machines with different OSs, either. This is the "laplink" style connection.) If you want a true, standardized, network session over your peripheral connection, then get firewire. (This is what not having a bus master allows.) It'll be old hardware, because it turns out that nobody actually wanted to pay more so that every device could be a master, and so firewire died. But once upon a time, this was one of its big advantages over usb. Mike Stone
Re: USB "null modem" cables and related Linux driver questions
On 2018-06-07, Joe Pfeiffer wrote: > > This depends on what you mean by "universal". It was intended to be a > protocol for computers to use to communicate with peripherals; > "universal" in this context was restricted to peripherals. And to the planet earth rather than all the way to the furthest reaches of the cosmos and back as I doubt whether the folks living out by Kepler-16 have much use for them.
Re: USB "null modem" cables and related Linux driver questions
On Wed, 2018-06-06 at 22:26 -0600, Joe Pfeiffer wrote: > Richard Owlett writes: > > > I have two computers with USB ports. > > I wish them to communicate as simply as mid-20th-century computers > > did. > > Then we used RS232-C with a null modem &/or appropriate software > > software at both ends. > > > > The underlying problem is that both ends egotistically expect to be > > *MASTER*. > > > > The hardware problem is solvable > > [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm]. > > Given how FTDI does things, I'd be really surprised if this didn't > meet > your desires. Have you actually tried it? Are you sure there is no > driver in the kernel? There is a driver in Linux because, from what the datasheet says, that cable is two of FTDIs standard USB-to-serial chips wired together. I.e. it's equivalent to getting 2 USB to serial cables and connecting them with a null modem cable. -- Tixy
Re: USB "null modem" cables and related Linux driver questions
Richard Owlett writes: > On 06/01/2018 08:21 AM, to...@tuxteam.de wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote: The one choice you have is that one of both sides takes a step back and plays "gadget" [...] >> >>> The gadget API is the programming API offered by the kernel for the OTG >>> ports: no OTG => no gadget! >>> [OTG] >> >>> More importantly, the USB ports which support OTG are driven by >>> different hardware. >> >> Ah, so the hardware has to play along... >> >>> Right, you need both your hardware's USB port to support OTG and you >>> need your kernel to have a driver that supports this hardware. >>> AFAIK the driver is usually available. >> >> Did I say I was handwaving? >> >> Thanks for the clarifications! >> > > It also suggests that I frequently grasp some of the implications of > what I read. Thank you. > As an illustration of my mindset: > If they had really intended USB to be *UNIVERSAL* serial bus, then it > should have been OTG from the get go. > P.S. I know of thousands of reasons they did not. > Vast majority preceded by $ ;/ This depends on what you mean by "universal". It was intended to be a protocol for computers to use to communicate with peripherals; "universal" in this context was restricted to peripherals.
Re: USB "null modem" cables and related Linux driver questions
Richard Owlett writes: > I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers did. > Then we used RS232-C with a null modem &/or appropriate software > software at both ends. > > The underlying problem is that both ends egotistically expect to be > *MASTER*. > > The hardware problem is solvable > [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm]. Given how FTDI does things, I'd be really surprised if this didn't meet your desires. Have you actually tried it? Are you sure there is no driver in the kernel? As for your actual needs... if you want two computers to communicate, you really ought to be using some sort of networking hardware. You've got a computer with a USB port, no serial port, and no ethernet or wifi?
Re: USB "null modem" cables and related Linux driver questions
On Fri 01 Jun 2018 at 09:08:53 (-0500), Richard Owlett wrote: > On 06/01/2018 08:21 AM, to...@tuxteam.de wrote: > >On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote: > >>>The one choice you have is that one of both sides takes a step > >>>back and plays "gadget" [...] > > > >>The gadget API is the programming API offered by the kernel for the OTG > >>ports: no OTG => no gadget! > >> > >>>[OTG] > > > >>More importantly, the USB ports which support OTG are driven by > >>different hardware. > > > >Ah, so the hardware has to play along... > > > >>Right, you need both your hardware's USB port to support OTG and you > >>need your kernel to have a driver that supports this hardware. > >>AFAIK the driver is usually available. > > > >Did I say I was handwaving? > > > >Thanks for the clarifications! > > > > It also suggests that I frequently grasp some of the implications of > what I read. Thank you. > As an illustration of my mindset: > If they had really intended USB to be *UNIVERSAL* serial bus, then > it should have been OTG from the get go. > P.S. I know of thousands of reasons they did not. > Vast majority preceded by $ ;/ I think you're misunderstanding the use of the word universal. USB was designed to be a universal way of connecting "any" peripherals to a PC (sensu lato) which acts as a unique, controlling host for them. It wasn't designed to duplicate networking hardware, communicating between multiple hosts. Nor was OTG. OTG was designed to allow, for example, what's normally a peripheral to be disconnected from the host, be connected to a peripheral and effectively become a host controlling it. Eg, a camera could act as a peripheral while uploading photos to a PC, then act as a host when connected to an inkjet to print them. Cheers, David.
Re: USB "null modem" cables and related Linux driver questions
On Fri, Jun 01, 2018 at 02:16:47PM -0500, Richard Owlett wrote: USB-Ethernet dongles would be a lot more useful in the long term than USB-Serial dongles. *WHO* said anything about a "USB-Serial dongle"? I want a USB-USB object. Subtle, but important, distinction. Well, you started out talking about RS232 and null modem cables, so don't be surprised if people are having trouble figuring out what you're asking for. Then you asked for better ideas. Then you got mad about all the ideas and started laughing hysterically. I have no idea what you actually want at this point. RS-232 had a really good 40 year run, but for general communications it was mostly obsolete nearly 20 years ago. You mentioned file transfers- So what? I get grief for not mentioning immediate goals. I casually mention a potential use and get *UNIVERSAL ADVICE*: Don't do that. ! So you can't articulate what you're trying to do at all? That will certainly reduce the odds of getting helpful advice. It seems like you want to connect two computers via USB "just because". Good luck with that. Mike Stone
Re: USB "null modem" cables and related Linux driver questions
Richard, On Fri, Jun 01, 2018 at 02:16:47PM -0500, Richard Owlett wrote: > On 06/01/2018 09:01 AM, Michael Stone wrote: > >I can't think of any applications where that's going to be better > >over a pair of USB-Serial dongles than a pair of USB-Ethernet > >dongles. > > Please read my stated goals. > Not my PREsumed goals. > *ROFL* Laugh all you want at people trying to help you, but time and time again you end up posting volumes of text here without finding a solution because you suck at concisely describing what you want to achieve. Everyone else fails to understand you, every time, so is everyone just stupid, or is it that the common factor here is you? Your first email said you wanted your machines to "communicate". That's as specific as you got. Dan then tried to narrow it down to one specific form of communication by spending a lot of their time listing out everything they could think of that you might have meant, and you replied, "Your list pretty much covers it." Useless and frustrating. Then Stefan tried: > > What kind of "communicate" do you need there? Your response? > Essentially any :/ I don't know what kind of response you expect to that uselessly vague comment. By doing that you force people to spend a lot of their time trying to cover every base, and then you complain at them when they try. It really seems like you just want to complain when people try their best to help you, even against your best efforts. I expect to just get a barrel of whinging back for this, but I hate to write a totally useless email myself, so… You mentioned you want to transfer files. If both machines have Ethernet interfaces then (as you've already been advised) the simplest, most reliable and most performant way will be direct Ethernet connection, or connection via a switch. If file transfer is your goal, no need to bother with USB. If somehow these machines don't both have Ethernet and USB really is the only way, then again as you've already been advised, USB Ethernet is the way to go. We are now leaving the realms of simplicity and performance for more subjective lands of doing things "just because" or for the retro computing experience. You can certainly use a pair of USB serial adaptors and then run a null modem cable between them, then run PPP over that. Absolutely no idea why you would want to do this rather than run Ethernet over USB. Instead of PPP you could use more arcane forms of serial data transfer like zmodem or kermit. If it's just a console you want, i.e. the console output and login prompt from one machine to appear in a serial terminal program on the other, then you can do that over Ethernet too! See "netconsole". For a serial console when you don't have Ethernet (or want it separate from the Ethernet infrastructure) then again it's USB serial dongles on both ends, a null modem cable in between, then use a serial terminal emulator like minicom or screen on the end you want to be the client. There are configuration details involved for the server end to get it to send console output to this USB-serial, and put a login prompt on it. Ask which parts you need more info on. Please be specific. Please don't make this harder than it needs to be! Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: USB "null modem" cables and related Linux driver questions
On 06/01/2018 09:01 AM, Michael Stone wrote: On Fri, Jun 01, 2018 at 04:56:32AM -0500, Richard Owlett wrote: On 05/31/2018 06:58 PM, David Wright wrote: (thanks for your link) gives an idea of the price, and in this case I can see some justification for it because they describe the electronics hidden inside the plugs (we hope). But considering that two NICs cost less than that cable, I'd need a pressing reason to purchase the cable instead. There is a perceived elegance aspect. There is also a practical aspect the only known working and 8>> conveniently physically accessible ports are USB. USB-Ethernet dongles would be a lot more useful in the long term than USB-Serial dongles. *WHO* said anything about a "USB-Serial dongle"? I want a USB-USB object. Subtle, but important, distinction. RS-232 had a really good 40 year run, but for general communications it was mostly obsolete nearly 20 years ago. You mentioned file transfers- So what? I get grief for not mentioning immediate goals. I casually mention a potential use and get *UNIVERSAL ADVICE*: Don't do that. ! -I can't think of any applications where that's going to be better over a pair of USB-Serial dongles than a pair of USB-Ethernet dongles. Please read my stated goals. Not my PREsumed goals. *ROFL* Mike Stone
Re: USB "null modem" cables and related Linux driver questions
On Friday 01 June 2018 06:20:59 Richard Owlett wrote: > On 05/31/2018 10:07 PM, Stefan Monnier wrote: > >> I have two computers with USB ports. > >> I wish them to communicate as simply as mid-20th-century computers > >> did. > > > > What kind of "communicate" do you need there? > > Essentially any ;/ > In fact one of the thought experiments I was pursuing was how to do > file copying/sharing over RS232 - even I would not actually attempt to > implement. Other than speed of the copy while the error correction verify's it sector by sector, why not. Both rsync and rzsz are quite capable of sending a file halfway around the planet with the last 17 miles on a barbed wire fence. And getting identical crc's in the final check. For a circuit that was actually that dirty, I think I'd choose rzsz as its default packet size is 256 bytes. If the crc of that packet fails, it requests a resend until it gets it right. So does rsync, but rsync's default packet is 64k, demanding a far cleaner path. rzsz unforch has several cousins 3x removed, so there is less than 100% compatibility. And the linux version is one of the worse compatibility violators. > > The "way back machine" to simulate a "null modem" serial cable > > exists, as you've seen, but it's rarely the best solution for > > nowadays's needs, > > "Best" is not an invariant absolute. > > > since nowadays connecting two computers is something completely > > normal, supported by a deluge of tools, but they all expect a > > "network" connection rather than a serial cable. > > > > In most cases those two computers also have ethernet or wifi "ports" > > so you can connect them via such a network (which usually offers > > faster transmission than a serial cable, lets you seamlessly > > multiplex several connections, and lets you use the many tools > > working over the network to connect computers). > > An explicit requirement is a wired, NOT WiFi, connection. > I that seriously. My internet access is a WiFi hotspot with its WiFi > capability disabled. > > > In some cases one of the two computers's USB port is an "OTG" port, > > meaning that it can act either as "master" or not, in which case you > > can just use a regular USB cable (and usually you then configure the > > OTG side to pretend it's a network card, so it ends up looking to > > the software like you've connected the two machines via an ethernet > > cable. That's what I use between my BananaPi "router" and my office > > desktop). > > I saw it and it meets most (all?) my requirements except my reading > suggested: >1. obsolete >2. available only for Windows/Mac >3. no way to determine if any of machines were equipped > > > If none of that are options, you can resort to using an "ethernet > > dongle" on both sides and an ethernet cable between the two. > > That's a 1 versus 3 items required per connection. > > > All of those things will typically work "out of the box" on a > > vanilla Linux kernel (the usbnet drivers have been incorporated > > years ago). > > > > Oh, and in case those computers are somewhat old, they may also come > > with Firewire ports, and those (contrary to USB) don't have the > > "slave/master" distinction so you can connect your computers this > > way with a plain normal Firewire cable (and make it appear to the > > software, again, as some kind of ethernet-like connection). > > > > > > Stefan -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: USB "null modem" cables and related Linux driver questions
On Fri, 1 Jun 2018 10:01:57 -0400 Michael Stone wrote: > On Fri, Jun 01, 2018 at 04:56:32AM -0500, Richard Owlett wrote: > >On 05/31/2018 06:58 PM, David Wright wrote: > >>(thanks for your link) gives an idea of the price, and in this case > >>I can see some justification for it because they describe the > >>electronics hidden inside the plugs (we hope). > >> > >>But considering that two NICs cost less than that cable, I'd need a > >>pressing reason to purchase the cable instead. > > > >There is a perceived elegance aspect. > >There is also a practical aspect the only known working and > >conveniently physically accessible ports are USB. > > USB-Ethernet dongles would be a lot more useful in the long term than > USB-Serial dongles. RS-232 had a really good 40 year run, but for > general communications it was mostly obsolete nearly 20 years ago. > You mentioned file transfers--I can't think of any applications where > that's going to be better over a pair of USB-Serial dongles than a > pair of USB-Ethernet dongles. > > Radio? This gadget: https://www.lensadaptor.com/mtf-effect-control-unit-3-kit uses straight point-to-point 8-bit serial over Zigbee type RF tranceivers. Bluetooth is basically 8-bit serial over radio, though with a very short range. -- Joe https://en.wikipedia.org/wiki/Zigbee
Re: USB "null modem" cables and related Linux driver questions
On Fri 01 Jun 2018 at 05:26:01 (-0500), Richard Owlett wrote:
> On 06/01/2018 01:27 AM, deloptes wrote:
> >Richard Owlett wrote:
> >
> >>I have two computers with USB ports.
> >>I wish them to communicate as simply as mid-20th-century computers did.
> >>Then we used RS232-C with a null modem &/or appropriate software
> >>software at both ends.
> >>
> >
> >J., why not take a crossover cable - all pcs have now ethernet port
> >
> >https://en.wikipedia.org/wiki/Ethernet_crossover_cable
> >
> >
>
> Some combinations require crossover cable, some don't.
> I investigated that and wen so fa as to purchase a {still shrink
> wrapped} 8-port switch as a solution. Decided clutter not worth it.
Just forget anyone said "crossover cable¹". You'd have to be making a
direct connection between two museum pieces to require one, and as
you have a switch, you have absolutely no need to ever do that.
Coonect both to the switch instead.
Accessibility? Using the NIC (usually at the back), it gets inserted
permanently and then forgotten, rather than needing to be inserted
on each occasion you want connectivity. Tidier too.
Bear in mind you're using the hardware as intended: no risk of
blowing up your USB port. (Ever noticed how often flaky USB ports
are mentioned here?)
You might even find you can use wakeonlan on the desktop PCs
to save some power.
¹ If you *have* obtained one, just use it like an ordinary cable nowadays.
Cheers,
David.
Re: USB "null modem" cables and related Linux driver questions
On 06/01/2018 08:21 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote: The one choice you have is that one of both sides takes a step back and plays "gadget" [...] The gadget API is the programming API offered by the kernel for the OTG ports: no OTG => no gadget! [OTG] More importantly, the USB ports which support OTG are driven by different hardware. Ah, so the hardware has to play along... Right, you need both your hardware's USB port to support OTG and you need your kernel to have a driver that supports this hardware. AFAIK the driver is usually available. Did I say I was handwaving? Thanks for the clarifications! It also suggests that I frequently grasp some of the implications of what I read. Thank you. As an illustration of my mindset: If they had really intended USB to be *UNIVERSAL* serial bus, then it should have been OTG from the get go. P.S. I know of thousands of reasons they did not. Vast majority preceded by $ ;/
Re: USB "null modem" cables and related Linux driver questions
On Fri, Jun 01, 2018 at 04:56:32AM -0500, Richard Owlett wrote: On 05/31/2018 06:58 PM, David Wright wrote: (thanks for your link) gives an idea of the price, and in this case I can see some justification for it because they describe the electronics hidden inside the plugs (we hope). But considering that two NICs cost less than that cable, I'd need a pressing reason to purchase the cable instead. There is a perceived elegance aspect. There is also a practical aspect the only known working and conveniently physically accessible ports are USB. USB-Ethernet dongles would be a lot more useful in the long term than USB-Serial dongles. RS-232 had a really good 40 year run, but for general communications it was mostly obsolete nearly 20 years ago. You mentioned file transfers--I can't think of any applications where that's going to be better over a pair of USB-Serial dongles than a pair of USB-Ethernet dongles. Mike Stone
Re: USB "null modem" cables and related Linux driver questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote: > > The one choice you have is that one of both sides takes a step > > back and plays "gadget" [...] > The gadget API is the programming API offered by the kernel for the OTG > ports: no OTG => no gadget! > > > [OTG] > More importantly, the USB ports which support OTG are driven by > different hardware. Ah, so the hardware has to play along... > Right, you need both your hardware's USB port to support OTG and you > need your kernel to have a driver that supports this hardware. > AFAIK the driver is usually available. Did I say I was handwaving? Thanks for the clarifications! Cheers - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlsRSHYACgkQBcgs9XrR2kYP9ACfb7mVtI1Qu/CjDeTIB5uoyOPv jNYAni1/EbprNJ8Gu6DuHMfyWoO+tCGP =dhmw -END PGP SIGNATURE-
Re: USB "null modem" cables and related Linux driver questions
> The one choice you have is that one of both sides takes a step > back and plays "gadget" (the jargon term, somewhat unfortunate > as search engine fodder). There seems to be something out there > for that, e.g. [2]. The gadget API is the programming API offered by the kernel for the OTG ports: no OTG => no gadget! > The other choice seems to be USB On The Go (aka "OTG") [3]. > You seem to need a special cable for that. More importantly, the USB ports which support OTG are driven by different hardware. > There seem to be Linux drivers to let the USB "stack" play along > with OTG [4], but I have no experience whatsoever with this Right, you need both your hardware's USB port to support OTG and you need your kernel to have a driver that supports this hardware. AFAIK the driver is usually available. Stefan
Re: USB "null modem" cables and related Linux driver questions
>> In some cases one of the two computers's USB port is an "OTG" port, >> meaning that it can act either as "master" or not, in which case you can >> just use a regular USB cable (and usually you then configure the OTG >> side to pretend it's a network card, so it ends up looking to the >> software like you've connected the two machines via an ethernet cable. >> That's what I use between my BananaPi "router" and my office desktop). > > I saw it and it meets most (all?) my requirements except my reading > suggested: > 1. obsolete > 2. available only for Windows/Mac > 3. no way to determine if any of machines were equipped Not obsolete at all. Availability has nothing to do with the OS (I never use either of macOS or Windows). But yes, OTG rare (read: non-existing) on laptops/desktops. They're very common on "embedded systems" which are expected to be (occasionally) plugged into a computer. E.g. many phones's USB port is OTG. >> If none of that are options, you can resort to using an "ethernet >> dongle" on both sides and an ethernet cable between the two. > That's a 1 versus 3 items required per connection. I just gave you alternatives. You'll let you decide what's better for your planned use cases. Stefan
Re: USB "null modem" cables and related Linux driver questions
On 06/01/2018 01:27 AM, deloptes wrote:
Richard Owlett wrote:
I have two computers with USB ports.
I wish them to communicate as simply as mid-20th-century computers did.
Then we used RS232-C with a null modem &/or appropriate software
software at both ends.
J., why not take a crossover cable - all pcs have now ethernet port
https://en.wikipedia.org/wiki/Ethernet_crossover_cable
Some combinations require crossover cable, some don't.
I investigated that and wen so fa as to purchase a {still shrink
wrapped} 8-port switch as a solution. Decided clutter not worth it.
Re: USB "null modem" cables and related Linux driver questions
On 05/31/2018 10:07 PM, Stefan Monnier wrote: I have two computers with USB ports. I wish them to communicate as simply as mid-20th-century computers did. What kind of "communicate" do you need there? Essentially any ;/ In fact one of the thought experiments I was pursuing was how to do file copying/sharing over RS232 - even I would not actually attempt to implement. The "way back machine" to simulate a "null modem" serial cable exists, as you've seen, but it's rarely the best solution for nowadays's needs, "Best" is not an invariant absolute. since nowadays connecting two computers is something completely normal, supported by a deluge of tools, but they all expect a "network" connection rather than a serial cable. In most cases those two computers also have ethernet or wifi "ports" so you can connect them via such a network (which usually offers faster transmission than a serial cable, lets you seamlessly multiplex several connections, and lets you use the many tools working over the network to connect computers). An explicit requirement is a wired, NOT WiFi, connection. I that seriously. My internet access is a WiFi hotspot with its WiFi capability disabled. In some cases one of the two computers's USB port is an "OTG" port, meaning that it can act either as "master" or not, in which case you can just use a regular USB cable (and usually you then configure the OTG side to pretend it's a network card, so it ends up looking to the software like you've connected the two machines via an ethernet cable. That's what I use between my BananaPi "router" and my office desktop). I saw it and it meets most (all?) my requirements except my reading suggested: 1. obsolete 2. available only for Windows/Mac 3. no way to determine if any of machines were equipped If none of that are options, you can resort to using an "ethernet dongle" on both sides and an ethernet cable between the two. That's a 1 versus 3 items required per connection. All of those things will typically work "out of the box" on a vanilla Linux kernel (the usbnet drivers have been incorporated years ago). Oh, and in case those computers are somewhat old, they may also come with Firewire ports, and those (contrary to USB) don't have the "slave/master" distinction so you can connect your computers this way with a plain normal Firewire cable (and make it appear to the software, again, as some kind of ethernet-like connection). Stefan
Re: USB "null modem" cables and related Linux driver questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jun 01, 2018 at 08:27:13AM +0200, deloptes wrote: > Richard Owlett wrote: > > > I have two computers with USB ports. > > I wish them to communicate as simply as mid-20th-century computers did. > > Then we used RS232-C with a null modem &/or appropriate software > > software at both ends. > > > > J., why not take a crossover cable - all pcs have now ethernet port FWIW these days, most devices are capable of doing the crossover thing automatically [1], so you can just use a straight cable. From personal experience, I haven't needed a crossover cable the last ten years (and I do muck around with oldish hardware). Cheers [1] https://en.wikipedia.org/wiki/Medium_Dependent_Interface#Auto_MDI-X - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlsRAmAACgkQBcgs9XrR2kbpPwCfYH3wQicOhfiQrgAvcDUPytCZ 29YAn0sYNXgIXIFfMDq3tt5wCJUKM8DK =tkoi -END PGP SIGNATURE-
Re: USB "null modem" cables and related Linux driver questions
Richard Owlett wrote: > I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers did. > Then we used RS232-C with a null modem &/or appropriate software > software at both ends. > J., why not take a crossover cable - all pcs have now ethernet port https://en.wikipedia.org/wiki/Ethernet_crossover_cable
Re: USB "null modem" cables and related Linux driver questions
> If none of that are options, you can resort to using an "ethernet > dongle" on both sides and an ethernet cable between the two. [ If one of the two computers has a free ethernet port, you can of course also such a dongle on the other computer. ] BTW, those ethernet dongles can be found pretty cheaply (like $10 or less) and they can be handy in many cases to add an ethernet port (or several ports, even). IOW, it's a good tool to have in your box. Stefan
Re: USB "null modem" cables and related Linux driver questions
> I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers did. What kind of "communicate" do you need there? The "way back machine" to simulate a "null modem" serial cable exists, as you've seen, but it's rarely the best solution for nowadays's needs, since nowadays connecting two computers is something completely normal, supported by a deluge of tools, but they all expect a "network" connection rather than a serial cable. In most cases those two computers also have ethernet or wifi "ports" so you can connect them via such a network (which usually offers faster transmission than a serial cable, lets you seamlessly multiplex several connections, and lets you use the many tools working over the network to connect computers). In some cases one of the two computers's USB port is an "OTG" port, meaning that it can act either as "master" or not, in which case you can just use a regular USB cable (and usually you then configure the OTG side to pretend it's a network card, so it ends up looking to the software like you've connected the two machines via an ethernet cable. That's what I use between my BananaPi "router" and my office desktop). If none of that are options, you can resort to using an "ethernet dongle" on both sides and an ethernet cable between the two. All of those things will typically work "out of the box" on a vanilla Linux kernel (the usbnet drivers have been incorporated years ago). Oh, and in case those computers are somewhat old, they may also come with Firewire ports, and those (contrary to USB) don't have the "slave/master" distinction so you can connect your computers this way with a plain normal Firewire cable (and make it appear to the software, again, as some kind of ethernet-like connection). Stefan
Re: USB "null modem" cables and related Linux driver questions
On Thu, May 31, 2018 at 09:21:27AM -0500, Richard Owlett wrote: > I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers did. > Then we used RS232-C with a null modem &/or appropriate software software > at both ends. > > The underlying problem is that both ends egotistically expect to be > *MASTER*. > > The hardware problem is solvable [e.g. > http://www.ftdichip.com/Products/Cables/USBtoUSB.htm]. > > The software is another case :< > The best Linux specific link I've found is dated September 2005 > [http://www.linux-usb.org/usbnet/] > > I've done DuckDuckGo searches for permutations/combinations of > usb, "peer to peer", lan, and bridge. > Most is Windows/Mac centric. > There were hints that needed drivers may exist in current Linux core. > > Pointers to good references and/or better search terms? Do you want: - One end is a terminal, the other end offers login? "agetty serial" and "minicom" - TCP/IP over RS-232 serial? Keyword is "PPP". - TCP/IP over ethernet attached via USB? "usbnet" and treat them like ethernet adapters. - Connect an actual hardware terminal like a VT320 to your Linux box? "agetty serial" again. - Something else? Describe it. -dsr-
Re: USB "null modem" cables and related Linux driver questions
Hi. On Thu, May 31, 2018 at 09:21:27AM -0500, Richard Owlett wrote: > I have two computers with USB ports. > I wish them to communicate as simply as mid-20th-century computers did. > Then we used RS232-C with a null modem &/or appropriate software software > at both ends. > > The underlying problem is that both ends egotistically expect to be > *MASTER*. I did the thing in the not-so-distant past. It took two USB-RS232 converters (FDTI chipsets should work out of the box), and a conventional RS232 null modem cable. Communication was limited to 112500 bps, but I needed it for the serial console anyway. As for the software part, agetty and minicom were all that was needed. Reco
USB "null modem" cables and related Linux driver questions
I have two computers with USB ports. I wish them to communicate as simply as mid-20th-century computers did. Then we used RS232-C with a null modem &/or appropriate software software at both ends. The underlying problem is that both ends egotistically expect to be *MASTER*. The hardware problem is solvable [e.g. http://www.ftdichip.com/Products/Cables/USBtoUSB.htm]. The software is another case :< The best Linux specific link I've found is dated September 2005 [http://www.linux-usb.org/usbnet/] I've done DuckDuckGo searches for permutations/combinations of usb, "peer to peer", lan, and bridge. Most is Windows/Mac centric. There were hints that needed drivers may exist in current Linux core. Pointers to good references and/or better search terms? TIA
Woody ... Squeeze, PPP works over a null modem; was Re (2): How to use serial ports?
From: peasth...@shaw.ca Date: Fri, 13 May 2011 09:57:26 -0800 > May 13 08:56:14 dalton pppd[2046]: but I couldn't find any suitable secret > (password) for it to use to do so. > > Previously, PPP would refer to /etc/passwd but seems to have forgotten that. In setting up the fresh machine I put this in /etc/ppp/pap-secrets. * dalton1 "" * Should have revised to this when the previous machine was replaced. * dalton "" * All the documentation in the world can't replace human memory. So Tapio, a null modem still works. Start with the simplest configuration and check all the details. Then work your way up to your objective. Regards, ... Peter E. -- Telephone 1 360 450 2132. bcc: peasthope at shaw.ca Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057005.44328.43208@cantor.invalid
Null modem cable; was Re (2): Serial Connection -- shielding
Abbass, > I migth need to check the cables but I think it's the standard Null modem. Yes, check the cable wiring with an ohmeter. All the hope in the world won't help. As Stephen said, > You need to find out > *exactly* how your cross-over cable or null modem is wired. There may > be some asymmetry in the wiring that causes the cable to behave differently > in opposite directions. The wiring should be symmetrical ... Symmetrical from end to end. Study this article, check the cable with an ohmeter and sketch the wiring to be sure. "http://en.wikipedia.org/wiki/Null_modem"; Regards, ... Peter E. -- Telephone 1 360 450 2132. Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056958.34229.31981@cantor.invalid
Re: Serial port connection (null modem) not working
On Aug 24, 2007, at 10:30 AM, Ken Irving wrote: On Fri, Aug 24, 2007 at 08:48:42AM -0800, Ken Irving wrote: On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote: As an alternative to minicom, 'screen' also makes a useful serial terminal program. At least on OS X, I often do something like this to talk to routers and the like: screen /dev/tty.usbserial 9600 "Ctrl-A Shift-K" will exit. "Ctrl-A i" will give you a nice little display of what the serial control lines are doing. I haven't tried it under Linux, but it should work the same. Of course you'd substitute /dev/ttyS0 or whatever device you're using for /dev/tty.usbserial. I tried it on a sid box, but just end up with screen showing a shell on the local host, i.e., the same as without those arguments. I googled for the Mac OS X screen manpage thinking it must be different, but it's identical to the one on my linux box. Any other hints on how that works or where/how it's documented? I learned about it here: http://www.tigoe.net/pcomp/resources/archives/avr/000749.shtml You're right that it doesn't seem to be documented in the manpage. How odd. Maybe it's a compile-time option or something. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On Fri, Aug 24, 2007 at 08:48:42AM -0800, Ken Irving wrote: > On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote: > > As an alternative to minicom, 'screen' also makes a useful serial terminal > > program. At least on OS X, I often do something like this to talk to > > routers and the like: > > screen /dev/tty.usbserial 9600 > > > > "Ctrl-A Shift-K" will exit. "Ctrl-A i" will give you a nice little display > > of what the serial control lines are doing. > > > > I haven't tried it under Linux, but it should work the same. Of course > > you'd substitute /dev/ttyS0 or whatever device you're using for > > /dev/tty.usbserial. > > I tried it on a sid box, but just end up with screen showing a shell on > the local host, i.e., the same as without those arguments. I googled for the Mac OS X screen manpage thinking it must be different, but it's identical to the one on my linux box. Any other hints on how that works or where/how it's documented? -- Ken Irving, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On Aug 24, 2007, at 9:48 AM, Ken Irving wrote: On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote: As an alternative to minicom, 'screen' also makes a useful serial terminal program. At least on OS X, I often do something like this to talk to routers and the like: screen /dev/tty.usbserial 9600 "Ctrl-A Shift-K" will exit. "Ctrl-A i" will give you a nice little display of what the serial control lines are doing. I haven't tried it under Linux, but it should work the same. Of course you'd substitute /dev/ttyS0 or whatever device you're using for /dev/tty.usbserial. I tried it on a sid box, but just end up with screen showing a shell on the local host, i.e., the same as without those arguments. Huh. I tried it on an FC5 box just now and it worked. Must be different builds of 'screen'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote: > As an alternative to minicom, 'screen' also makes a useful serial terminal > program. At least on OS X, I often do something like this to talk to > routers and the like: > screen /dev/tty.usbserial 9600 > > "Ctrl-A Shift-K" will exit. "Ctrl-A i" will give you a nice little display > of what the serial control lines are doing. > > I haven't tried it under Linux, but it should work the same. Of course > you'd substitute /dev/ttyS0 or whatever device you're using for > /dev/tty.usbserial. I tried it on a sid box, but just end up with screen showing a shell on the local host, i.e., the same as without those arguments. Ken -- Ken Irving, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
As an alternative to minicom, 'screen' also makes a useful serial terminal program. At least on OS X, I often do something like this to talk to routers and the like: screen /dev/tty.usbserial 9600 "Ctrl-A Shift-K" will exit. "Ctrl-A i" will give you a nice little display of what the serial control lines are doing. I haven't tried it under Linux, but it should work the same. Of course you'd substitute /dev/ttyS0 or whatever device you're using for /dev/tty.usbserial. It won't trigger nostalgia for Telix the way minicom does, though. ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Serial port connection (null modem) not working
After some testing it turned out that the cable is indeed not properly wired :S I ordered a better one and I'm hoping that it will do the job flawlessly. Thanks for replying! Regards, Fili Btw. the cat/echo is a proposed test by Linux-Ha.org which should work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On Thu, Aug 23, 2007 at 11:17:11AM -0800, Ken Irving wrote: > On Thu, Aug 23, 2007 at 03:06:45PM +, Douglas A. Tutty wrote: > > I have yet to find a ready-made null-modem cable that is actually wired > > correctly for use by UNIX. How it should be wired can be found in > > several places accessible as packages on Debian. > > I've never had any trouble with null modem cables purchased off-the-shelf, > though that may be due to simple requirements. Unless you're doing > something fancy, or maybe using high data rates, many applications really > only need a 3-wire connection, and the other pins shouldn't matter. > I normally disable hardware handshaking, don't need the ring or the > other wired (and swapped) signals. > When I did this, I ran 115200 across a 50 foot serial line so I need the handshaking and hardware flow controll. Granted for a terminal at 9600 three wires is just fine. For a ppp serial link where one would otherwise use Ethernet, a little tweaking gives great results. This setup was for using a laptop without Ethernet for backing up with rsync as well as ssh access. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On Thu, Aug 23, 2007 at 03:06:45PM +, Douglas A. Tutty wrote: > On Thu, Aug 23, 2007 at 03:37:00PM +0200, Fili Wiese wrote: > > I'm having trouble setting up a serial connection between two servers > > using a null modem cable. > > ... > > > > Maybe the (brand-new) null-modem cable is not wired properly but how do > > I find that out? > > > ... > I have yet to find a ready-made null-modem cable that is actually wired > correctly for use by UNIX. How it should be wired can be found in > several places accessible as packages on Debian. I've never had any trouble with null modem cables purchased off-the-shelf, though that may be due to simple requirements. Unless you're doing something fancy, or maybe using high data rates, many applications really only need a 3-wire connection, and the other pins shouldn't matter. I normally disable hardware handshaking, don't need the ring or the other wired (and swapped) signals. Other things to check are the ownership and baud rates. stty can be used to view and change port/terminal settings, but probably the easiest way to check out the connection is by using minicom on both ends. Ken > > Serial-HOWTO > Modem-HOWTO, both in the doc-linux-HOWTO package > Hardware book, available in the hwb package. > > Also, in book form: > Unix System Administration Handbook. Nemeth, Evi, et.al. > > The actual wireing of the cable can be verified with an ohm-meter if you > have both ends of the cable in your hand, or by putting a wrap plug on > one end. The functioning of the link can be verified with minicom. If > you put a wrap plug on one end, and the other end on one of the servers, > you can use minicom and talk to yourself. The signal goes down the > wire, through the wrap plug and back you your box. > > Then you can run minicom at both ends an talk. > > Setting up ppp or something over the wire is a possibility but it won't > provide any further details if you don't need ppp. If you _do_ need > ppp, then the PPP-HOWTO will tell you how to setup a link. Its really > quite easy. Basically you set up mgetty on one box and have ppp on the > other box access it. Since there's no modem, there are no dialing > strings. > > Doug. -- Ken Irving, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On Thu, Aug 23, 2007 at 03:37:00PM +0200, Fili Wiese wrote: > I'm having trouble setting up a serial connection between two servers > using a null modem cable. > This link is needed as a redundant connection for Heartbeat. > Both machines are indentical (both hardware and software). > > In my humble view, everything seems to be set up perfectly. > However, an echo/cat test simply doesn't work: > > server1: echo test >/dev/ttyS0 > server2: cat (no output) > > I'm really at a loss :S > Does anybody have a clue where to look next? > > Maybe the (brand-new) null-modem cable is not wired properly but how do > I find that out? > Since cat doesn't set up the port for use, it won't work. I have yet to find a ready-made null-modem cable that is actually wired correctly for use by UNIX. How it should be wired can be found in several places accessible as packages on Debian. Serial-HOWTO Modem-HOWTO, both in the doc-linux-HOWTO package Hardware book, available in the hwb package. Also, in book form: Unix System Administration Handbook. Nemeth, Evi, et.al. The actual wireing of the cable can be verified with an ohm-meter if you have both ends of the cable in your hand, or by putting a wrap plug on one end. The functioning of the link can be verified with minicom. If you put a wrap plug on one end, and the other end on one of the servers, you can use minicom and talk to yourself. The signal goes down the wire, through the wrap plug and back you your box. Then you can run minicom at both ends an talk. Setting up ppp or something over the wire is a possibility but it won't provide any further details if you don't need ppp. If you _do_ need ppp, then the PPP-HOWTO will tell you how to setup a link. Its really quite easy. Basically you set up mgetty on one box and have ppp on the other box access it. Since there's no modem, there are no dialing strings. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
Fili Wiese wrote: Hello, I'm having trouble setting up a serial connection between two servers using a null modem cable. This link is needed as a redundant connection for Heartbeat. Both machines are indentical (both hardware and software). [cut] I'm really at a loss :S Does anybody have a clue where to look next? Maybe the (brand-new) null-modem cable is not wired properly but how do I find that out? It's fairly simple to check a null MODEM cable: the following URL appears to offer an accurate description, or I could send the information in a PDF file, if required. Peter HB http://www.loop-back.com/null-mod.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serial port connection (null modem) not working
On 08/23/2007 08:37 AM, Fili Wiese wrote: Hello, I'm having trouble setting up a serial connection between two servers using a null modem cable. This link is needed as a redundant connection for Heartbeat. Both machines are indentical (both hardware and software). Some info: - #uname -a Linux galvatron 2.6.18-5-686 #1 SMP Sun Aug 12 21:57:02 UTC 2007 i686 GNU/Linux #ls -al /dev/ttyS0 crw-rw-rw- 1 root dialout 4, 64 2007-08-23 14:56 /dev/ttyS0 #groups dailout (among others) #setserial /dev/ttyS0 /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 #cat /proc/interrupts 4: 4 1IO-APIC-edge serial #cat /proc/ioports 03f8-03ff : serial #cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:16550A port:03F8 irq:4 tx:0 rx:2 brk:2 RTS|DTR|DSR 1: uart:unknown port:02F8 irq:3 2: uart:unknown port:03E8 irq:4 3: uart:unknown port:02E8 irq:3 - In my humble view, everything seems to be set up perfectly. However, an echo/cat test simply doesn't work: server1: echo test >/dev/ttyS0 server2: cat I never tried to use 'cat' to test null-modem connectivity, so I would not vouch for it. Use pppd instead. There are a few things that must be done to the serial port before data can be sent or received, and pppd knows how to do these things. I can't find the document that showed me how to set this up, but this is what I remember having to do: 1. Create an /etc/ppp/options.ttyS0 that configures the serial port for 115200 bps, pap authentication, specific IP addresses for the self and the peer, and 'silent' (wait for a connection). 2. Add the user and host names to /etc/ppp/pap-secrets. 3. Add a line to /etc/inittab to launch the pppd instance like so: pd:2345:respawn:/usr/sbin/pppd /dev/ttyS0 nodetach > /dev/null Except for number three, both machines need these things done to them. The third item might be omitted for the machine to which you have continuous keyboard access. Believe me when I say I wish I could find the "Null Modem FAQ" or whatever it was that showed me how to set this up, because it's quite complicated, and I couldn't do it again if I had to. Maybe you can search Yahoo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Serial port connection (null modem) not working
Hello, I'm having trouble setting up a serial connection between two servers using a null modem cable. This link is needed as a redundant connection for Heartbeat. Both machines are indentical (both hardware and software). Some info: - #uname -a Linux galvatron 2.6.18-5-686 #1 SMP Sun Aug 12 21:57:02 UTC 2007 i686 GNU/Linux #ls -al /dev/ttyS0 crw-rw-rw- 1 root dialout 4, 64 2007-08-23 14:56 /dev/ttyS0 #groups dailout (among others) #setserial /dev/ttyS0 /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 #cat /proc/interrupts 4: 4 1IO-APIC-edge serial #cat /proc/ioports 03f8-03ff : serial #cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:16550A port:03F8 irq:4 tx:0 rx:2 brk:2 RTS|DTR|DSR 1: uart:unknown port:02F8 irq:3 2: uart:unknown port:03E8 irq:4 3: uart:unknown port:02E8 irq:3 - In my humble view, everything seems to be set up perfectly. However, an echo/cat test simply doesn't work: server1: echo test >/dev/ttyS0 server2: cat To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Woody->FreeBSD box via null modem cable
On Mon, Dec 30, 2002 at 02:14:02PM +0100, Holger Rauch wrote: > Hi! > > I would like to connect to a FreeBSD box from Woody using a null modem > cable. The FreeBSD box is already set up properly (a getty is running on > one of the serial ports). The serial cable is connected to ttyS1 on my > Debian box. I tried to set things up using "minicom -s": > > 1. I entered the serial port the cable is connected to (on my Debian box): > /dev/ttyS1 > 2. I set the modem init string to the empty string. > > Do I need any other software package besides "minicom" on my Debian box? Is > there some article/howto explaining null modem cable setups in greater > detail? (I was looking at the serial port console howto, but this one > covers only the pin layout for null modem cables. Besides, this howto > mostly deals with redirecting *boot* messages to the serial console, which > is not what I'm interested in.) You could also set up slip (serial line IP) networking between the two computers over the serial port using slattach (in the net-tools package). See the Net-HOWTO for details. This typically is limited to ~115 kbps data transfers. You could then use telnet, ssh, ftp, etc. A pair of cheap NICS and a crossover cable will offer better performance, however. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Woody->FreeBSD box via null modem cable
Holger Rauch said: > Hi! > > I would like to connect to a FreeBSD box from Woody using a null modem > cable. The FreeBSD box is already set up properly (a getty is running on > one of the serial ports). The serial cable is connected to ttyS1 on my > Debian box. I tried to set things up using "minicom -s": no other software is required. freebsd, like most other systems default to 9600 for the serial port. so be sure minicom is configured for 9600/8/N/1. Also it helps to disable flow control(both hardware and software). if the null modem cable works, and the serial ports on both system works you will get a prompt. One system I have one of the pins(or perhaps more) of the serial port is dead, so I could transmit, but not recieve, I discovered this by running strace on the serial getty process and saw my characters comming through, but they didn't show up on my local screen. using the other serial port resolved that problem though. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Woody->FreeBSD box via null modem cable
Hi! I would like to connect to a FreeBSD box from Woody using a null modem cable. The FreeBSD box is already set up properly (a getty is running on one of the serial ports). The serial cable is connected to ttyS1 on my Debian box. I tried to set things up using "minicom -s": 1. I entered the serial port the cable is connected to (on my Debian box): /dev/ttyS1 2. I set the modem init string to the empty string. Do I need any other software package besides "minicom" on my Debian box? Is there some article/howto explaining null modem cable setups in greater detail? (I was looking at the serial port console howto, but this one covers only the pin layout for null modem cables. Besides, this howto mostly deals with redirecting *boot* messages to the serial console, which is not what I'm interested in.) Any help will be greatly appreciated! Thanks in advance! Greetings, Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: null modem test
On Mon, 12 Nov 2001 14:53, J.A.Serralheiro wrote: > you can try minicom. its not exactly what you want but it can handle the > job How do you make minicom test the rts/cts lines? -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: null modem test
you can try minicom. its not exactly what you want but it can handle the job
null modem test
Is there any software in Debian to test a null modem? What I want is software to run on both ends that will exercise all control lines (DTR, DSR, RTS, and CTS) and display the values of these lines so I can see if my cable is good. If there is no software in Debian to do this then is there some software on the net under a suitable license for packaging? Failing that I'll have to write it myself. :( -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: connecting MS-Win 2000 client to Linux server via ppp null modem
* John Kerr Anderson ([EMAIL PROTECTED]) spake thusly: > Has anyone been successful on connecting a MS-Windows 2000 computer to a > Linux server via ppp null modem? I have consulted the serial lap link > howto and PPP howto. > > I keep on getting a message from my Linux computer that the connection is > not 8 bit clean. I cannot find anyway to change the word size on the > MS-Win computer. If I type "CLIENT" in the terminal window of the Windows > client the Linux server claims that a PPP connection is made, but ifconfig > says there is no connection. I never get to a point where authentication > takes place. Turn on debug and kdebug on server side. Use a terminal program on client side. Hopefully this way you'll get enough information to figure out what's wrong. "Not 8-bit clean" on client side usually means the server is sending out ASCII characters (e.g. login prompt) when client expects PPP frames. Dunno what's happening in your case. (Why not use ethernet, anyway?) Dima -- One distinguishing characteristic of BOFHen is attention deficit disorder. Put me in front of something boring and I can find a near-infinite number of really creative ways to bugger off. -- ADB
connecting MS-Win 2000 client to Linux server via ppp null modem
Has anyone been successful on connecting a MS-Windows 2000 computer to a Linux server via ppp null modem? I have consulted the serial lap link howto and PPP howto. I keep on getting a message from my Linux computer that the connection is not 8 bit clean. I cannot find anyway to change the word size on the MS-Win computer. If I type "CLIENT" in the terminal window of the Windows client the Linux server claims that a PPP connection is made, but ifconfig says there is no connection. I never get to a point where authentication takes place. Any help would be gladly appreciated! - John Kerr Anderson [EMAIL PROTECTED] Debian GNU/Linux 2.2 -
Re: PPP over null modem
On Wed, May 03, 2000 at 02:21:32PM +0700, Oki DZ wrote: > On Tue, 2 May 2000, Dan Brosemer wrote: > > I'm trying to install potato over a PPP connection between a laptop with no > > network card (hermod) and a desktop with ethernet (bolverk). > > > > I can communicate over the null modem between machines with minicom no > > problem. > > > > hermod:~# pppd -detach /dev/ttyS0 57600 192.168.5.2:192.168.5.1 crtscts > > debug noauth > > bolverk:~# pppd -detach /dev/ttyS1 57600 192.168.5.1:192.168.5.2 crtscts > > debug noauth > You can setup a user on the "server" so that when the user logs in, pppd > would be started; in /etc/passwd: > pppuser:...:/usr/local/bin/ppplogin > in which ppplogin basically a script that starts pppd: > /usr/sbin/pppd file /etc/ppp/options > On the client machine, set a ppp connection up with a self-written chat > script; the script handles the login: and password: prompts. I tried something slightly simpler. I used bash as the shell and tried to start pppd manually over the serial connection. This might mean something: in minicom: bolverk:/etc/ppp# pppd noauth (hangs) in an eterm on bolverk: bolverk:/home/odin# pppd noauth ~ÿ}#À!}!}!} }4}"}&} } } } (etc.) The latter looks right, but why on earth does it work and not the former? I copied my /etc/ppp/options file to /etc/ppp/options.ttyS1 to make sure there weren't weird differences in how it was being started even. For some reason, pppd just won't chatter over my serial ports... it's quite confusing. > If you have a network card on your laptop, it would be nice; you can setup > IP alias feature on the kernel so that you can monitor both machines with > ease (you don't have to go back and forth between them). Just use a > network number for the ethernet and another for the ppp link. I wish. I have a network card coming by mail order (about a week-1/2 to deliver). If I had it already, I wouldn't care about setting up pppd. I just want to install software and get the laptop usable sooner rather than later. It seems a waste to have such a nice machine with only the base system on it. Thanks for your help. -Dan -- "Beware he who would deny you access to information, for in his heart he dreams himself your master." pgpuVyT3eNUkL.pgp Description: PGP signature
Re: PPP over null modem
On Tue, 2 May 2000, Dan Brosemer wrote: > I'm trying to install potato over a PPP connection between a laptop with no > network card (hermod) and a desktop with ethernet (bolverk). > > I can communicate over the null modem between machines with minicom no > problem. > > hermod:~# pppd -detach /dev/ttyS0 57600 192.168.5.2:192.168.5.1 crtscts > debug noauth > bolverk:~# pppd -detach /dev/ttyS1 57600 192.168.5.1:192.168.5.2 crtscts > debug noauth You can setup a user on the "server" so that when the user logs in, pppd would be started; in /etc/passwd: pppuser:...:/usr/local/bin/ppplogin in which ppplogin basically a script that starts pppd: /usr/sbin/pppd file /etc/ppp/options On the client machine, set a ppp connection up with a self-written chat script; the script handles the login: and password: prompts. If you have a network card on your laptop, it would be nice; you can setup IP alias feature on the kernel so that you can monitor both machines with ease (you don't have to go back and forth between them). Just use a network number for the ethernet and another for the ppp link. Oki
PPP over null modem
I'm trying to install potato over a PPP connection between a laptop with no network card (hermod) and a desktop with ethernet (bolverk). I can communicate over the null modem between machines with minicom no problem. hermod:~# pppd -detach /dev/ttyS0 57600 192.168.5.2:192.168.5.1 crtscts debug noauth bolverk:~# pppd -detach /dev/ttyS1 57600 192.168.5.1:192.168.5.2 crtscts debug noauth does not set up a ppp0 interface on either machine... in fact, no information is transmitted across the serial line at all! also: bolverk:~# echo die pppd die >/etc/ttyS1 while pppd is running on hermod does not kill pppd or even cause it to log weird stuff. Is there anyone who can help me figure out what I'm doing wrong? TIA -Dan -- "Beware he who would deny you access to information, for in his heart he dreams himself your master." pgpCxCTbr0GLa.pgp Description: PGP signature
trying null modem Pt2Pt.. frustrated net-newbie
Hello, I am hoping someone can point out to this lost soul where he's screwed up. I've installed Deb. 2.2 onto a new system (Athlon) using the CD minimal install disk which gets me in with enough stuff to connect to the rest of the world... It's next to the old 486 box running 2.2.14 and a ppp line out. I've connected the two through COM 1 ports with a null modem cable (is this the mistake?), and have serial/SLIP/CSLIP in the kernels. The hosts file in the 486 (kaynjay) reads 127.0.0.1 localhost loopback 192.168.1.1 kaynjay.kenward.vaughan kaynjay 192.168.1.2H_Potter.kenward.vaughan H_Potter at the top, with some Ip6 stuff underneath. Resolv.conf reads domain kenward.vaughan at the top with DNS info underneath for the modem. The Athlon box (H_Potter ... I've got kids :) resolv.conf file has search kenward.vaughan at the top and the same DNS stuff underneath (I'm Hoping to IP masq. out of the 486 eventually). Its hosts file has 127.0.0.1 localhost loopback 192.168.1.2H_Potter.kenward.vaughan H_Potter Following the NETWORKING HowTo, I ran slattach -s 115200 /dev/ttyS0 & ifconfig sl0 192.168.1.1 pointopoint 192.168.1.2 on kaynjay, and the equivalent on H_Potter. Right now on kaynjay (with the modem up) ifconfig gives: loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:38 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ppp0 Link encap:Point-to-Point Protocol inet addr:63.196.173.47 P-t-P:63.196.172.5 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1514 Metric:1 RX packets:67 errors:0 dropped:0 overruns:0 frame:0 TX packets:59 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 sl0 Link encap:VJ Serial Line IP inet addr:192.168.1.1 P-t-P:192.168.1.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:296 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 compressed:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 compressed:0 txqueuelen:10 where I guess the TX packets:5 were the attempts to ping H_Potter. I can't ping either way, much less anything else. I'm quite uncertain about this whole procedure, as I get the feeling that I'm doing something blazingly wrong, but it is not clear to this non-geek hobbyist from the document what I Should be seeing. My goal at this point is to be able to transfer or directly use the potato debs on kaynjay. I recognize the obvious alternative (moving the HD over), but I'd never learn to network these things that way. If the cable is wrong, I can always use the printer cable and recompile for PLIP, yes?? Sorry for the long post. I'm weary now (way late here). I'd be grateful for any help, though. Kenward
Linux and Windows PPP over a Null Modem
I've got two machines and a null modem. Both are dual bootable with Windows and Linux. I can get pppd running when they are both running Linux and I can get Direct Cable Connection to work when they're both Windows. What I can't get (and the only thing I really want) is to get pppd running on the Linux machine while the other runs Windows. I do intend to put network cards in these machines some time, but that won't be too soon (I'm waiting for some hand-me-down cards after my work machines are upgraded). rgds-- TA ([EMAIL PROTECTED]) I don't speak for the Federal Reserve Board, it doesn't speak for me.
PPP over null modem: no rcvd?
Last night, I had a PPP connection over null modem working perfectly. I was using it to install packages on a laptop over the modem on my desktop, after installing the potato base using floppies and setting up IP-Masquerate on the desktop. It worked flawlessly. This morning I can't connect. As far as I can tell I'm using the same command line. This is what I'm entering on the desktop: pppd nodetach debug crtscts lock local 192.168.0.1:192.168.1.2 \ /dev/ttyS0 57600 And on the laptop the same, with the IP addresses reversed and defaultroute. I know the serial ports work because I can run a getty on either box and log into the other using minicom. When I try it, I get a series of lines like this: sent [LCP ConfReq id=0x1 ] Last night, after this there's be a ConfAck packet and some other negotiation, then a connection would be there for me to use ifconfig and route. This morning, the laptop didn't show any "rcvd" messages. although the desktop did. Obviously with only one machine "hearing" the other they couldn't negotiate a connection. After multiple tries, now *neither* machine is showing any "rcvd" messages. Again, the physical connection is fine, because I can talk over it using getty. What the heck is going on here? More info on request. -- Carl Fink [EMAIL PROTECTED] Manager, Dueling Modems Computer Forum <http://dm.net>
Re: null-modem PPP connection from Windows
In <[EMAIL PROTECTED]> Oki DZ <[EMAIL PROTECTED]> wrote: >I did that by putting "exec pppd" in a script (/usr/local/bin/ppplogin) >and "/usr/local/bin/ppplogin" in /etc/password as the replacement for >the "/bin/bash" of the username that I had set up for connecting via >PPP. I did something similar to connect my psion to my Computer. The cable has no cd. When the user logs out the ppp connection is terminated but pppd doesn't exit before I try to connect again. cu Jutta
Re: null-modem PPP connection from Windows
Peter S Galbraith wrote: ... > The question is now to get pppd started automatically instead of > a shell login. Is that done using the `-l login_program' getty > option? I did that by putting "exec pppd" in a script (/usr/local/bin/ppplogin) and "/usr/local/bin/ppplogin" in /etc/password as the replacement for the "/bin/bash" of the username that I had set up for connecting via PPP. Oki
Re: null-modem PPP connection from Windows
On Wed, Nov 10, 1999 at 04:30:22PM -0500, Peter S Galbraith wrote > > A friend want to connect his Debian laptop and a Windows box > through a null-modem cable; we thought a PPP link would be most > flexible in terms of usability (http, ftp, telnet, etc). > > He uncommented the `getty -L ttyS1 19200 vt100' line in > /etc/inittab and added the serail port to /etc/securetty. > In the Windows log files, he can see that the "Debian GNU/Linux 2.1" > login prompt appear. > You are probably best off using the "mgetty" package rather than getty. It provides an "auto_PPP" feature (configurable on a port-by-port basis, in /etc/mgetty/login.config) that will automatically start pppd (ideally, with PAP authentication) if it sees a pppd (e.g., Win95) on the other end. You will have to configure it not to expect a modem. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
Re: null-modem PPP connection from Windows
Peter S Galbraith writes: > The pppd will sit there waiting for possibly hours for someone to > connect? If you have started it with 'passive', yes. > What happens when the user disconnects? If you have started it with 'persist' it will go back to waiting. > Which manuals? The pppd man page. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: null-modem PPP connection from Windows
Felipe Alvarez Harnecker wrote: > Peter S Galbraith writes: > > A friend want to connect his Debian laptop and a Windows box > > through a null-modem cable; we thought a PPP link would be most > > flexible in terms of usability (http, ftp, telnet, etc). > > > > He uncommented the `getty -L ttyS1 19200 vt100' line in > > /etc/inittab and added the serail port to /etc/securetty. > > In the Windows log files, he can see that the "Debian GNU/Linux 2.1" > > login prompt appear. > > Don't start a getty instead start pppd from init or a shell > script in /etc/init.d/. Really? The pppd will sit there waiting for possibly hours for someone to connect? What happens when the user disconnects? > See the manuals. Which manuals? > Just curious, how do you set up the Winbug side of the ppp connection > ?? I have forwarded your answer for him to answer. Thanks! Peter
Re: null-modem PPP connection from Windows
Hello :) I had the same problem with nokia 9000 and ppp connections to a linux box. The short script below is not mine but helped me connecting n9k & linux. Anyway, try setting up a dial-up connection on windows, then minicom on linux and answer "OK" to every AT command sent to you :) Also write it somewhere and modify the chat script below :) Maybe modify the IPs as well... Try putting such a script into inittab or /etc/init.d as well. Should help. But may produce bg problems if your linux machine is a masquerading server (especially with ipmasq package). But if not, then it's not such a problem. #!/bin/sh pppd /dev/ttyS1 38400 modem lock -crtscts xonxoff debug \ connect 'chat -v -t 864000 \ ABORT"+++ATH0" \ "ATZ""OK^M^J" \ "AT&F" "OK^M^J" \ "ATD""CONNECT^M^J"\ "" "ppp^M^J" \ "" \d\c' \ 192.168.1.193:192.168.1.194 \ bsdcomp 15 \ domain lan ms-dns 192.168.1.1 \ noauth asyncmap 0 proxyarp \ -ccp nodefaultroute \ lcp-echo-interval 10 lcp-echo-failure 2 lcp-max-configure 30 \ persist -detach $* & > It alway think of a modem involved. > Regards -- Wojciech Kocjan If you think before you speak the other guy gets his joke in first.
null-modem PPP connection from Windows
Peter S Galbraith writes: > A friend want to connect his Debian laptop and a Windows box > through a null-modem cable; we thought a PPP link would be most > flexible in terms of usability (http, ftp, telnet, etc). > > He uncommented the `getty -L ttyS1 19200 vt100' line in > /etc/inittab and added the serail port to /etc/securetty. > In the Windows log files, he can see that the "Debian GNU/Linux 2.1" > login prompt appear. Don't start a getty instead start pppd from init or a shell script in /etc/init.d/. See the manuals. > > The question is now to get pppd started automatically instead of > a shell login. Is that done using the `-l login_program' getty > option? > > Any hints out there? > Thanks > -- > Peter Galbraith, research scientist <[EMAIL PROTECTED]> > 6623'rd GNU/Linux user at the Counter - http://counter.li.org/ Just curious, how do you set up the Winbug side of the ppp connection ?? It alway think of a modem involved. -- __ Felipe Alvarez Harnecker. QlSoftware. Tel. 09.874.60.17 e-mail: [EMAIL PROTECTED] Potenciado por Ql/Linux http://www.qlsoft.cl __
null-modem PPP connection from Windows
A friend want to connect his Debian laptop and a Windows box through a null-modem cable; we thought a PPP link would be most flexible in terms of usability (http, ftp, telnet, etc). He uncommented the `getty -L ttyS1 19200 vt100' line in /etc/inittab and added the serail port to /etc/securetty. In the Windows log files, he can see that the "Debian GNU/Linux 2.1" login prompt appear. The question is now to get pppd started automatically instead of a shell login. Is that done using the `-l login_program' getty option? Any hints out there? Thanks -- Peter Galbraith, research scientist <[EMAIL PROTECTED]> 6623'rd GNU/Linux user at the Counter - http://counter.li.org/
Re: PPP with IP masquerading over a null modem
Hi Nathaniel, As nobody seems to be responding to your question, I'll give it a try. I'm using IP masquerading the other way round (with a masqueraded ethernet connected to the Net via PPP) and I'm by far no expert at networking, but maybe this helps. On Sun, May 16, 1999 at 04:52:18PM -0500, tigerchild wrote: > I'm trying to connect two machines, near and far, via a null modem > plugged in to /dev/ttyS0 on each, using PPP and IP masquerading so > they can share my ethernet connection. For IP masquerading, I'd like > the near machine to be 192.168.1.1 and the far machine to be > 192.168.1.2. My lan is Class-C. > > Each machine is configured to plug into my lan, but I only have one > IP address so only one can use the lan at a time. Do you want to be able to connect both machines directly to the LAN, masquerading the other, or is it enough to have one of the two masquerading the other permanently ? I'll assume the latter, with *near machine* connected to the LAN. > /etc/ppp/options.ttyS0: > > *near machine*: > /dev/ttyS0 > persist > bsdcomp 15,15 > crtscts > 115200 > asyncmap 0 > local > lock > 192.168.1.1:192.168.1.2 > -pap > *far machine*: > /dev/ttyS0 > persist > bsdcomp 15,15 > crtscts > 115200 > asyncmap 0 > defaultroute > local > lock > 192.168.1.2:192.168.1.1 > -pap I can't say for sure if this will work, but it looks OK. Test it and see if it works. You might want to use the `silent' option on *near machine* and let *far machine* initiate the connection. > Routing tables: > > *near machine*: > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > localnet* 255.255.255.0 U 0 00 eth0 > default x.x.x.1 0.0.0.0 UG1 00 eth0 > > *far machine*: > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > localnet* 255.255.255.0 U 0 01 eth0 > 127.0.0.0 * 255.0.0.0 U 0 01 lo > default x.x.x.1 0.0.0.0 UG1 01 eth0 > > where x.x.x.1 is my lan's gateway. *near machine* looks OK. When the PPP link is up, a route to *far machine* should be added automatically. On *far machine*, I think you will only need the loopback route set (someone correct me if I'm wrong). pppd will set up a default route to *near machine*, which will then forward connections to the LAN or your gateway. > Interface configs: > > *near machine*: > eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:x.x.x.x Bcast:x.x.x.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13952 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4880 errors:0 dropped:0 overruns:0 carrier:0 > collisions:91 txqueuelen:100 > Interrupt:3 Base address:0x240 > > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:3924 Metric:1 > RX packets:8 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > > > *far machine* > loLink encap:Local Loopback > inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 > UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 > RX packets:2 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 > Collisions:0 > > eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:x.x.x.x Bcast:x.x.x.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:10 errors:0 dropped:0 overruns:0 carrier:10 > Collisions:0 > Interrupt:9 Base address:0x300 > > where x.x.x.x is my IP and x.x.x.255 is my lan's broadcast address. I suppose these are working now, so you won't need to change them. You don't need the eth0 interface on *far machine*, though. > The near machine is a potato running kernel 2.2.8 with IP > masquerading enabled and IPMasq modules loaded, the far machine is > running slink with the default kernel 2.0.36 and IPMasq modules > loaded. You won't need IP masquerading on *far machine*, so you can remove the modules there. On *near machine*, I suggest installing the ipmasq package, which worked out of the box here. > I'm not sure of what changes need to be ma
PPP with IP masquerading over a null modem
I'm trying to connect two machines, near and far, via a null modem plugged in to /dev/ttyS0 on each, using PPP and IP masquerading so they can share my ethernet connection. For IP masquerading, I'd like the near machine to be 192.168.1.1 and the far machine to be 192.168.1.2. My lan is Class-C. Each machine is configured to plug into my lan, but I only have one IP address so only one can use the lan at a time. /etc/ppp/options.ttyS0: *near machine*: /dev/ttyS0 persist bsdcomp 15,15 crtscts 115200 asyncmap 0 local lock 192.168.1.1:192.168.1.2 -pap *far machine*: /dev/ttyS0 persist bsdcomp 15,15 crtscts 115200 asyncmap 0 defaultroute local lock 192.168.1.2:192.168.1.1 -pap Routing tables: *near machine*: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface localnet* 255.255.255.0 U 0 00 eth0 default x.x.x.1 0.0.0.0 UG1 00 eth0 *far machine*: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface localnet* 255.255.255.0 U 0 01 eth0 127.0.0.0 * 255.0.0.0 U 0 01 lo default x.x.x.1 0.0.0.0 UG1 01 eth0 where x.x.x.1 is my lan's gateway. Interface configs: *near machine*: eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:x.x.x.x Bcast:x.x.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13952 errors:0 dropped:0 overruns:0 frame:0 TX packets:4880 errors:0 dropped:0 overruns:0 carrier:0 collisions:91 txqueuelen:100 Interrupt:3 Base address:0x240 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 *far machine* loLink encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:x.x.x.x Bcast:x.x.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:10 Collisions:0 Interrupt:9 Base address:0x300 where x.x.x.x is my IP and x.x.x.255 is my lan's broadcast address. The near machine is a potato running kernel 2.2.8 with IP masquerading enabled and IPMasq modules loaded, the far machine is running slink with the default kernel 2.0.36 and IPMasq modules loaded. I'm not sure of what changes need to be made to the routing tables and the interface configs, other PPP files I need to configure, and startup files that I should be modifying to make these changes sticky (/etc/init.d/network ?). I am not a complete newbie...but take it slow =). Any help is greatly appreciated. Thanks in advance! Nathaniel
Re: The Null-Modem cable info
Hans Dumbrajs wrote: > Hi! > Here is all the stufff that you need if you want to connect a win95 (I > dunno if the modem.inf works with win98, but you can try) box to your > linux box with a null modem cable and pppd. > > The modem.inf file attached is not my own work. I just added a line > there to get it running with pppd. Much credit goes to the original > author, but I don't know who he/she is. > The modem.inf file contains 3 drivers. The "Generic NULL modem" driver > is the correct one. > > The perl scribt pppcontrol, and the shell script startppp go into /sbin > on your linux box. > The perl script supplied is acctually not nessecerry. You can equally > well use cron to do what it does. > The "pppcontrol" script is started in one of your rc files with > "/sbin/pppcontrol &". What it does is simply looping forever and > checking that the pppd is running on the linux box. I couldn't get the > persist option working with pppd, if you get it working you don't need > the perl script. > As I said pppcontrol loops all the time and checks every 30 secs if pppd > is running (It assumes /usr/sbin/pppd to be the path). If pppd is not > running anymore it will call startppp to get pppd back up again. The > reason why you need a script to check if pppd is running is simply > because pppd will exit with an LCP config request timeout after a while > because your win95 box is switched of or something. > > You might want to change the network options in startppp to your liking. > > pppd opions: > local Means that you don't use a modem. > noauth is used so you don't have to enter any user name and password on > the win95 maschine. If you want authentication, change it. > nocrtcts disables hardware flow control. > xonxoff enables software flow control > > Configuring the win95 box: > Of course you need to enter all the network options correctly in win95 > dun.. like the IP address. > If you use the noauth option in pppd, it doesn't matter what you enter > as username and password. > As a phone number just enter anything.. I don't remember if you can > leave the field empty or not. Just enter 123. > What I did to get my win95 laptop to automatically log in to my linux > box at startup was this: > There is checkbox somewhere in DUN (don't remeber where) that disables > the confirmation you have to click every time you open a DUN connection. > Check that, and then simply trow a "Shortcut" into you StartMenu\Startup > folder to the DUN connection. > > I hope you can make some sense out of this.. For any clarification > please e-mail me! > Of course you can change as much as you want to my scripts and the rest. > As I said the modem.inf file is acctually not my own work. > Please let me know if you got it working! > > -- > Hans Dumbrajs / [EMAIL PROTECTED] > > >Name: pppd-dun.zip >pppd-dun.zipType: Zip Compressed Data (application/x-zip-compressed) >Encoding: base64 I forgot an important thing: Don't forget to set your serial port on the win95 box to use XON/XOFF!! Otherwise you're get crappy performance. I get about 11k/sec now which is really good for a 115200 serial port.
The Null-Modem cable info
Hi! Here is all the stufff that you need if you want to connect a win95 (I dunno if the modem.inf works with win98, but you can try) box to your linux box with a null modem cable and pppd. The modem.inf file attached is not my own work. I just added a line there to get it running with pppd. Much credit goes to the original author, but I don't know who he/she is. The modem.inf file contains 3 drivers. The "Generic NULL modem" driver is the correct one. The perl scribt pppcontrol, and the shell script startppp go into /sbin on your linux box. The perl script supplied is acctually not nessecerry. You can equally well use cron to do what it does. The "pppcontrol" script is started in one of your rc files with "/sbin/pppcontrol &". What it does is simply looping forever and checking that the pppd is running on the linux box. I couldn't get the persist option working with pppd, if you get it working you don't need the perl script. As I said pppcontrol loops all the time and checks every 30 secs if pppd is running (It assumes /usr/sbin/pppd to be the path). If pppd is not running anymore it will call startppp to get pppd back up again. The reason why you need a script to check if pppd is running is simply because pppd will exit with an LCP config request timeout after a while because your win95 box is switched of or something. You might want to change the network options in startppp to your liking. pppd opions: local Means that you don't use a modem. noauth is used so you don't have to enter any user name and password on the win95 maschine. If you want authentication, change it. nocrtcts disables hardware flow control. xonxoff enables software flow control Configuring the win95 box: Of course you need to enter all the network options correctly in win95 dun.. like the IP address. If you use the noauth option in pppd, it doesn't matter what you enter as username and password. As a phone number just enter anything.. I don't remember if you can leave the field empty or not. Just enter 123. What I did to get my win95 laptop to automatically log in to my linux box at startup was this: There is checkbox somewhere in DUN (don't remeber where) that disables the confirmation you have to click every time you open a DUN connection. Check that, and then simply trow a "Shortcut" into you StartMenu\Startup folder to the DUN connection. I hope you can make some sense out of this.. For any clarification please e-mail me! Of course you can change as much as you want to my scripts and the rest. As I said the modem.inf file is acctually not my own work. Please let me know if you got it working! -- Hans Dumbrajs / [EMAIL PROTECTED] <>
Re: Null-modem
Whoa, weird coincidence. I'm just now trying to get this to work between WinNT wkst and Linux. It doesn't look too hopeful so far. I installed a modem from 'standard' called 'dialup networking serial connection between two PCs' or something like that. However, on the Linux end I ran seyon on the port to see what WinNT does when it goes to 'dial' and it sends the string 'CLIENT' about five times and then pops up a box which complains that the 'modem' isn't working. Apparently as is the M$ custom they couldn't just stick with regular PPP. That would make their product actually interoperate with other systems and they simply *can't* have that! Dirty, rotten, Anyway, let me know if you make better progress than I. If I get there first I'll let you know but for myself since I need this connection to work I'll probably end up wiring the box to another NT machines. (Ugh.) Andrei Ivanov wrote: > Morning all. > > Is it possible to connect linux box and winbox through a nullmodem? > THanks, > Andrew > > --- > Andrei S. Ivanov > [EMAIL PROTECTED] > UIN 12402354 > http://members.tripod.com/AnSIv <--Little things for Linux. > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED]
Re: Null-modem
yep--use SLIP on your linux box and a SLIP emulator on your winbox. On Tue, 13 Apr 1999, Andrei Ivanov wrote: > Morning all. > > Is it possible to connect linux box and winbox through a nullmodem? > THanks, > Andrew > > --- > Andrei S. Ivanov > [EMAIL PROTECTED] > UIN 12402354 > http://members.tripod.com/AnSIv <--Little things for Linux. > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > mailto:[EMAIL PROTECTED]>Who is John Galt? Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld
Null-modem
Morning all. Is it possible to connect linux box and winbox through a nullmodem? THanks, Andrew --- Andrei S. Ivanov [EMAIL PROTECTED] UIN 12402354 http://members.tripod.com/AnSIv <--Little things for Linux.
Re: How to get Debian and (argh!) Windows 95 machines linked through null modem?
Pablo Longhi Lorenzzoni wrote: > > Hi Debianers!! > > I have a big problem and little time to solve. Can anyone help me? > I have to get a Debian (hamm) machine and a (argh!) Windows 95 one > linked through a null modem cable using PPP protocol. The Debian machine can > be > able to connect Internet through ppp0. > I already tryed everything I know. Does anyone have any ideas? > I solved this problem as follows: 1. I configured the corresponding serial port as a standard modem on the W machine. 2. I observed the modem control commands sent by the W machine, and answered them as expected (OK, CONNECT, ...) so the W thought it was talking to a working modem. 3. Now I run pppd from inittab (respawn) with the appropriate connect and disconnect scripts (using chat) to automate the previous step. The W machine starts up the PPP link after this fake "modem" reports a successful connection. After that, everything should work as a normal PPP link. Note: if you want to use both this and the Internet connection on the Debian machine, you should write the correct ip-up and ip-down scripts to update your routing table, and you should enable IP forwarding in the kernel in order to enable Internet connection for the W machine (I'm not sure it works, 'cause I use this whole stuff only for connecting the two machines). I've also got a question according to this. I'd like to get Samba working over this nullmodem PPP link to share the disk space and the printer on the Linux machine. I've tried a lot of fine-tunings concerning interface and routing table settings and Samba configuration, but the result is always the same: it sometimes works correctly (browsing, sharing and the like), but sometimes it doesn't work at all (the W machine doesn't even start up M$ Networking), with exactly the same setup on both machines. Now I'm not sure of even which machine is to be blamed for this. András
Re: How to get Debian and (argh!) Windows 95 machines linked through null modem?
Paul Huygen wrote: > > Pablo (Spectra) <[EMAIL PROTECTED]> wrote: > > >I have a big problem and little time to solve. Can anyone help me? > >I have to get a Debian (hamm) machine and a (argh!) Windows 95 one > >linked through a null modem cable using PPP protocol. The Debian machine can > >be > >able to connect Internet through ppp0. > > Try Samba. Debian supports Samba. Samba supports the Windows > networking style via TCP-IP. Alas, I can't help you with the lack of > time you have. Recently I have set up a network with Samba and it has > cost me much time and many questions on a local dutch Linux mailing > list to get it going. > > Paul Huygen > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null if you have installed one of the doc-linux packages, then look at the PPP-HOWTO (on my system, doing zless /usr/doc/HOWTO/PPP-HOWTO works) This has a section about using ppp over a nullmodem cable to connect to other OSs Samba is jumping the gun a bit at this stage : - you need to have ppp connectivity working first, then you might want to think about file/printer sharing. frankie -- Confession is good for the soul only in the sense that a tweed coat is good for dandruff. --Peter de Vries http://www.skunkpussy.freeserve.co.uk - Drum'n'Bass music, samples and links. ICQ://25576761begin:vcard n:;Frankie x-mozilla-html:TRUE url:http://www.skunkpussy.freeserve.co.uk adr:;;;Birmingham;;;UK version:2.1 email;internet:[EMAIL PROTECTED] title:Mr x-mozilla-cpt:;-8160 fn:Frankie end:vcard
Re: How to get Debian and (argh!) Windows 95 machines linked through null modem?
> I have a big problem and little time to solve. Can anyone help me? > I have to get a Debian (hamm) machine and a (argh!) Windows 95 one > linked through a null modem cable using PPP protocol. The Debian machine can > be > able to connect Internet through ppp0. > I already tryed everything I know. Does anyone have any ideas? You should probably use getty/mgetty on the linux side. I'm not sure if win95 has a serial line modem driver. I'm pretty sure win98 has though. Good Luck Regards Sarel Botha
Re: How to get Debian and (argh!) Windows 95 machines linked through null modem?
Pablo (Spectra) <[EMAIL PROTECTED]> wrote: >I have a big problem and little time to solve. Can anyone help me? >I have to get a Debian (hamm) machine and a (argh!) Windows 95 one >linked through a null modem cable using PPP protocol. The Debian machine can be >able to connect Internet through ppp0. Try Samba. Debian supports Samba. Samba supports the Windows networking style via TCP-IP. Alas, I can't help you with the lack of time you have. Recently I have set up a network with Samba and it has cost me much time and many questions on a local dutch Linux mailing list to get it going. Paul Huygen
How to get Debian and (argh!) Windows 95 machines linked through null modem?
Hi Debianers!! I have a big problem and little time to solve. Can anyone help me? I have to get a Debian (hamm) machine and a (argh!) Windows 95 one linked through a null modem cable using PPP protocol. The Debian machine can be able to connect Internet through ppp0. I already tryed everything I know. Does anyone have any ideas? TIA []s Pablo (Spectra)
Re: RE: Null Modem SLIP Connection
If you want to use RS-422, you can buy a RS-232 <=> RS-422 converter from companies like Jameco or Black Box. You can probably learn more about it by finding a book on serial communications. You'll be able to use RS-232 for your application without problem. RS-422 is used for very long distance serial communications and multi-drop applications. It handles noise well and does not suffer from the grounding problems that RS-232 has. OK, one more thing. RS-422 uses 4 wires; 2 for transmit and 2 for receive. George mentioned differential transmission. The first transmit wire, tx+ is referenced against the second, tx- rather than ground, this way any noise on the wires is pretty much cancelled out. The same is true for the receive side. If you have any more questions, I'd be glad to try to answer them >>> "David Karlin" <[EMAIL PROTECTED]> 11/10/98 6:15:54 AM >>> George, First of all, thanks for the extremely speedy response. Secondly, the connection is for two machines in different rooms of the same apartment. (I'm loading up my new room-mates 'puter with a second HDD for Debian.) The distance between the machines will be, at most, 60-70 feet. Thirdly, where can I find info on RS-422? Thanks again, --David > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of George Bonser > Sent: Tuesday, November 10, 1998 2:46 AM > To: David Karlin > Cc: Debian User > Subject: Re: Null Modem SLIP Connection > > > > > plip is less than serial, serial will shrink as speed increases, both > depend on the quality of cable. DO NOT attempt a link betwen machines in > different buildings or on completely different power circuits as the > difference in ground potential may fry the serial ports. For long distance > connections over cable, use a differential method such as RS-422. > > On Tue, 10 Nov 1998, David Karlin wrote: > > > Hello, > > What is the practical limit for distance between two computers > > connected via null-modem slip? > > > > How about plip? > > > > TIA > > > > --David > > > > > > -- > > Unsubscribe? mail -s unsubscribe > [EMAIL PROTECTED] < /dev/null > > > > > > > > George Bonser > > The Linux "We're never going out of business" sale at an FTP site > near you! > -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: Null Modem SLIP Connection
George, First of all, thanks for the extremely speedy response. Secondly, the connection is for two machines in different rooms of the same apartment. (I'm loading up my new room-mates 'puter with a second HDD for Debian.) The distance between the machines will be, at most, 60-70 feet. Thirdly, where can I find info on RS-422? Thanks again, --David > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of George Bonser > Sent: Tuesday, November 10, 1998 2:46 AM > To: David Karlin > Cc: Debian User > Subject: Re: Null Modem SLIP Connection > > > > > plip is less than serial, serial will shrink as speed increases, both > depend on the quality of cable. DO NOT attempt a link betwen machines in > different buildings or on completely different power circuits as the > difference in ground potential may fry the serial ports. For long distance > connections over cable, use a differential method such as RS-422. > > On Tue, 10 Nov 1998, David Karlin wrote: > > > Hello, > > What is the practical limit for distance between two computers > > connected via null-modem slip? > > > > How about plip? > > > > TIA > > > > --David > > > > > > -- > > Unsubscribe? mail -s unsubscribe > [EMAIL PROTECTED] < /dev/null > > > > > > > > George Bonser > > The Linux "We're never going out of business" sale at an FTP site > near you! >
Null Modem SLIP Connection
Hello, What is the practical limit for distance between two computers connected via null-modem slip? How about plip? TIA --David
Re: Null modem connection
> Dear Debian users, > how can I connect two Debian machines by a null modem cable so that I > can point Dselect on one of them (with only the base system installed) > to the other (with access to a Debian CD-ROM) using the FTP or the NFS > access methods? ppp / slip links are very slow. If you actually want to do some minimal networking use a null printer cable (parallel laplink cable), and use slip. There is a nice PLIP howto, too. -Michele
Re: Null modem connection
Andreas Nolda <[EMAIL PROTECTED]> wrote: |> how can I connect two Debian machines by a null modem cable so |> that I can point Dselect on one of them (with only the base |> system installed) to the other (with access to a Debian CD-ROM) |> using the FTP or the NFS access methods? |> |> Andreas Nolda Andreas: Oddly enough, I did exactly this today. I have a laptop that has no CD-ROM drive and whose only net connection is via PPP (too slow to use the FTP access method for dselect). I installed the base system for 2.0 on the laptop using floppies. Then I set up a PLIP connection between the parallel port of the laptop and the parallel port of my desktop machine---which does have a CD-ROM drive. Once the PLIP connection was up, I was able to turn the desktop machine into an NFS fileserver for the laptop. I mounted the Debian 2.0 CD at \mnt on the desktop machine, and then mounted it via the NFS link on the laptop, and installed 2.0. It all went very smoothly, as far as I can tell so far anyway. To set up the PLIP connection, I recommend that you look at the PLIP-Mini-HOWTO written by Andrea Controzzi. The latest version is available at his web-page: http://www.cli.di.unipi.it/~controzz . It's very clear and complete. Setting up the NFS connection is easy after that: On the server: [1] Start the relevant daemons: /usr/sbin/rpc.portmap (should already be running) /usr/sbin/rpc.mountd /usr/sbin/rpc.nfsd This assumes that you have NFS support built into your kernel. [2] Make sure that the file /etc/exports exists and that it contains the appropriate entry: /mntlapdog ^ ^ | | name of client machine | the directory on the server that is to be exported [3] If any changes were made to /etc/exports, make the relevant daemons re-read the file with: killall -HUP rpc.nfsd rpc.mountd --- On the client machine: [4] Create a directory (if it doesn't already exist) to be the mountpoint for the file-system on the server, say /nfs. [5] Mount the remote filesystem with: mount -t nfs SERVERNAME:/mnt /nfs [6] *Very important* Make sure to unmount before shutting down: umount /nfs If you've mounted a CD-ROM on \mnt on the server, you then have full access to the contents of the CD-ROM from the client machine, and you can use the `mounted' access method in dselect. Hope this helps, Jim
Re: Null modem connection
See section 6.27.7 of the NET-3-HOWTO for some helpful information. I did this before I installed ethernet by using slattach + ifconfig to set up the connection. With 16550A UARTs I was able to get a 115.2 kbaud serial speed. slattach is in the netbase package and I don't recall if that is in the base installation. You could probably transfer it with an ext2 floppy, however. Bob On Fri, 11 Sep 1998, Andreas Nolda wrote: > Dear Debian users, > > how can I connect two Debian machines by a null modem cable so that I > can point Dselect on one of them (with only the base system installed) > to the other (with access to a Debian CD-ROM) using the FTP or the NFS > access methods? > > Andreas Nolda > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Null modem connection
Dear Debian users, how can I connect two Debian machines by a null modem cable so that I can point Dselect on one of them (with only the base system installed) to the other (with access to a Debian CD-ROM) using the FTP or the NFS access methods? Andreas Nolda
Re: Network config -- slip + null modem
Daniel Martin writes: > Really? My pppd man page covers this [/etc/ppp/options.ttySX]... Mine doesn't. > My ppp is from bo, version 2.2.0f-23 My pppd is pppd version 2.2 patch level 0, on a 1.3.1 system recently upgraded with a Cheap Bytes CD. On the pppd man page source I find 'pppd.8,v 1.1.1.2 1996/01/28 22:11:41 alvar Exp'. I wonder if my man pages got upgraded properly? -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
[EMAIL PROTECTED] (Robert D. Hilliard) writes: > The pppd man page mentions the option as requiring > pppd to make a ppp connection using the specified device, but does not > mention that pppd will then read the file /etc/ppp. README.linux and > the comments in the file /etc/ppp/options.ttyXX included with the > distribution document this, but I think the manpage should cover it as > well. Really? My pppd man page covers this - not as clearly as it might, but it does say in the section on "options files" that pppd reads /etc/ppp/options and ~/.ppprc before reading options on the command line, and the "files" section says that /etc/ppp/options.ttyXX is read after the command line. My ppp is from bo, version 2.2.0f-23. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
Robert D. Hilliard writes: > The pppd man page mentions the option as requiring pppd to > make a ppp connection using the specified device, but does not mention > that pppd will then read the file /etc/ppp. README.linux and the > comments in the file /etc/ppp/options.ttyXX included with the > distribution document this, but I think the manpage should cover it as > well. The pppd man page has been out of date for quite a while now. Fortunately, 2.3 (which is in unstable) has an up-to-date man page. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
Lindsay writes: > One small point. You can get compression from a modem but it is very > difficult to get compression over a piece of wire. :-) 'bsdcomp 15,15' works just fine over a piece of wire. Better, in fact, than over a modem since the modem should already be doing hardware compression. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
(My original post, requesting assistance configuring slip over a null modem, and the responses recommending ppp instead are omitted to save bandwidth.) Thanks again to all. My link is now working perfectly. The pppd man page mentions the option as requiring pppd to make a ppp connection using the specified device, but does not mention that pppd will then read the file /etc/ppp. README.linux and the comments in the file /etc/ppp/options.ttyXX included with the distribution document this, but I think the manpage should cover it as well. I am still puzzled about my failure with the slip method described in the NET-3-HOWTO, and why the HOWTO doesn't mention this simple ppp method. Bob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Compression over null-modem connection (Was Re: Network config -- slip + null modem
Lindsay Allen <[EMAIL PROTECTED]> writes: > One small point. You can get compression from a modem but it is very > difficult to get compression over a piece of wire. :-) I believe compression from a modem is actually software compression implemented by the modem's ROM, while BSD compression is software compression implemented by the kernel. It seems to me that BSD compression should work over any ppp line, regardless of whether it went through a modem or not. Correct me if I'm wrong. Bob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
Bob, One small point. You can get compression from a modem but it is very difficult to get compression over a piece of wire. :-) I fell for the same thing myself. But do go for 115200. Lindsay =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia voice +61 8 9316 248632.0125S 115.8445Evk6lj Debian Unix =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Mon, 26 Jan 1998, Robert D. Hilliard wrote: > Thanks very much for your responses. All responders recommended > using ppp instead of slip. I will try a ppp setup tonight. > > I started trying to use slip because the NET-3-HOWTO recommends > it in this situation. Is that advice now obsolete? > > John says: "If this works I suggest upping the speed to 115200 > and adding compression." As I understand it, 38400 is the highest > speed that may be set directly. To get 115200 one must specify 38400, > and use the spd_vhi option to setserial. Is this correct, or can the > higher speed be set directly by pppd? > > Lindsay and Gregory: I have a couple of suggested files. If I > have trouble getting it to work, I will ask you for the files you > offered. > > Thanks again for your prompt and helpful responses. > > Bob > > > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
Thanks very much for your responses. All responders recommended using ppp instead of slip. I will try a ppp setup tonight. I started trying to use slip because the NET-3-HOWTO recommends it in this situation. Is that advice now obsolete? John says: "If this works I suggest upping the speed to 115200 and adding compression." As I understand it, 38400 is the highest speed that may be set directly. To get 115200 one must specify 38400, and use the spd_vhi option to setserial. Is this correct, or can the higher speed be set directly by pppd? Lindsay and Gregory: I have a couple of suggested files. If I have trouble getting it to work, I will ask you for the files you offered. Thanks again for your prompt and helpful responses. Bob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Network config -- slip + null modem
I needed the same thing recently and someone on this list kindly posted this solution. Put this on both machines in /etc/ppp/options.ttyS0 and then type pppd ttyS0 on both sides. I'm assuming that you are using the first serial port (ttyS0) on both computers here. 'bobspc' will then have two ppp connections running, one to you ISP and one to 'zeos'. --[ start ]- /dev/ttyS0 passive persist bsdcomp 15,15 crtscts 115200 asyncmap 0 local lock # # The first ip below is the local ip, the second the remote. # Thus they should be in opposite order on the two machines. bobspc:zeos # # Uncomment this line only on your client machine 'zeos' #defaultroute [ end ]- --Bob Robert D. Hilliard wrote: > > I am trying, so far unsuccessfully, to connect two linux boxes > with a null modem cable and slip, following the directions in the > NET-3-HOWTO. > > One machine, bobspc, is a Micron Pentium-166 that is my primary > computer, while the other, zeos, is an old 486DX-33 with a new no-name > motherboard. Bobspc has internet access through a dialup ppp > connection. Zeos has no network connection presently, and I want to > connect the two machines in order to use zeos as a backup for bobspc. > > Both machines are running bo (1.3.1r6), and a 2.0.32 kernel and > bash version 2.00.0(1)-release. > > Following are the relevant configuration files: > > /etc/hosts - bobspc > 127.0.0.1 localhost > 192.168.0.1 bobspc bobspc.estar.net > 192.168.0.2 zeoszeos.estar.net > > /etc/hosts - zeos > 127.0.0.1 localhost > 192.168.0.2 zeoszeos.estar.net > 192.168.0.1 bobspc bobspc.estar.net > > I created a file /etc/init.d/local_net with the following: > > /sbin/slattach -p cslip -s 19200 /dev/ttyS0 & > /sbin/ifconfig sl0 192.168.0.1 pointopoint 192.168.0.2 up > > This file is run from /etc/init.d/boot after > /etc/rc.boot/0setserial is run. > > During bootup the following messages are displayed: > > SIOCSIFADDR: No such device > SIOCSIFDSTADDR: No such device > > ifconfig sl0 gives no response, and ps -ax doesn't show an > slattach process. > > Running /etc/init.d/local_net a second time (after booting is > complete) gives the same messages; ifconfig sl0 still gives no response, > but ps -ax now includes the line: > > 201 1 S 0:00 /sbin/slattach -p cslip -s 19200 /dev/ttyS0 > > Trying to telnet from one machine to the other gives the > following results: > > root:vc-1:~>telnet zeos > Trying 192.168.0.2... > telnet: Unable to connect to remote host: Network is unreachable > > A ping command gives similar results. > > What am I missing? > > Bob > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Network config -- slip + null modem
I am trying, so far unsuccessfully, to connect two linux boxes with a null modem cable and slip, following the directions in the NET-3-HOWTO. One machine, bobspc, is a Micron Pentium-166 that is my primary computer, while the other, zeos, is an old 486DX-33 with a new no-name motherboard. Bobspc has internet access through a dialup ppp connection. Zeos has no network connection presently, and I want to connect the two machines in order to use zeos as a backup for bobspc. Both machines are running bo (1.3.1r6), and a 2.0.32 kernel and bash version 2.00.0(1)-release. Following are the relevant configuration files: /etc/hosts - bobspc 127.0.0.1 localhost 192.168.0.1 bobspc bobspc.estar.net 192.168.0.2 zeoszeos.estar.net /etc/hosts - zeos 127.0.0.1 localhost 192.168.0.2 zeoszeos.estar.net 192.168.0.1 bobspc bobspc.estar.net I created a file /etc/init.d/local_net with the following: /sbin/slattach -p cslip -s 19200 /dev/ttyS0 & /sbin/ifconfig sl0 192.168.0.1 pointopoint 192.168.0.2 up This file is run from /etc/init.d/boot after /etc/rc.boot/0setserial is run. During bootup the following messages are displayed: SIOCSIFADDR: No such device SIOCSIFDSTADDR: No such device ifconfig sl0 gives no response, and ps -ax doesn't show an slattach process. Running /etc/init.d/local_net a second time (after booting is complete) gives the same messages; ifconfig sl0 still gives no response, but ps -ax now includes the line: 201 1 S 0:00 /sbin/slattach -p cslip -s 19200 /dev/ttyS0 Trying to telnet from one machine to the other gives the following results: root:vc-1:~>telnet zeos Trying 192.168.0.2... telnet: Unable to connect to remote host: Network is unreachable A ping command gives similar results. What am I missing? Bob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: nfs-booting with a null-modem cable ?
-BEGIN PGP SIGNED MESSAGE- On Tue, 27 May 1997, Bruce Perens wrote: >Oops. Right - he wants to use PPP. Sorry, my answer _was_ specific to >Ethernet. > >You'd need to use INITRD. That's a good deal harder, but do-able. You would >have to load a small root filesystem, start up PPPD, mount the new root >filesystem, and then exit the initrd. See >/usr/src/linux/Docuemntation/initrd.txt . Sven Rudolph did an awful good job on the Boot/Root/Rescue Disks. Starting from the Debian Rescue disk the mentioned task should not take much work. It is possible to make the ramdisk bigger so that a full libc can be used, and a lot of stuff that is needed for installation only could be thrown away to make room for pppd etc. Also a custom kernel with the serial driver compiled in might save some bytes (with the side effect that booting probably also will be faster because less devices are probed) Nils - -- \ /| Nils Rennebarth --* WINDOWS 42 *-- | Schillerstr. 61 / \| 37083 Göttingen | ++49-551-71626 Micro$oft's final answer | http://www.nus.de/~nils -BEGIN PGP SIGNATURE- Version: 2.6.3i Charset: noconv iQB1AwUBM4wJJlptA0IhBm0NAQH9TAL/UOqEnGhcxphEjDfrgD8w4mj5DCjJj2eq m5gz8gywEuJsGUk9hr5CtsyFk3ESML8K3kopjNhYE7drjrOf8zpKLuWsCVYNRMNe nSj5IeJWhOb0eY90wblsEVmpplSFLNQo =gcv0 -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: nfs-booting with a null-modem cable ?
Bruce: > Not nearly so difficult, he can use a floppy drive. You can load > the kernel from floppy and have it mount an NFS root. SysLinux > would be best for this. From: Rob Browning <[EMAIL PROTECTED]> > I presume that this will only work if you're using NFS over something > like ethernet (not that nfs would be really tolerable over a 115K PPP > serial port connection anyway). Oops. Right - he wants to use PPP. Sorry, my answer _was_ specific to Ethernet. You'd need to use INITRD. That's a good deal harder, but do-able. You would have to load a small root filesystem, start up PPPD, mount the new root filesystem, and then exit the initrd. See /usr/src/linux/Docuemntation/initrd.txt . Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: nfs-booting with a null-modem cable ?
[EMAIL PROTECTED] (Bruce Perens) writes: > Not nearly so difficult, he can use a floppy drive. You can load > the kernel from floppy and have it mount an NFS root. SysLinux > would be best for this. I presume that this will only work if you're using NFS over something like ethernet (not that nfs would be really tolerable over a 115K PPP serial port connection anyway). Thanks -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: nfs-booting with a null-modem cable ?
From: Rob Browning <[EMAIL PROTECTED]> > If you're talking about the 486 booting from an nfs mounted root on > your PPro machine, I think you may need an ethernet card with special > boot ROMs. Not nearly so difficult, he can use a floppy drive. You can load the kernel from floppy and have it mount an NFS root. SysLinux would be best for this. On a Debian system: Put a formatted floppy in the first floppy drive. Unzip /usr/lib/syslinux/img1440.gz to the raw floppy, /dev/fd0. Mount the floppy as an MSDOS filesystem, and copy the kernel on to it. Edit SYSLINUX.CFG to add the NFS root parameters to the boot command line. See the file /usr/src/linux/Documentation/nfsroot.txt, you will have to install the kernel-source package if you have not done so. That should work fine. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: nfs-booting with a null-modem cable ?
Alexandre Lebrun <[EMAIL PROTECTED]> writes: > I'd like to set up my PPro to enable my 486 to boot nfs. > looking at mknfsroot, this should be possible and perhaps easy with eth > cards. If you're talking about the 486 booting from an nfs mounted root on your PPro machine, I think you may need an ethernet card with special boot ROMs. Though I'm no expert in this area, so I could be wrong. If you're just talking about having a small hard drive in the 486 and nfs mounting stuff after it comes up, then that's easy, you can do that with the modem cable, or with ethernet. With the modem cable approach, you'll need ppp, and will be limited to about 10k/s. You should browse the HOWTO index. There's a HOWTO on PPP, and one (I think) on net booting. You can reach the HOWTO index from any Debian web site mirror (www.debian.org). -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
