/freebsd/share/examples/ipfilter/ |
H A D | ipf.conf.restrictive | 18 # 150 outgoing ed1 20 # 250 outgoing fxp0 48 # outgoing ed1 traffic - group 150 49 # Setup outgoing DNS 52 # allow outgoing http-service 54 # allow outgoing smtp traffic 56 # allow outgoing pop3 traffic 58 # allow outgoing ftp traffic 70 # outgoing traffic on fxp0 - group 250
|
H A D | firewall.2 | 51 # these don't have daemons listening but are used by outgoing
|
/freebsd/sys/contrib/device-tree/Bindings/soc/qcom/ |
H A D | qcom,smp2p.txt | 29 Definition: three entries specifying the outgoing ipc bit used for 70 If not specified this node will denote the outgoing entry 78 Usage: required for outgoing entries
|
H A D | qcom,smsm.txt | 18 Definition: three entries specifying the outgoing ipc bit used for 80 encompasses one outbound entry and the outgoing interrupt for the wireless
|
H A D | qcom,aoss-qmp.txt | 40 Definition: reference to the mailbox representing the outgoing doorbell
|
H A D | qcom,smd.txt | 34 Definition: three entries specifying the outgoing ipc bit used for
|
/freebsd/sys/contrib/device-tree/Bindings/spi/ |
H A D | nvidia,tegra114-spi.txt | 28 with this tap value. This property is used to tune the outgoing data from 29 Tegra SPI master with respect to outgoing Tegra SPI master clock.
|
/freebsd/share/examples/ipfilter/rules/ |
H A D | example.2 | 2 # block all outgoing TCP packets on le0 from any host to port 23 of
|
H A D | tcpstate | 2 # Only allow TCP packets in/out of le0 if there is an outgoing connection setup
|
/freebsd/share/examples/pf/ |
H A D | faq-example3 | 11 # each queue can be controlled. the max outgoing bandwidth is 1.5Mbps. 17 # outgoing traffic on fxp0. 42 # std_int - the standard queue. also the default queue for outgoing
|
/freebsd/contrib/unbound/ |
H A D | README | 4 many (10000) outgoing ports. By default max 256 ports are opened at
|
H A D | README.md | 29 outgoing ports. By default max 256 ports are opened at the same time and the
|
/freebsd/contrib/unbound/doc/ |
H A D | example.conf.in | 71 # specify the interfaces to send outgoing queries to authoritative 73 # is used. Specify every interface on a 'outgoing-interface:' line. 74 # outgoing-interface: 192.0.2.153 75 # outgoing-interface: 2001:DB8::5 76 # outgoing-interface: 2001:DB8::6 80 # outgoing-interface: 2001:DB8::/64 93 # outgoing-range: 4096 96 # making outgoing queries, using an outgoing interface. 97 # outgoing-port-permit: 32768 100 # making outgoing queries, using an outgoing interface. [all …]
|
H A D | README.DNS64 | 34 orthogonal to DNS64; it allows Unbound to send outgoing queries to IPv4-only
|
H A D | README | 24 (thousands) of outgoing ports. This improves randomization and spoof 25 resistance. It also allows a higher number of outgoing queries.
|
/freebsd/contrib/sendmail/cf/feature/ |
H A D | genericstable.m4 | 22 # Generics table (mapping outgoing addresses)
|
/freebsd/sys/contrib/device-tree/Bindings/phy/ |
H A D | qcom-pcie2-phy.txt | 23 - clock-output-names: name of the outgoing clock signal from the PHY PLL
|
/freebsd/contrib/unbound/util/ |
H A D | configlexer.lex | 224 outgoing-range{COLON} { YDVAR(1, VAR_OUTGOING_RANGE) } 225 outgoing-port-permit{COLON} { YDVAR(1, VAR_OUTGOING_PORT_PERMIT) } 226 outgoing-port-avoid{COLON} { YDVAR(1, VAR_OUTGOING_PORT_AVOID) } 227 outgoing-num-tcp{COLON} { YDVAR(1, VAR_OUTGOING_NUM_TCP) } 238 outgoing-tcp-mss{COLON} { YDVAR(1, VAR_OUTGOING_TCP_MSS) } 279 outgoing-interface{COLON} { YDVAR(1, VAR_OUTGOING_INTERFACE) }
|
/freebsd/share/doc/IPv6/ |
H A D | IMPLEMENTATION | 298 outgoing interface. To configure the default outgoing interface, use 518 outgoing interface through another API, which can disambiguate the 531 ambiguous destination, but it still tries to get the outgoing 533 the outgoing packet using in6_selectsrc(). If the interface is 569 the outgoing interface of a packet. Similarly, the IPV6_PKTINFO or 576 they are too strong for outgoing packets. For example, consider a 579 we can only specify one of the interfaces for the outgoing packet with 608 + To disambiguate scoped addresses of outgoing packets, 609 * if it is okay to just specify the outgoing interface, use the 626 syntax, as documented in RFC4007. You can specify the outgoing link, [all …]
|
/freebsd/usr.sbin/ppp/ |
H A D | README.nat | 240 translated local address (192.168.0.4), but outgoing 256 A handler needs to be added to correctly NAT outgoing error messages. 267 host address, outgoing NAT and incoming de-NATing). 374 - Now supports outgoing as well as incoming ICMP error messages/
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | DTLSv1_listen.pod | 72 outgoing datagrams transmitted by DTLS to be transmitted to that host. In other 74 socket means that any host on the network can cause outgoing DTLS traffic to be
|
H A D | SSL_connect.pod | 39 buffer outgoing TCP data if a TCP packet has already been sent for which no
|
/freebsd/contrib/libpcap/doc/ |
H A D | README.hpux | 25 >it, but I can only see incoming data, never outgoing. 56 > outgoing. I have tried tcpflow-0.12 which also uses libpcap and the
|
H A D | README.aix | 110 be responsible for DLPI not being able to capture outgoing packets.
|
H A D | README.macos | 74 not be able to capture outgoing packets.)
|