| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Telnet for FrontDoor? |
ML> that's wierd... i seem to recall something somewhere to do with ML> the formatt of the DFRS stuff but i don't recall if it is/was ML> anything in FD or if it was settings in the modems i was using at ML> the time... i don't know that it is anything critical, though... is ML> it? TJM> 22:21:29 Processing NetMail folder TJM> 22:21:29 No messages to send in this event TJM> = 22:21:31 RING TJM> = 22:21:34 CONNECT 115200/141158126138 TJM> + 22:21:34 Incoming call at 115200 BPS TJM> 22:21:34 Sending text in \FD\BANNER2.TXT TJM> Here's my log file. Wish I knew how to work around this. I can TJM> guess what the IP is, or check the netserial log, but it would be TJM> nice to have it imported into the BBS correctly tho. :( that's in IP number??? it looks like a connect message to me... here's what i get... = 14:25:16 RING = 14:25:20 RING = 14:25:20 CONNECT 57600/ARQ/TEL FROM 192.168.42.7 + 14:25:22 Incoming call at 57600 BPS 14:25:24 Sending text in X:\FD\BAN11.FD definitely a different format... you'll probably have an easier time getting the folk who wrote your virtual modem driver to conform to a/the more standard format... the above is more like the following industry standardized format single line connect messages... = 12:00:35 RING = 12:00:41 RING = 12:00:58 CONNECT 24000/ARQ/V34/LAPM/V42BIS i can see why joho wouldn't want to have to recode that section... what you show is really "out there" ;) not trying to be negative or dissuade you... it doesn't really look like bug that i can see... )\/(ark* Origin: (1:3634/12) SEEN-BY: 633/267 @PATH: 3634/12 123/500 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.