Author Topic: USB Modem  (Read 3776 times)

Dave Yeo

  • Hero Member
  • *****
  • Posts: 3627
  • Karma: +77/-0
    • View Profile
Re: USB Modem
« Reply #15 on: February 04, 2022, 06:19:58 pm »
It's weird, years of dial up and I never noticed it before. It shows mine as dead, as expected.
Code: [Select]
ATZ
No response from modem...
AT&F
AT&D2&C1X4V1Q0S7=70

On Linux, had to write a chat script, papchat or such and it was easy to get wrong but the whole connection could be logged to see where the failure was. Be good if able to log the connection on OS/2 to verify the password is rejected.

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 834
  • Karma: +21/-0
    • View Profile
    • Blonde Guy
Re: USB Modem
« Reply #16 on: February 05, 2022, 12:33:57 am »
modemtst has a text window. Logging isn't possible, but you can cut/paste from the window to the system editor.

So I was able to see precisely that login was the failure. I'm hoping to make progress in finding the actual login userid/password.
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 834
  • Karma: +21/-0
    • View Profile
    • Blonde Guy
Re: USB Modem
« Reply #17 on: February 18, 2022, 04:54:54 pm »
Reactivating this thread, I got a valid password. It works on website and if I use modemtst.exe, it works there, too.

But configuring the IBM Dialer seems to be the problem. I try to connect there, and I get errors. I'm way out of practice for dial-up modems, but clearly, I have set something up wrong. What can cause this error?

Code: [Select]
notice : OS/2 ppp 2.00 Revision: 1.18a started by OS/2, pid 106
info   : Using interface ppp0
info   : Setting line characteristics
info   : Setting com port baud rate to 57600
notice : Linking: ppp0 <--> com1
info   : Time critical priority level 1
info   : Connecting with <slattach AT OK ATZ OK ATDT18183040263 NNECT>
info   :
Connector completed ...
info   : Remote message:
info   : [io_event] Unsupported protocol (80fd) received.
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
error  : [NETW] Invalid fcs
info   : fsm_rtermreq LCP terminated at peer's request
notice : lcp_down: Connection terminated.
info   : Exit called
info   : Terminating link.
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1548
  • Karma: +4/-2
    • View Profile
Re: USB Modem
« Reply #18 on: February 18, 2022, 05:31:17 pm »
I have no idea what that might be, and I no longer have a telephone line to try things.

A couple of suggestions:

ZOC is at HOBBES. It may do something different, or tell you more.

If you still have a machine with a serial port, and a real modem, try the same thing with it. Any differences may be instructive, especially if you try the USB modem on the same machine.

While you are doing your testing, it is an opportunity to see if PMMail will still dial. That feature hasn't been tested for a long time.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 3627
  • Karma: +77/-0
    • View Profile
Re: USB Modem
« Reply #19 on: February 18, 2022, 07:51:09 pm »
Code: [Select]
info   : [io_event] Unsupported protocol (80fd) received.
error  : [NETW] Invalid fcs

I used to see similar with Injoy but it would connect. I'd still suggest downloading Injoy from Hobbes and testing with that. It worked much better then DOIP, which really was designed for SLIP and the PPP support (which wasn't even present in my first Warp 3 install) may well be only compatible with the old 16 TCPIP stack.
I also used the dialer that came with eCommstation from ecosoft IIRC, it was more of a hassle to get working but did work.
I also had to kill socktidy, can't remember if it was only with Injoy.

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 834
  • Karma: +21/-0
    • View Profile
    • Blonde Guy
Re: USB Modem
« Reply #20 on: February 24, 2022, 03:32:44 pm »
Injoy does seem to work. I took the modem strings over to the IBM Dialer, and it still does not work.

I am puzzled about why Injoy can work, but the IBM dialer does not.
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Andi B.

  • Hero Member
  • *****
  • Posts: 641
  • Karma: +8/-1
    • View Profile
Re: USB Modem
« Reply #21 on: February 24, 2022, 06:18:22 pm »
Here in Austria I never got the IBM dialer to work. Injoy did the job for years. But I never tracked down what's the reason.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 3627
  • Karma: +77/-0
    • View Profile
Re: USB Modem
« Reply #22 on: February 24, 2022, 06:22:31 pm »
IIRC, Injoy has its own PPP implementation. How do the connect string compare? Perhaps just a timing thing.

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 834
  • Karma: +21/-0
    • View Profile
    • Blonde Guy
Re: USB Modem
« Reply #23 on: February 25, 2022, 04:38:10 am »
It's been a long time since I used Injoy, but while it says there is a successful connection, I don't recall how to make that useful.

I've got a standard setup.cmd that makes LAN 0 DHCP. If I then connect Injoy, I should see something in PPP0. But I don't get connectivity. I can't ping, nslookup, tracerte. I'm wondering how it gets set up.

I want to be able to unplug the Ethernet cable, and have packets go to dial-up instead. There is a resolve.inj in the etc directory, but resolv2 still points to the DHCP LAN0 version.
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Dave Yeo

  • Hero Member
  • *****
  • Posts: 3627
  • Karma: +77/-0
    • View Profile
Re: USB Modem
« Reply #24 on: February 25, 2022, 07:27:22 am »
It's been a long time for me as well and just now I started up Injoy and it took out lan0, ended up rebooting :)
For a start, Injoy uses PPP1 IIRC as PPP0 is DOIP. Maybe try by moving setup.cmd out of the way, reboot to clear everything and retest.
The connection info should show in Injoy's terminal window though I have Injoy 2.1 or such and current is 3.x so don't know if things changed.

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 834
  • Karma: +21/-0
    • View Profile
    • Blonde Guy
Re: USB Modem
« Reply #25 on: February 25, 2022, 05:33:47 pm »
I finally thought of looking in the In-joy logs. This is with setup.cmd removed, but I tried with it in place, and it makes no difference. Apparently socket error WSAENOTSOCK (10038) after including thread is happening a lot.

Code: [Select]
*** TRACE FILE FOR IN-JOY DIALER - version 2.30

Fri Feb 25 08:13:44 2022


2502122 08134484 TCP/IP stack version 6.3100 detected
2502122 08150878 Activating packet mode
2502122 08150881 TX: CONFIG-REQ :periodic :id :50
2502122 08150908 RX: LCP PACKET - id = 50
2502122 08150909 RX: CONFIG_ACK
2502122 08151006 RX: LCP PACKET - id = 1
2502122 08151006 RX: CONFIG_REQ
2502122 08151007 Unknown LCP option :type :0 :len :4
2502122 08151007 OPTION -> LCPOPTION_MRU -> MRU [1524]
2502122 08151007 OPTION -> LCPOPTION_ACCM -> ACCM [2560]
2502122 08151007 Will attempt to force remote ACCM to zero
2502122 08151007 OPTION -> LCPOPTION_AUTPROT, METHOD [PAP]
2502122 08151007 OPTION -> LCPOPTION_PROTCOMP
2502122 08151007 OPTION -> LCPOPTION_ADDRESSCOMP
2502122 08151008 Unknown LCP option :type :17 :len :4
2502122 08151008 Unknown LCP option :type :19 :len :9
2502122 08151008 TX: LCP PACKET, id = 1, code = 4
2502122 08151206 RX: LCP PACKET - id = 1
2502122 08151206 RX: CONFIG_REQ
2502122 08151206 Unknown LCP option :type :0 :len :4
2502122 08151207 OPTION -> LCPOPTION_MRU -> MRU [1524]
2502122 08151207 OPTION -> LCPOPTION_ACCM -> ACCM [2560]
2502122 08151207 Will attempt to force remote ACCM to zero
2502122 08151207 OPTION -> LCPOPTION_AUTPROT, METHOD [PAP]
2502122 08151207 OPTION -> LCPOPTION_PROTCOMP
2502122 08151207 OPTION -> LCPOPTION_ADDRESSCOMP
2502122 08151207 Unknown LCP option :type :17 :len :4
2502122 08151208 Unknown LCP option :type :19 :len :9
2502122 08151208 TX: LCP PACKET, id = 1, code = 4
2502122 08151232 RX: LCP PACKET - id = 2
2502122 08151233 RX: CONFIG_REQ
2502122 08151233 OPTION -> LCPOPTION_MRU -> MRU [1524]
2502122 08151233 OPTION -> LCPOPTION_ACCM -> ACCM [2560]
2502122 08151233 Couldn't force remote ACCM to zero - accepting value
2502122 08151233 OPTION -> LCPOPTION_AUTPROT, METHOD [PAP]
2502122 08151233 OPTION -> LCPOPTION_PROTCOMP
2502122 08151233 OPTION -> LCPOPTION_ADDRESSCOMP
2502122 08151233 TX: LCP PACKET, id = 2, code = 2
2502122 08151234 Setting ESCAPE ACCM table to accm [2560]
2502122 08151234 *** LCP LAYER OPENED SUCCESSFULLY ***
2502122 08151234 *** PAP ENABLED.. KICKING OFF ***
2502122 08151234 TX: PAP AUTHENTICATION-REQ
2502122 08151277 RX: PAP INCLUDING PAP-EADER
2502122 08151277 PAP: Authentication Succeeded
2502122 08151277 RX: PAP CONFIG_ACK
2502122 08151278 IPCP: Initiating - Sending CONFIG_REQ
2502122 08151278 TX: IPCP_CONFIG-REQ, INCL HEADER
2502122 08151278 RX: IPCP PACKET INCLUDING IPCP-HEADER
2502122 08151278 RX: CONFIG_REQ
2502122 08151278 IPCP: OPTION -> IPCP_COMPRESS
2502122 08151278 IPCP: Rejecting VJ compression
2502122 08151278 IPCP: OPTION -> IPCP_ADDRESS, ADDRESS OF PEER [66.90.128.161]
2502122 08151279 TX: IPCP PACKET, INCL. HEADER
2502122 08151279 PPP: Unknown protocol: 0x80FD, PROTOCOL REJECT generated
2502122 08151279 TX: PROTOCOL REJECT
2502122 08151304 RX: IPCP PACKET INCLUDING IPCP-HEADER
2502122 08151304 RX: CONFIG_NAK
2502122 08151304 IPCP: OPTION NAK/REJ-> IP ADDRESS
2502122 08151304 IPCP: OPTION NAK/REJ-> PRIMARY DNS ADDRESS: 8.8.8.8
2502122 08151304 IPCP: OPTION NAK/REJ-> SECONDARY DNS ADDRESS: 8.8.4.4
2502122 08151305 RX: IPCP PACKET INCLUDING IPCP-HEADER
2502122 08151305 RX: CONFIG_REQ
2502122 08151305 IPCP: OPTION -> IPCP_ADDRESS, ADDRESS OF PEER [66.90.128.161]
2502122 08151305 TX: IPCP PACKET, INCL. HEADER
2502122 08151479 TX: IPCP_CONFIG-REQ, INCL HEADER
2502122 08151503 RX: IPCP PACKET INCLUDING IPCP-HEADER
2502122 08151503 RX: CONFIG_ACK
2502122 08151504 *** IPCP LAYER OPENED SUCCESSFULLY ***
2502122 08151504 [ppp0] [66.90.128.161] [72.251.9.176] [255.255.255.0]
2502122 08151504 Err 10038 defining interface parameters - try #1
2502122 08151504 Err 10038 removing interface route
2502122 08151531 Err 10038 defining interface parameters - try #2
2502122 08151531 Err 10038 removing interface route
2502122 08151559 Err 10038 defining interface parameters - try #3
2502122 08151559 Err 10038 removing interface route
2502122 08151584 Err 10038 defining interface parameters - try #4
2502122 08151584 Err 10038 removing interface route
2502122 08151609 [ppp0] Default Route [66.90.128.161]
2502122 08151609 Err 10038, adding default route
2502122 08184656 TX: TERMINATE REQ
2502122 08184916 Connection log entry generated
2502122 08184916 Deleting Default Route
2502122 08184930 Deleting [ppp0] [66.90.128.161] [72.251.9.176] [255.255.255.0]
2502122 08184930 Err 10038 removing interface route
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Dave Yeo

  • Hero Member
  • *****
  • Posts: 3627
  • Karma: +77/-0
    • View Profile
Re: USB Modem
« Reply #26 on: February 25, 2022, 07:34:23 pm »
So everything is good until setting up the interface. My guess is something already grabbed the interface. Use something like top or ps to see what in x:\mptn\bin is running. Here there's socktidy, dhcpd and cntrl. Socktidy and dhcpd could be killed to see if it helps, might take a while for the routing to be released.
Looking at my email archives, it was 5 years back with Bluelion 4.95 where I was having problems with dial up, thread on testers was dial up and BL 4.95 02/22/17 where most of my problems were caused by socktidy, but they seemed to be due to dial on demand.

ivan

  • Hero Member
  • *****
  • Posts: 1356
  • Karma: +14/-0
    • View Profile
Re: USB Modem
« Reply #27 on: February 25, 2022, 09:23:15 pm »
Might I suggest trying ZOC, I say that because I never could get In-goy to work with my USB modem - it didn't like some of the settings.  With ZOC I just toild it what to dial and where to find the modem and everything worked.

Sorry I can't run a test for you now as the only telephone line I have is VOIP now.

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 834
  • Karma: +21/-0
    • View Profile
    • Blonde Guy
Re: USB Modem
« Reply #28 on: February 27, 2022, 01:50:24 am »
I may have to try ZOC, but for the time being, I looked back at my e-mail from Feb, 2017 and I see the socktidy.exe issue.

Socktidy is launched from B4TCP.CMD, so I commented it out. I disabled Ethernet by renaming SETUP.CMD.

Injoy now connects. I can ping my server, I can ftp to my server, I can load a simple web page with Firefox. The connection is slow, and the Injoy window is full of errors. Eventually Injoy crashes. Oddly for such an old program, a .TRP file is left behind. (see attachment)

I'm hoping the crash is just because of my bad landline.

Trace:
Code: [Select]
*** TRACE FILE FOR IN-JOY DIALER - version 2.30

Sat Feb 26 16:35:59 2022


2602122 16355921 TCP/IP stack version 6.3100 detected
2602122 16370704 Activating packet mode
2602122 16370706 TX: CONFIG-REQ :periodic :id :50
2602122 16370800 RX: LCP PACKET - id = 1
2602122 16370800 RX: CONFIG_REQ
2602122 16370800 Unknown LCP option :type :0 :len :4
2602122 16370800 OPTION -> LCPOPTION_MRU -> MRU [1524]
2602122 16370801 OPTION -> LCPOPTION_ACCM -> ACCM [2560]
2602122 16370801 Will attempt to force remote ACCM to zero
2602122 16370801 OPTION -> LCPOPTION_AUTPROT, METHOD [PAP]
2602122 16370801 OPTION -> LCPOPTION_PROTCOMP
2602122 16370801 OPTION -> LCPOPTION_ADDRESSCOMP
2602122 16370801 Unknown LCP option :type :17 :len :4
2602122 16370802 Unknown LCP option :type :19 :len :9
2602122 16370802 TX: LCP PACKET, id = 1, code = 4
2602122 16370802 RX: LCP PACKET - id = 50
2602122 16370802 RX: CONFIG_ACK
2602122 16370895 RX: LCP PACKET - id = 1
2602122 16370895 RX: CONFIG_REQ
2602122 16370895 Unknown LCP option :type :0 :len :4
2602122 16370895 OPTION -> LCPOPTION_MRU -> MRU [1524]
2602122 16370895 OPTION -> LCPOPTION_ACCM -> ACCM [2560]
2602122 16370895 Will attempt to force remote ACCM to zero
2602122 16370895 OPTION -> LCPOPTION_AUTPROT, METHOD [PAP]
2602122 16370896 OPTION -> LCPOPTION_PROTCOMP
2602122 16370896 OPTION -> LCPOPTION_ADDRESSCOMP
2602122 16370896 Unknown LCP option :type :17 :len :4
2602122 16370896 Unknown LCP option :type :19 :len :9
2602122 16370896 TX: LCP PACKET, id = 1, code = 4
2602122 16370965 RX: LCP PACKET - id = 2
2602122 16370965 RX: CONFIG_REQ
2602122 16370965 OPTION -> LCPOPTION_MRU -> MRU [1524]
2602122 16370965 OPTION -> LCPOPTION_ACCM -> ACCM [2560]
2602122 16370965 Couldn't force remote ACCM to zero - accepting value
2602122 16370966 OPTION -> LCPOPTION_AUTPROT, METHOD [PAP]
2602122 16370966 OPTION -> LCPOPTION_PROTCOMP
2602122 16370966 OPTION -> LCPOPTION_ADDRESSCOMP
2602122 16370966 TX: LCP PACKET, id = 2, code = 2
2602122 16370966 Setting ESCAPE ACCM table to accm [2560]
2602122 16370967 *** LCP LAYER OPENED SUCCESSFULLY ***
2602122 16370967 *** PAP ENABLED.. KICKING OFF ***
2602122 16370967 TX: PAP AUTHENTICATION-REQ
2602122 16371043 RX: PAP INCLUDING PAP-EADER
2602122 16371043 PAP: Authentication Succeeded
2602122 16371044 RX: PAP CONFIG_ACK
2602122 16371044 IPCP: Initiating - Sending CONFIG_REQ
2602122 16371044 TX: IPCP_CONFIG-REQ, INCL HEADER
2602122 16371044 RX: IPCP PACKET INCLUDING IPCP-HEADER
2602122 16371044 RX: CONFIG_REQ
2602122 16371044 IPCP: OPTION -> IPCP_COMPRESS
2602122 16371044 IPCP: Rejecting VJ compression
2602122 16371045 IPCP: OPTION -> IPCP_ADDRESS, ADDRESS OF PEER [66.90.128.161]
2602122 16371045 TX: IPCP PACKET, INCL. HEADER
2602122 16371045 PPP: Unknown protocol: 0x80FD, PROTOCOL REJECT generated
2602122 16371045 TX: PROTOCOL REJECT
2602122 16371112 RX: IPCP PACKET INCLUDING IPCP-HEADER
2602122 16371112 RX: CONFIG_NAK
2602122 16371112 IPCP: OPTION NAK/REJ-> IP ADDRESS
2602122 16371113 IPCP: OPTION NAK/REJ-> PRIMARY DNS ADDRESS: 8.8.8.8
2602122 16371113 IPCP: OPTION NAK/REJ-> SECONDARY DNS ADDRESS: 8.8.4.4
2602122 16371113 RX: IPCP PACKET INCLUDING IPCP-HEADER
2602122 16371113 RX: CONFIG_REQ
2602122 16371113 IPCP: OPTION -> IPCP_ADDRESS, ADDRESS OF PEER [66.90.128.161]
2602122 16371113 TX: IPCP PACKET, INCL. HEADER
2602122 16371246 TX: IPCP_CONFIG-REQ, INCL HEADER
2602122 16371313 RX: IPCP PACKET INCLUDING IPCP-HEADER
2602122 16371313 RX: CONFIG_ACK
2602122 16371313 *** IPCP LAYER OPENED SUCCESSFULLY ***
2602122 16371313 [ppp0] [66.90.128.161] [72.251.14.51] [255.255.255.0]
2602122 16371313 [ppp0] Default Route [66.90.128.161]
2602122 16374339 PPP: Invalid protocol 0x3A20
2602122 16374340 Invalid fcs
2602122 16374689 PPP: Invalid protocol 0x0
2602122 16374689 Invalid fcs
2602122 16374690 PPP: Invalid protocol 0x2802
2602122 16374735 Invalid fcs
2602122 16375137 Invalid fcs
2602122 16381986 Invalid fcs
2602122 16381986 Invalid fcs
2602122 16381992 Invalid fcs
2602122 16382026 Invalid fcs
2602122 16383840 Invalid fcs
2602122 16384890 PPP: Invalid protocol 0x4
2602122 16384892 Invalid fcs
2602122 16384893 PPP: Invalid protocol 0x6230
2602122 16384893 Invalid fcs
2602122 16384895 PPP: Invalid protocol 0x3006
2602122 16384896 Invalid fcs
2602122 16384896 Invalid fcs
2602122 16385256 Invalid fcs
2602122 16385258 Invalid fcs
2602122 16385259 Invalid fcs
2602122 16385405 Invalid fcs
2602122 16385486 Invalid fcs
2602122 16385573 Invalid fcs
2602122 16385573 Invalid fcs
2602122 16385719 Invalid fcs
2602122 16385732 Invalid fcs
2602122 16390010 Invalid fcs
2602122 16390035 Invalid fcs
2602122 16390108 Invalid fcs
2602122 16390184 Invalid fcs
2602122 16390188 Invalid fcs
2602122 16390346 Invalid fcs
2602122 16390524 Invalid fcs
2602122 16390525 Invalid fcs
2602122 16390526 Invalid fcs
2602122 16390664 Invalid fcs
2602122 16390757 Invalid fcs
2602122 16390758 Invalid fcs
2602122 16390758 Invalid fcs
2602122 16390888 Invalid fcs
2602122 16391027 Invalid fcs
2602122 16391363 Invalid fcs
2602122 16391432 Invalid fcs
2602122 16391436 Invalid fcs
2602122 16391438 Invalid fcs
2602122 16391438 Invalid fcs
2602122 16391445 Invalid fcs
2602122 16391583 Invalid fcs
2602122 16391602 Invalid fcs
2602122 16391695 Invalid fcs
2602122 16391815 Invalid fcs
2602122 16391880 Invalid fcs
2602122 16392228 Invalid fcs
2602122 16392243 Invalid fcs
2602122 16392388 Invalid fcs
2602122 16392545 Invalid fcs
2602122 16392638 Invalid fcs
2602122 16392668 Invalid fcs
2602122 16392821 Invalid fcs
2602122 16392821 Invalid fcs
2602122 16392908 Invalid fcs
2602122 16392918 Invalid fcs
2602122 16392918 Invalid fcs
2602122 16392925 Invalid fcs
2602122 16393042 Invalid fcs
2602122 16393063 Invalid fcs
2602122 16393119 Invalid fcs
2602122 16393122 Invalid fcs
2602122 16393130 Invalid fcs
2602122 16393262 Invalid fcs
2602122 16393263 Invalid fcs
2602122 16393438 Invalid fcs
2602122 16393440 Invalid fcs
2602122 16393441 Invalid fcs
2602122 16393453 Invalid fcs
2602122 16393456 Invalid fcs
2602122 16393511 PPP: Invalid protocol 0x50
2602122 16393512 Invalid fcs
2602122 16393512 PPP: Invalid protocol 0x204
2602122 16393513 Invalid fcs
2602122 16393514 Invalid fcs
2602122 16394209 Invalid fcs
2602122 16394211 Invalid fcs
2602122 16394211 Invalid fcs
2602122 16394393 Invalid fcs
2602122 16394405 Invalid fcs
2602122 16394405 PPP: Invalid protocol 0x0
2602122 16394406 Invalid fcs
2602122 16394587 Invalid fcs
2602122 16394729 Invalid fcs
2602122 16394730 PPP: Invalid protocol 0x8EFA
2602122 16394794 Invalid fcs
2602122 16394892 Invalid fcs
2602122 16394893 PPP: Invalid protocol 0x1600
2602122 16394893 Invalid fcs
2602122 16394897 Invalid fcs
2602122 16394923 Invalid fcs
2602122 16394923 PPP: Invalid protocol 0x1600
2602122 16394923 Invalid fcs
2602122 16394942 Invalid fcs
2602122 16395068 Invalid fcs
2602122 16395623 PPP: Invalid protocol 0x5002
2602122 16395623 Invalid fcs
2602122 16395624 PPP: Invalid protocol 0x6EE2
2602122 16395624 Invalid fcs
2602122 16395761 Invalid fcs
2602122 16395958 Invalid fcs
2602122 16400012 Invalid fcs
2602122 16400041 Invalid fcs
2602122 16400080 Invalid fcs
2602122 16400143 Invalid fcs
2602122 16400178 Invalid fcs
2602122 16400440 Invalid fcs
2602122 16400443 Invalid fcs
2602122 16401046 Connection log entry generated
2602122 16401047 Deleting Default Route
2602122 16401047 Deleting [ppp0] [66.90.128.161] [72.251.14.51] [255.255.255.0]
« Last Edit: February 27, 2022, 02:05:31 am by Neil Waldhauer »
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Dave Yeo

  • Hero Member
  • *****
  • Posts: 3627
  • Karma: +77/-0
    • View Profile
Re: USB Modem
« Reply #29 on: February 27, 2022, 05:31:13 am »
There's options for PPP under Change-->OK-->PPP that might help. I doubt that your phone line is worse then mine was, cheap modems would train down to 0 bytes a second pretty quick and usual connection was 26.4.
Bitwise owns Injoy now and have an issue tracker at Github