WiMAX TLV value correct in debug but not correct in packet capture

[James Leavitt]

Ok,

After some compiling and configuring, I've managed to get version 3.0.0
up and running, and I seem to be having a similar issue:

Radsniff  on the wire (verified that it is the same in  tcpdump and
wireshark):

Access-Accept Id 204    10.199.10.14:1812 -> 10.199.20.240:6217    +3.541
    Session-Timeout = 86400
    Acct-Interim-Interval = 60
    WiMAX-Packet-Data-Flow-Id = 18359
    WiMAX-Service-Data-Flow-Id = 3513
    WiMAX-Service-Profile-Id = 263782400
    WiMAX-Packet-Data-Flow-Id = 18359
    WiMAX-Service-Data-Flow-Id = 18359
    WiMAX-Service-Profile-Id = 0
    Microsoft-Attr-17 =
0x86c4d95414f6aecd8f16cc5ef0aa1ff8b5354e553cb724bc9f103636741cdef35a57f89db1afca3711c57d5d900a06b2578b
    Microsoft-Attr-16 =
0x8812b94254b5c21e2be59bd62927f045f5536b1844f79f45ca7d9442db106f538f8b960b61bb483f61bad39442975af58612
    EAP-Message = 0x03070004
    Message-Authenticator = 0xd4654370830d4a11371d217714ee7b4f
    User-Name = "1B2D2F35483D3BEF7D8827EA61F8EEA5 at undisclosed.com"

Debug on the radius server process shows things as they are in the DB:

Sending Access-Accept of id 204 to 10.199.20.240 port 6217
    Session-Timeout := 86400
    Acct-Interim-Interval := 60
    WiMAX-Packet-Data-Flow-Id := 14
    WiMAX-Service-Data-Flow-Id := 14
    WiMAX-Service-Profile-Id := 14
    WiMAX-Packet-Data-Flow-Id += 17
    WiMAX-Service-Data-Flow-Id += 17
    WiMAX-Service-Profile-Id += 17
    MS-MPPE-Recv-Key =
0xc5232594526fb99097311c861a49671710a2d6db7c0068788ef0122c9b551ae1
    MS-MPPE-Send-Key =
0xed6c9de58fabf8519b09d2900849d611142ece093a7a6973869761872d9c9bc6
    EAP-Message = 0x03070004
    Message-Authenticator = 0x00000000000000000000000000000000
    User-Name = "1B2D2F35483D3BEF7D8827EA61F8EEA5 at undisclosed.com"

I am trying to get a tcp capture but the system is now not letting me
re-auth (I was working on fixing the CSID in the accounting and must
have changed something it doesn't like) so not sure what's up, but I
don't believe v3 is the solution.

I will get a tcpdump if it's worth while.

Thanks,

James


On 07/30/2013 12:01 PM, James Leavitt wrote:
> Re: WiMAX TLV value correct in debug but not correct in packet capture
>
> Thank you Gentlemen,
>
> I am working with Alvarion CPEs but a WiChorus ASN, which I have setup
> on a commercial AAA without issues. I also have Freeradius working with
> WiChorus on another instance also but not for receiving these particular
> TLVs.
>
> I initially performed a tcpdump and this was where I was seeing the
> different values (which match radsniff btw) than what was programmed. I
> then compared the capture to our working solution (a commercial radius
> platform) and confirmed that the values radsniff / tcpdump were what I
> was expecting, which in turn do not match the output from Freeradius. I
> feel the problem is when the values are copied to the outer tunnel, but
> just these TLVs get corrupted.
>
> I'll take a look at 3.0.0 and see if I can work with that and post back
> my findings.
>
> Thanks again,
>
> James
>
>
>
> On 07/30/2013 11:13 AM, David Peterson wrote:
> > RE: WiMAX TLV value correct in debug but not correct in packet capture
> >
> > Don't forget if the hardware is Alvarion or Runcom you cannot use the
> > standard dictionaries.
> >
> > Alvarion (now Telrad) is proprietary but similar to the standard
> > dictionary
> > and Runcom only uses their own.
> >
> > David
> >
> >
> > -----Original Message-----
> > From:
> >
> freeradius-users-bounces+davidp=wirelessconnections.net at lists.freeradius.org
> >
> [mailto:freeradius-users-bounces+davidp=wirelessconnections.net at lists.freera
> > dius.org] On Behalf Of Alan DeKok
> > Sent: Tuesday, July 30, 2013 8:02 AM
> > To: FreeRadius users mailing list
> > Subject: Re: WiMAX TLV value correct in debug but not correct in packet
> > capture
> >
> > James Leavitt wrote:
> > > I've probably missed something or buggered an option, but I've
> > > searched and searched and cannot find an answer to this. This is for a
> > > WiMAX deployment and am using the built in dictionaries. The issue is
> > > with the WiMAX-Packet-Flow-Descriptor tlv .
> > ...
> > > Everything looks good but on a pcap / radsniff I get this:
> >
> >   Put the raw "pcap" file somewhere.  Maybe the issue is the server,
> maybe
> > it's radsniff.
> >
> >   You could also try the git branch "release_branch_3.0.0".  It has a
> > re-written WiMAX encoder / decoder, which now works everywhere.
> >
> >   Alan DeKok.
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
> >
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
> >
> > --
> > This message has been scanned by MailScanner
> >
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
> --
> This message has been scanned by MailScanner
>

-- 


James Leavitt
Network Systems Architect

Xplornet Communications Inc.
300 Lockhart Mill Road
Woodstock, NB
E7M 5C3

Phone: (506) 324-8659
Fax: (506) 328-1582
Cell: (506) 324-4960
Helpdesk: (888) 439-6511

Email: james.leavitt at corp.xplornet.com <mailto: james.leavitt at corp.xplornet.com> 

Xplornet - Broadband Everywhere.

GPG / SSH Public Keys in V-Card Notes