Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PACLEN enforced on V2.0 receipt #102

Closed
rlevine opened this issue Jun 5, 2017 · 3 comments
Closed

PACLEN enforced on V2.0 receipt #102

rlevine opened this issue Jun 5, 2017 · 3 comments

Comments

@rlevine
Copy link

rlevine commented Jun 5, 2017

I think I've found a possible issue with the way direwolf uses PACLEN for v2.0 frames.

Currently, PACLEN is enforced for the upper bound on the size of both transmitted and received information fields.

In our field usage, PACLEN is set to 128 for field stations, but longer for server BBS TNCs.

To match the TNC behavior we're expecting, it would be helpful for PACLEN to be enforced only for transmitted frames, and not on reciept from the BBS.

The issue is caused here - ax25_link.c:2212

    if (info_len >= 0 && info_len <= S->n1_paclen) 

Swapping AX25_MAX_INFO_LEN for S->n1_paclen is what I'm after, but a real fix might be to split out params for received and transmitted max lengths in set_version_2_0 () (line 2682) instead of just having one.

Thanks!

Rick

KK6WHJ

@wb2osz
Copy link
Owner

wb2osz commented Jun 5, 2017

Fixed in 'dev' branch.
979fdf1

@wb2osz wb2osz closed this as completed Jun 5, 2017
@wb2osz
Copy link
Owner

wb2osz commented Jun 5, 2017

Thanks for pointing this out.

@rlevine
Copy link
Author

rlevine commented Jun 6, 2017

Thanks for the fix, John!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants