The problem that you are seeing is in libpppoe.c,
#define TAG_DATA(type, tag_ptr) ((type *) tag_ptr+1)
This is causing the failure in verify_packet where hu_val is set, if you
printf the value of 'ses' you will probably see that the f1a0 is correct, it
is the 0400 causing the miscompare.
hu_val = *TAG_DATA(struct session*, p->tags[TAG_HOST_UNIQ]);
Maybe someone more familiar with the arm compiler can shed some light?
David
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Doug Dunlop
Sent: Monday, April 02, 2001 1:32 PM
To: [EMAIL PROTECTED]
Subject: pppoe using 2.4 kernel
A couple of months ago, there was a thread about using pppoe on an arm
machine. There seemed at the time to be some people trying to use it.
I have a graphics client plus and have been trying to get pppoe working
without much success.
I am using a 2.4.0-test11 kernel with ppp and pppoe compiled in (not
modules)
When I try to connect, I get a 'sending PADI ' message in the logfile and
ifconfig confirms that there is a packet sent.
Next, I get a message "HOST_UNIQ mismatch:0400f1a0 %i" and "Failed to
negotiate PPPoE connection: 25 Inappropriate ioctl for device"
The latter two messages only appear if there is a PPPoE server on the
network. Otherwise the 'sending PADI' is the last message that I get.
Any suggestions? I wouldn't mind using someone else's working setup.
Thanks,
Doug
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
