[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::common_brouters

Title:Digital Brouters Conference
Notice:New common-code brouter family: RouteAbout, DECswitch 900
Moderator:MARVIN::HARTLL
Created:Mon Jul 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:929
Total number of notes:3736

780.0. "Problem RA90EI and copying .exe files fr. PC to LAN" by STU03::RUEGGEN () Wed Mar 05 1997 05:46

	Hello,


	I have a configuration where 4 Win95 PC's equipped with an ISDN
	card connect to their local LAN via an RouteabtAccess90EI.

	Everything works fine except the copying of .dll or .exe files from
    	PC to their LAN. Copying from LAN to PC works fine.
	When the copy starts I can see the following in ELS:


ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 1504 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 1272 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 146 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 202 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 145 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 202 nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0


	I lowered the PPP LCP option Max MRU to 1504 but no change.
	I still see the same "Pkt ln of 2048" and the "Bd fr" message.

	When they copy large .txt files, there is no problem but the
	Pkt ln never exeeds 1504.

	Can I change anything to avoid this ?

	Btw. what does "MRU default high" mean ? 


	Thank you and regards

	Ulrich Rueggen
T.RTitleUserPersonal
Name		DateLines
780.1mgb.rkg.dec.com::GILLOTTMark Gillott, 831-3172 (rkg)Thu Mar 06 1997 04:2716
So do  the  PCs  have  an  ISDN  card  and  are thus talking directly to the
RA90EI?.   Does  it  look  like PPP negotiated the correct MRU sizes?.  What
version is the RA90EI running?.

If everything  looks "ok" on the RA90EI side, then I sould suspect a problem
on  the  PC.   Since  the copy is from PC->LAN and the RA90EI is complaining
about  a  received  packet being too big, then I'd suspect that the PPP/ISDN
s/w on the PC has a bug that causes it to generate oversized frames.

� 	Btw. what does "MRU default high" mean ? 

In what context?. 

Mark
780.2more infoSTU03::RUEGGENThu Mar 06 1997 04:4213
    Hello Marc,
    
    with MRU default high I refer to an option in the PPP LPC setup. The
    router asks for max MRU and MRU default high (yes/no).
    
    The router is running V2.0-2
    
    When the router negotiates for a max MRU of 2048 and can't handle a
    packet of that size, why is this an erroneous packet ?
    
    I will run another trace to show the neg. MRU size and post it here
    
    Thank you for your quick reply
780.3I hope this helpsSTU03::RUEGGENThu Mar 06 1997 07:13114
	Hello Marc,


	here the start of the communication. As I read it they finally 
	agree on MRU 1500.




 PPP.045: ck accm 0x000A0000
 PPP.026: lcp req rslt: Configure Ack, opt 2, ln 6, nt 7 int PPP/4
 PPP.036: mk accm 0x000A0000
 PPP.047: ck mag 0x0061347F
 PPP.026: lcp req rslt: Configure Ack, opt 5, ln 6, nt 7 int PPP/4
 PPP.038: mk mag 0x0061347F
 PPP.019: LCP/Ack Rcvd lcp_makeoptions nt 7 int PPP/4
 PPP.035: mk mru 2042
 PPP.016: LCP/Ack Rcvd snd Configure Nak, id 3 len 8, nt 7 int PPP/4
 PPP.014: LCP/Ack Rcvd fsm_timer nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 24 nt 2 int ISDN/0
 PPP.017: LCP/Ack Rcvd rcv Configure Request, id 4 len 20, nt 7 int PPP/4
 PPP.019: LCP/Ack Rcvd lcp_request nt 7 int PPP/4
 PPP.044: ck mru 1500
 PPP.026: lcp req rslt: Configure Ack, opt 1, ln 4, nt 7 int PPP/4
 PPP.035: mk mru 1500
 PPP.045: ck accm 0x000A0000


	Here the copying starts and the Router seems to receive a 2048Byte
	frame.

	Would this be a PC problem ?


PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 127 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 127 len 34, nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 128 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 128 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 100 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 164 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 152 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 146 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 77 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 1504 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 1272 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 147 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 93 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 148 nt 2 int ISDN/0
PPP.007: Rcv Bd fr addr 93 nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 129 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 129 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 147 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 93 nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 130 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 130 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 147 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 93 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 44 nt 2 int ISDN/0
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 131 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 131 len 34, nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 132 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 132 len 34, nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 133 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 133 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 2048 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 126 nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 147 nt 2 int ISDN/0
 PPP.007: Rcv Bd fr addr 93 nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 134 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 134 len 34, nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 135 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 135 len 34, nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 136 len 34, nt 7 int PPP/4
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
 PPP.017: LCP/Open rcv Echo Reply, id 136 len 34, nt 7 int PPP/4
 PPP.003: Mnt nt 7 int PPP/4
 PPP.016: LCP/Open snd Echo Request, id 137 len 34, nt 7 int PPP/4




	Thanks and regards

	Ulrich
780.4MARVIN::TURNERNeil Turner IPEG REO, 830-4140Fri Mar 07 1997 03:0936
It looks like we have negotiated an MRU of 1500 but to be sure you can use
the T 5, PPP> LIS CONTROL LCP on the running link. This will show you the
negotiated parameters in both directions. eg.

*t 5
+net 'dial-circuit-net-number'
Point-to-Point Console
PPP>lis con lcp

Version:                   1
LCP State:                 Open
Previous State:            Ack Rcvd
Time Since Change:         13 hours, 33 minutes and 15 seconds

LCP Option                 Local                      Remote
----------                 -----                      ------
Max Receive Unit:          2042                       2042
Async Char Mask:           FFFFFFFF                   FFFFFFFF
Authentication:            None                       None
Magic Number:              1028C10                    12285A8
Protocol Compr:            No                         No
Addr/Cntl Compr:           No                         No
32-Bit Checksum:           No                         No

If an MRU of 1500 is being used then we should not be seeing frames of 2048
bytes.

However the error being reported by PPP 'Rcv Bd fr addr 126 nt 7 in PPP/4'
indicated corruption at the front of the frame. Basically the first byte of
the PPP frame should start with 0xFF (255) and the RouteAbout is seeing a
different value (0x7E or 126 in this case).

It looks like the remote PC ISDN implementation is sending oversized badly
formatted packets.

Neil