FreeBSD Bugzilla – Attachment 6554 Details for
Bug 14766
In libalias.3, section 4.4/4.5 are contained illegal section.
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
file.diff
file.diff (text/plain), 2.09 KB, created by
Kazutoshi Kubota
on 1999-11-07 15:40:01 UTC
(
hide
)
Description:
file.diff
Filename:
MIME Type:
Creator:
Kazutoshi Kubota
Created:
1999-11-07 15:40:01 UTC
Size:
2.09 KB
patch
obsolete
>*** libalias.3.orig Sun Nov 7 23:06:17 1999 >--- libalias.3 Sun Nov 7 23:18:15 1999 >*************** >*** 495,518 **** > PacketAliasRedirectDelete(), then a program crash > or unpredictable operation could result, so it is > necessary to be careful using this function. >- .Sh 5. Fragment Handling >- The functions in this section are used to deal with >- incoming fragments. >- >- Outgoing fragments are handled within PacketAliasOut() >- by changing the address according to any >- applicable mapping set by PacketAliasRedirectAddress(), >- or the default aliasing address set by >- PacketAliasSetAddress(). >- >- Incoming fragments are handled in one of two ways. >- If the header of a fragmented IP packet has already >- been seen, then all subsequent fragments will be >- re-mapped in the same manner the header fragment >- was. Fragments which arrive before the header >- are saved and then retrieved once the header fragment >- has been resolved. >- > .Ss 4.4 PacketAliasProxyRule() > > .Ft int >--- 495,500 ---- >*************** >*** 599,605 **** > This function is usually used to redirect outgoing connections for > internal machines that are not permitted certain types of internet > access, or to restrict access to certain external machines. >- > .Ss 4.5 PacketAliasPptp() > > .Ft extern int >--- 581,586 ---- >*************** >*** 627,633 **** >--- 608,630 ---- > .Pq 255.255.255.255 , > .Dv PPTP > aliasing is disabled. >+ .Sh 5. Fragment Handling >+ The functions in this section are used to deal with >+ incoming fragments. > >+ Outgoing fragments are handled within PacketAliasOut() >+ by changing the address according to any >+ applicable mapping set by PacketAliasRedirectAddress(), >+ or the default aliasing address set by >+ PacketAliasSetAddress(). >+ >+ Incoming fragments are handled in one of two ways. >+ If the header of a fragmented IP packet has already >+ been seen, then all subsequent fragments will be >+ re-mapped in the same manner the header fragment >+ was. Fragments which arrive before the header >+ are saved and then retrieved once the header fragment >+ has been resolved. > .Ss 5.1 PacketAliasSaveFragment() > > .Ft int
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 14766
: 6554