Hello.

I'm trying to do some kind of packet assembler
disassembler between an interface x.21 from a
2507 and an interface rs232 from a pc.

I'm using a pic 16f873 with a set of max488 in the
side of cisco and a max232 in the side of pc.

I have a little problem with a strange (for me) packet.
who looks like this:

..181818181041FFF1EDFF3FFEBD7E7FE517D3B3169A060606060606...

If I toggle 0 and 1 and shift some bits:

...     01111110 01111110
01111110 01111110 11111011 11
10000000 00000011 10000100
10000000 00110000 00000000
01010000 10100000 01100000

00000110 (*)
10111010 (*)
00001011 (*)
00010011 (*)

00111010 01011001
01111110 01111110 01111110 ...


The debug console is telling this:

ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 605DD0C8
PPP Serial1: O LCP CONFREQ(0x1) id 12 len 10
   MAGICNUMBER (6) 0x60 0x5D 0xD0 0xC8


Question 1.
I can recognise this magic number on (*)
(lsb first)

00000110 60
10111010 5D
00001011 D0
00010011 C8

but I cannot understand why the packet
is "shifted 2 bits".
I have read the datasheet of Hitachi HD64570 and
it seems to be a 8 bit serial controller.
Why the iddle caracter (0x7e) after the packet is not
the same before the packet?
Is there some kind of strangeous encapsulation?
How must I read this packet?

The router setup:
int s1
ip address 192.168.0.1/24
clock rate 1200
encap ppp


Question 2.
The datasheet of this chip (Hitachi HD64570) tells that there are a mode
asynchronous capable.
Is there any command to tell the router how to
make serial interface asynchronous?

Question 3.
If I'm able to read this serial interface with
another standard like eia/tia-232 or v.35
will I see exactly the same bits ?
i.e: the serial cable assemblie and pinouts
force the way bits are transmitted ?

I would highly appreciate any suggestion.
Best regards.



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=66373&t=66373
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to