I have a PM-3 running ComOS 3.7. Today I got a call from a customer
complaining that it took him 15 seconds to connect with his Teles card.
After checking his config I got it down to 4 seconds. Good, but not good
enough. So I did a PPP debug when he connected. The result (after being
processed through Livingstons debug ring) is appended at the end of this
mail.
As you can see, the PM-3 does not reject both the primary and secondary
NBNS options at once, nor does it NAK the 2 DNS options simultaneously.
Instead, after rejecting the pri NBNS it NAKs the sec along with the sec
DNS, and then rejects the sec NBNS. By this time my PM-3 has obviously
gotten the peer so confused that it forgets about the sec DNS and only
asks for the pri DNS.
Am I completely wrong thinking this is a good example how not to
negotiate IPCP options? Have I missed anything that might stop this odd
behaviour?
Best regards,
Fredrik Juhlin NetGuide Scandinavia Phone: +46 (0)31 50 79 40
juhlin@netg.se http://www.netg.se/ Fax: +46 (0)31 50 79 39
'Principles are supposed to be strange,
otherwise they're just common sense' -- Dark
--- DRING analysis of PM-3 PPP debug output
[snipped LCP and PAP]
Received IPCP_CONFIGURE_REQUEST on port S3 of 36 bytes containing:
01 01 00 28 02 06 00 2D 0F 01 03 06 00 00 00 00 81 06 00 00 00 00 82 06
00 00 00 00 83 06 00 00 00 00 84 06 00 00 00 00
Packet Info: Code: 01, ID: 01, 40 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F01]
IP-Address [0x03], length: (6 bytes), [0.0.0.0]
Primary DNS Server Address [0x81], length: (6 bytes), [0.0.0.0]
Primary NBNS Server Address [0x82], length: (6 bytes), [0.0.0.0]
Secondary DNS Server Address [0x83], length: (6 bytes), [0.0.0.0]
Secondary NBNS Server Address [0x84], length: (6 bytes),
[0.0.0.0]
Sending IPCP_CONFIGURE_REJECT to port S3 of 10 bytes containing:
04 01 00 0A 84 06 00 00 00 00
Packet Info: Code: 04, ID: 01, 10 bytes.
Secondary NBNS Server Address [0x84], length: (6 bytes),
[0.0.0.0]
Received IPCP_CONFIGURE_ACK on port S3 of 12 bytes containing:
02 01 00 10 02 06 00 2D 0F 00 03 06 C2 34 CD 0D
Packet Info: Code: 02, ID: 01, 16 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F00]
IP-Address [0x03], length: (6 bytes), [194.52.205.13]
Received IPCP_CONFIGURE_REQUEST on port S3 of 30 bytes containing:
01 02 00 22 02 06 00 2D 0F 01 03 06 00 00 00 00 81 06 00
00 00 00 82 06 00 00 00 00 83 06 00 00 00 00
Packet Info: Code: 01, ID: 02, 34 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F01]
IP-Address [0x03], length: (6 bytes), [0.0.0.0]
Primary DNS Server Address [0x81], length: (6 bytes), [0.0.0.0]
Primary NBNS Server Address [0x82], length: (6 bytes), [0.0.0.0]
Secondary DNS Server Address [0x83], length: (6 bytes), [0.0.0.0]
Sending IPCP_CONFIGURE_NAK to port S3 of 16 bytes containing:
03 02 00 10 82 06 00 00 00 00 83 06 C2 34 CD 34
Packet Info: Code: 03, ID: 02, 16 bytes.
Primary NBNS Server Address [0x82], length: (6 bytes), [0.0.0.0]
Secondary DNS Server Address [0x83], length: (6 bytes),
[194.52.205.52]
Received IPCP_CONFIGURE_REQUEST on port S3 of 30 bytes containing:
01 03 00 22 02 06 00 2D 0F 01 03 06 00 00 00 00 81 06 00 00 00 00 82 06
00 00 00 00 83 06 C2 34 CD 34
Packet Info: Code: 01, ID: 03, 34 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F01]
IP-Address [0x03], length: (6 bytes), [0.0.0.0]
Primary DNS Server Address [0x81], length: (6 bytes), [0.0.0.0]
Primary NBNS Server Address [0x82], length: (6 bytes), [0.0.0.0]
Secondary DNS Server Address [0x83], length: (6 bytes),
[194.52.205.52]
Sending IPCP_CONFIGURE_REJECT to port S3 of 10 bytes containing:
04 03 00 0A 82 06 00 00 00 00
Packet Info: Code: 04, ID: 03, 10 bytes.
Primary NBNS Server Address [0x82], length: (6 bytes), [0.0.0.0]
Sending IPCP_CONFIGURE_REQUEST to port S3 of 16 bytes containing:
01 02 00 10 02 06 00 2D 0F 00 03 06 C2 34 CD 0D
Packet Info: Code: 01, ID: 02, 16 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F00]
IP-Address [0x03], length: (6 bytes), [194.52.205.13]
Received IPCP_CONFIGURE_ACK on port S3 of 12 bytes containing:
02 02 00 10 02 06 00 2D 0F 00 03 06 C2 34 CD 0D
Packet Info: Code: 02, ID: 02, 16 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F00]
IP-Address [0x03], length: (6 bytes), [194.52.205.13]
Received IPCP_CONFIGURE_REQUEST on port S3 of 18 bytes containing:
01 04 00 16 02 06 00 2D 0F 01 03 06 00 00 00 00 81 06 00 00 00 00
Packet Info: Code: 01, ID: 04, 22 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F01]
IP-Address [0x03], length: (6 bytes), [0.0.0.0]
Primary DNS Server Address [0x81], length: (6 bytes), [0.0.0.0]
Sending IPCP_CONFIGURE_NAK to port S3 of 16 bytes containing:
03 04 00 10 03 06 C2 C6 5E 1F 81 06 C2 34 CD 03
Packet Info: Code: 03, ID: 04, 16 bytes.
IP-Address [0x03], length: (6 bytes), [194.198.94.31]
Primary DNS Server Address [0x81], length: (6 bytes),
[194.52.205.3]
Received IPCP_CONFIGURE_REQUEST on port S3 of 18 bytes containing:
01 05 00 16 02 06 00 2D 0F 01 03 06 C2 C6 5E 1F 81 06 C2 34 CD 03
Packet Info: Code: 01, ID: 05, 22 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F01]
IP-Address [0x03], length: (6 bytes), [194.198.94.31]
Primary DNS Server Address [0x81], length: (6 bytes),
[194.52.205.3]
Sending IPCP_CONFIGURE_ACK to port S3 of 22 bytes containing:
02 05 00 16 02 06 00 2D 0F 01 03 06 C2 C6 5E 1F 81 06 C2 34 CD 03
Packet Info: Code: 02, ID: 05, 22 bytes.
IP-Compression-Protocol [0x02], length: (6 bytes), Van Jacobson
Compressed TCP/IP [0x002D0F01]
IP-Address [0x03], length: (6 bytes), [194.198.94.31]
Primary DNS Server Address [0x81], length: (6 bytes),
[194.52.205.3]
--- END