linux ip-route - routing table management

新手必看!用Cisco Packet Tracer模拟真实公司网络:从VLAN划分到DHCP配置全流程 本文详细介绍了如何使用Cisco Packet Tracer模拟构建企业级网络环境,涵盖VLAN划分、DHCP配置、无线网络部署等关键步骤。通过实战案例,帮助网络新手掌握从基础规划到高级配置的全流程,提升网络架构设计能力。 阅读详情
linux:~$ man ip-route
IP-ROUTE(8)                                     Linux                                    IP-ROUTE(8)


NAME
       ip-route - routing table management


SYNOPSIS
       ip [ ip-OPTIONS ] route  { COMMAND | help }


       ip route { list | flush } SELECTOR


       ip route save SELECTOR


       ip route restore


       ip route get ADDRESS [ from ADDRESS iif STRING  ] [ oif STRING ] [ tos TOS ]


       ip route { add | del | change | append | replace } ROUTE


       SELECTOR := [ root PREFIX ] [ match PREFIX ] [ exact PREFIX ] [ table TABLE_ID ] [ proto
               RTPROTO ] [ type TYPE ] [ scope SCOPE ]


       ROUTE := NODE_SPEC [ INFO_SPEC ]


       NODE_SPEC := [ TYPE ] PREFIX [ tos TOS ] [ table TABLE_ID ] [ proto RTPROTO ] [ scope SCOPE ]
               [ metric METRIC ]


       INFO_SPEC := NH OPTIONS FLAGS [ nexthop NH ] ...


       NH := [ via ADDRESS ] [ dev STRING ] [ weight NUMBER ] NHFLAGS


       OPTIONS := FLAGS [ mtu NUMBER ] [ advmss NUMBER ] [ rtt TIME ] [ rttvar TIME ] [ reordering
               NUMBER ] [ window NUMBER ] [ cwnd NUMBER ] [ ssthresh REALM ] [ realms REALM ] [
               rto_min TIME ] [ initcwnd NUMBER ] [ initrwnd NUMBER ] [ quickack BOOL ]


       TYPE := [ unicast | local | broadcast | multicast | throw | unreachable | prohibit | black-
               hole | nat ]


       TABLE_ID := [ local| main | default | all | NUMBER ]


       SCOPE := [ host | link | global | NUMBER ]


       NHFLAGS := [ onlink | pervasive ]


       RTPROTO := [ kernel | boot | static | NUMBER ]


DESCRIPTION
       ip route is used to manipulate entries in the kernel routing tables.


       Route types:


               unicast - the route entry describes real paths to the destinations covered by the
               route prefix.


               unreachable - these destinations are unreachable.  Packets are discarded and the ICMP
               message host unreachable is generated.  The local senders get an EHOSTUNREACH error.


               blackhole - these destinations are unreachable.  Packets are discarded silently.  The
               local senders get an EINVAL error.


               prohibit - these destinations are unreachable.  Packets are discarded and the ICMP
               message communication administratively prohibited is generated.  The local senders
               get an EACCES error.


               local - the destinations are assigned to this host.  The packets are looped back and
               delivered locally.


               broadcast - the destinations are broadcast addresses.  The packets are sent as link
               broadcasts.


               throw - a special control route used together with policy rules. If such a route is
               selected, lookup in this table is terminated pretending that no route was found.
               Without policy routing it is equivalent to the absence of the route in the routing
               table.  The packets are dropped and the ICMP message net unreachable is generated.
               The local senders get an ENETUNREACH error.


               nat - a special NAT route.  Destinations covered by the prefix are considered to be
               dummy (or external) addresses which require translation to real (or internal) ones
               before forwarding.  The addresses to translate to are selected with the attribute
               via.  Warning: Route NAT is no longer supported in Linux 2.6.


               anycast - not implemented the destinations are anycast addresses assigned to this
               host.  They are mainly equivalent to local with one difference: such addresses are
               invalid when used as the source address of any packet.


               multicast - a special type used for multicast routing.  It is not present in normal
               routing tables.


       Route tables: Linux-2.x can pack routes into several routing tables identified by a number in
       the range from 1 to 2^31 or by name from the file /etc/iproute2/rt_tables By default all nor-
       mal routes are inserted into the main table (ID 254) and the kernel only uses this table when
       calculating routes.  Values (0, 253, 254, and 255) are reserved for built-in use.


       Actually, one other table always exists, which is invisible but even more important.  It is
       the local table (ID 255).  This table consists of routes for local and broadcast addresses.
       The kernel maintains this table automatically and the administrator usually need not modify
       it or even look at it.


       The multiple routing tables enter the game when policy routing is used.


       ip route add
              add new route


       ip route change
              change route


       ip route replace
              change or add new one


              to TYPE PREFIX (default)
                     the destination prefix of the route.  If TYPE is omitted, ip assumes type uni-
                     cast.  Other values of TYPE are listed above.  PREFIX is an IP or IPv6 address
                     optionally followed by a slash and the prefix length.  If the length of the
                     prefix is missing, ip assumes a full-length host route.  There is also a spe-
                     cial PREFIX default - which is equivalent to IP 0/0 or to IPv6 ::/0.


              tos TOS


              dsfield TOS
                     the Type Of Service (TOS) key.  This key has no associated mask and the longest
                     match is understood as: First, compare the TOS of the route and of the packet.
                     If they are not equal, then the packet may still match a route with a zero TOS.
                     TOS is either an 8 bit hexadecimal number or an identifier from
                     /etc/iproute2/rt_dsfield.


              metric NUMBER


              preference NUMBER
                     the preference value of the route.  NUMBER is an arbitrary 32bit number.


              table TABLEID
                     the table to add this route to.  TABLEID may be a number or a string from the
                     file /etc/iproute2/rt_tables.  If this parameter is omitted, ip assumes the
                     main table, with the exception of local, broadcast and nat routes, which are
                     put into the local table by default.


              dev NAME
                     the output device name.


              via ADDRESS
                     the address of the nexthop router.  Actually, the sense of this field depends
                     on the route type.  For normal unicast routes it is either the true next hop
                     router or, if it is a direct route installed in BSD compatibility mode, it can
                     be a local address of the interface.  For NAT routes it is the first address of
                     the block of translated IP destinations.


              src ADDRESS
                     the source address to prefer when sending to the destinations covered by the
                     route prefix.


              realm REALMID
                     the realm to which this route is assigned.  REALMID may be a number or a string
                     from the file /etc/iproute2/rt_realms.


              mtu MTU


              mtu lock MTU
                     the MTU along the path to the destination.  If the modifier lock is not used,
                     the MTU may be updated by the kernel due to Path MTU Discovery.  If the modi-
                     fier lock is used, no path MTU discovery will be tried, all packets will be
                     sent without the DF bit in IPv4 case or fragmented to MTU for IPv6.


              window NUMBER
                     the maximal window for TCP to advertise to these destinations, measured in
                     bytes.  It limits maximal data bursts that our TCP peers are allowed to send to
                     us.


              rtt TIME
                     the initial RTT ('Round Trip Time') estimate. If no suffix is specified the
                     units are raw values passed directly to the routing code to maintain compati-
                     bility with previous releases.  Otherwise if a suffix of s, sec or secs is used
                     to specify seconds and ms, msec or msecs to specify milliseconds.


              rttvar TIME (2.3.15+ only)
                     the initial RTT variance estimate. Values are specified as with rtt above.


              rto_min TIME (2.6.23+ only)
                     the minimum TCP Retransmission TimeOut to use when communicating with this des-
                     tination.  Values are specified as with rtt above.


              ssthresh NUMBER (2.3.15+ only)
                     an estimate for the initial slow start threshold.


              cwnd NUMBER (2.3.15+ only)
                     the clamp for congestion window.  It is ignored if the lock flag is not used.


              initcwnd NUMBER (2.5.70+ only)
                     the initial congestion window size for connections to this destination.  Actual
                     window size is this value multiplied by the MSS (``Maximal Segment Size'') for
                     same connection. The default is zero, meaning to use the values specified in
                     RFC2414.


              initrwnd NUMBER (2.6.33+ only)
                     the initial receive window size for connections to this destination.  Actual
                     window size is this value multiplied by the MSS of the connection.  The default
                     value is zero, meaning to use Slow Start value.


              quickack BOOL (3.11+ only)
                     Enable or disable quick ack for connections to this destination.


              advmss NUMBER (2.3.15+ only)
                     the MSS ('Maximal Segment Size') to advertise to these destinations when estab-
                     lishing TCP connections.  If it is not given, Linux uses a default value calcu-
                     lated from the first hop device MTU.  (If the path to these destination is
                     asymmetric, this guess may be wrong.)


              reordering NUMBER (2.3.15+ only)
                     Maximal reordering on the path to this destination.  If it is not given, Linux
                     uses the value selected with sysctl variable net/ipv4/tcp_reordering.


              nexthop NEXTHOP
                     the nexthop of a multipath route.  NEXTHOP is a complex value with its own syn-
                     tax similar to the top level argument lists:


                             via ADDRESS - is the nexthop router.


                             dev NAME - is the output device.


                             weight NUMBER - is a weight for this element of a multipath route
                             reflecting its relative bandwidth or quality.


              scope SCOPE_VAL
                     the scope of the destinations covered by the route prefix.  SCOPE_VAL may be a
                     number or a string from the file /etc/iproute2/rt_scopes.  If this parameter is
                     omitted, ip assumes scope global for all gatewayed unicast routes, scope link
                     for direct unicast and broadcast routes and scope host for local routes.


              protocol RTPROTO
                     the routing protocol identifier of this route.  RTPROTO may be a number or a
                     string from the file /etc/iproute2/rt_protos.  If the routing protocol ID is
                     not given, ip assumes protocol boot (i.e. it assumes the route was added by
                     someone who doesn't understand what they are doing).  Several protocol values
                     have a fixed interpretation.  Namely:


                             redirect - the route was installed due to an ICMP redirect.


                             kernel - the route was installed by the kernel during autoconfigura-
                             tion.


                             boot - the route was installed during the bootup sequence.  If a rout-
                             ing daemon starts, it will purge all of them.


                             static - the route was installed by the administrator to override
                             dynamic routing. Routing daemon will respect them and, probably, even
                             advertise them to its peers.


                             ra - the route was installed by Router Discovery protocol.


                     The rest of the values are not reserved and the administrator is free to assign
                     (or not to assign) protocol tags.


              onlink pretend that the nexthop is directly attached to this link, even if it does not
                     match any interface prefix.


       ip route delete
              delete route
              ip route del has the same arguments as ip route add, but their semantics are a bit
              different.


              Key values (to, tos, preference and table) select the route to delete.  If optional
              attributes are present, ip verifies that they coincide with the attributes of the
              route to delete.  If no route with the given key and attributes was found, ip route
              del fails.


       ip route show
              list routes
              the command displays the contents of the routing tables or the route(s) selected by
              some criteria.


              to SELECTOR (default)
                     only select routes from the given range of destinations.  SELECTOR consists of
                     an optional modifier (root, match or exact) and a prefix.  root PREFIX selects
                     routes with prefixes not shorter than PREFIX.  F.e.  root 0/0 selects the
                     entire routing table.  match PREFIX selects routes with prefixes not longer
                     than PREFIX.  F.e.  match 10.0/16 selects 10.0/16, 10/8 and 0/0, but it does
                     not select 10.1/16 and 10.0.0/24.  And exact PREFIX (or just PREFIX) selects
                     routes with this exact prefix. If neither of these options are present, ip
                     assumes root 0/0 i.e. it lists the entire table.


              tos TOS


              dsfield TOS
                     only select routes with the given TOS.


              table TABLEID
                     show the routes from this table(s).  The default setting is to show table main.
                     TABLEID may either be the ID of a real table or one of the special values:


                             all - list all of the tables.


                             cache - dump the routing cache.


              cloned


              cached list cloned routes i.e. routes which were dynamically forked from other routes
                     because some route attribute (f.e. MTU) was updated.  Actually, it is equiva-
                     lent to table cache.


              from SELECTOR
                     the same syntax as for to, but it binds the source address range rather than
                     destinations.  Note that the from option only works with cloned routes.


              protocol RTPROTO
                     only list routes of this protocol.


              scope SCOPE_VAL
                     only list routes with this scope.


              type TYPE
                     only list routes of this type.


              dev NAME
                     only list routes going via this device.


              via PREFIX
                     only list routes going via the nexthop routers selected by PREFIX.


              src PREFIX
                     only list routes with preferred source addresses selected by PREFIX.


              realm REALMID


              realms FROMREALM/TOREALM
                     only list routes with these realms.


       ip route flush
              flush routing tables
              this command flushes routes selected by some criteria.


              The arguments have the same syntax and semantics as the arguments of ip route show,
              but routing tables are not listed but purged.  The only difference is the default
              action: show dumps all the IP main routing table but flush prints the helper page.


              With the -statistics option, the command becomes verbose. It prints out the number of
              deleted routes and the number of rounds made to flush the routing table. If the option
              is given twice, ip route flush also dumps all the deleted routes in the format
              described in the previous subsection.


       ip route get
              get a single route
              this command gets a single route to a destination and prints its contents exactly as
              the kernel sees it.


              to ADDRESS (default)
                     the destination address.


              from ADDRESS
                     the source address.


              tos TOS


              dsfield TOS
                     the Type Of Service.


              iif NAME
                     the device from which this packet is expected to arrive.


              oif NAME
                     force the output device on which this packet will be routed.


              connected
                     if no source address (option from) was given, relookup the route with the
                     source set to the preferred address received from the first lookup.  If policy
                     routing is used, it may be a different route.


              Note that this operation is not equivalent to ip route show.  show shows existing
              routes.  get resolves them and creates new clones if necessary.  Essentially, get is
              equivalent to sending a packet along this path.  If the iif argument is not given, the
              kernel creates a route to output packets towards the requested destination.  This is
              equivalent to pinging the destination with a subsequent ip route ls cache, however, no
              packets are actually sent.  With the iif argument, the kernel pretends that a packet
              arrived from this interface and searches for a path to forward the packet.


       ip route save
              save routing table information to stdout
              This command behaves like ip route show except that the output is raw data suitable
              for passing to ip route restore.


       ip route restore
              restore routing table information from stdin
              This command expects to read a data stream as returned from ip route save.  It will
              attempt to restore the routing table information exactly as it was at the time of the
              save, so any translation of information in the stream (such as device indexes) must be
              done first.  Any existing routes are left unchanged.  Any routes specified in the data
              stream that already exist in the table will be ignored.


EXAMPLES
       ip ro
           Show all route entries in the kernel.


       ip route add default via 192.168.1.1 dev eth0
           Adds a default route (for all addresses) via the local gateway 192.168.1.1 that can be
           reached on device eth0.


SEE ALSO
       ip(8)


AUTHOR
       Original Manpage by Michail Litvak <mci@owl.openwall.com>


iproute2                                     13 Dec 2012                                 IP-ROUTE(8)
linux:~$ 
linux:~$ 
华为小型园区网三层架构配置实战:VLAN、M-LAG与防火墙策略详解 在中小型企业网络建设中,VLAN(虚拟局域网)是实现网络逻辑隔离与安全分区的核心技术,通过划分不同的广播域来提升网络性能与管理效率。其原理是基于IEEE 802.1Q标准,在数据帧中插入VLAN标签,使单条物理链路能承载多个逻辑网络的数据。这项技术的核心价值在于简化网络结构、增强安全性并支持灵活的业务部署。在典型的接入-汇聚-出口三层架构中,VLAN规划与配置是基础,常与M-LAG(跨设备链路聚合)技术结合,后者通过将两台物理交换机虚拟成一台逻辑设备,实现设备级冗余与链路高可用,极大提升了汇聚层的可靠性。这 阅读详情

相关推荐

Claude代理网关实战:Next.js+Hono构建可审计AI基础设施

API网关是现代AI应用的核心中间件,它不仅实现协议转换与请求转发,更承载负载均衡、熔断限流、可观测性与成本计量等关键能力。基于OpenAI兼容接口规范,这类网关需支持多模型供应商统一接入、流式响应零拷贝转发及高并发下的强一致性状态管理。Next.js App Router提供声明式路由与自动OpenAPI文档能力,Hono凭借Web标准流处理保障SSE低延迟,PostgreSQL确保价格与权限配置的事务安全,Redis则承担瞬时状态协调。本文聚焦于Claude Code Hub这一生产级开源实现,深入解析

keke1314520的博客 407

linux 路由表功能解析

本文,简单描述一下路由的作用.简单来说,路由器就是一个公交站台,公交站台上面有很多路公交.每条线路公交车又有很多站台(路由器),你就会选择最近的一条公交出行方案,当然啦,站牌上面的路线是会经常更新,更新的事,有当地部门更新.这就是路由.一台电脑主机有路由表,路由器也有路由表,一般来说,一台主机电脑如果只有一个网卡的话,应该会有最少两条路由信息,一条是公网路由,一条是局域网路由(它是不会经过路由器的

yiyeguzhou100的专栏 4106

深入解析VLAN Tag:从帧结构到交换机端口行为与故障排查

在计算机网络中,二层交换技术是构建局域网的基础。传统以太网广播域带来的性能与安全问题,催生了VLAN(虚拟局域网)技术,它通过在数据链路层实现逻辑隔离,优化了网络结构。其核心机制是802.1Q协议定义的VLAN Tag,这是一个插入以太网帧源MAC地址与类型字段之间的4字节标识,包含关键的VLAN ID(VID),用于区分不同的广播域。这项技术的价值在于,它允许网络管理员灵活地在一台物理设备上划分多个逻辑网络,极大地提升了网络的安全性、可管理性和资源利用率。在工程实践中,交换机的Access、Trunk、H

weixin_30655569的博客 419

内网服务器实现共享上网

1.准备工作 主机 IP地址 内网地址 备注 node1 10.0.0.10 172.16.1.10 管理机 node2 10.0.0.11 172.16.1.11 内网机 ##两台服务器都必须添加内网地址(172.16.1.0/24) ##两台主机必须做hosts解析 vim /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 l

HYXRX的博客 2232

【信息科学与工程学】【通信工程】计算机科学与自动化——第二百三十三篇 云NaaS服务 系列二02

字段内容类型​云网络自定义路由表(Custom Route Table):允许用户自定义 VPC 或子网的路由规则,控制流量走向,支持黑白名单、策略路由。端计算节点->边缘计算节点->边缘DC->中心云的网络情况及存储需求及配置情况列表​端计算节点为 VPC 内的云资源。边缘计算节点不适用。边缘 DC 和中心云为路由表管理平台。存储需求:路由条目存储于数据库。网络:路由表在虚拟路由器中执行。QoS:无。网络的端到端配置(从接入到汇聚到核心)​。

weixin_49199313的博客 331

linux iproute2中ip命令man

linux ip 命令 man,linux ip 命令 man

IPv4路由exception缓存

当前设备的接口ens32的ip地址为192.168.1.109,当前的默认路由为192.168.1.1。 # ip address 2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0c:29:a0:c2:ff brd ff:ff:ff:ff:ff:ff inet 192.168.1.109/24 br

redwingz的博客 4020

药物重定位实战:如何用反向找靶技术挖掘老药新用(附Python代码示例)

本文详细介绍了药物重定位中的反向找靶技术,通过分子相似性计算、机器学习模型和结构对接等方法,挖掘已有药物的新治疗潜力。附Python代码示例,帮助读者快速实现从分子结构到潜在靶标的智能预测,显著提升药物研发效率。

weixin_28726671的博客 259

ip命令手册《二》

 摘要 这一部分是关于使用ip命令管理系统路由的内容。 ------------------------------------------------------------------------ -------- By nixe0n 7.路由表管理 7.1.缩写   route、ro、r 7.2.对象   路由条目保存在内核的路由表中,它们包含寻找到其它网络节点的路径

不用此栏 2601

西门子200SMART自定义库开发实战:从PID到露点算法的工业应用

本文详细介绍了西门子200SMART自定义库开发实战,涵盖从PID控制到露点算法的工业应用。通过代码封装技巧、多语言支持和性能优化等高级开发方法,帮助工程师提升PLC编程效率。文章特别强调了自创库在实际项目中的优势,如恒温恒湿控制系统的成功案例,展示了自定义库在工业自动化中的强大应用价值。

lake5的博客 1029

1.全基因组重测序数据分析介绍

二代测序原理及fastq数据解读、全基因组重测序数据分析内容

weixin_53682198的博客 1885

tcp/iP协议族——IP工作原理及实例详解(下)

 IP协议详解 上一篇文章文章主要介绍了IP服务的特点,IPv4头部结构IP分片,并用tcpdump抓取数据包,来观察IP数据报传送过程中IP的格式,以及分片的过程。本文主要介绍IP路由,IP转发,重定向和IPv6头部结构。 IP路由 IP协议的一个核心任务是数据报的路由,即决定发送数据报到目标机器的路径。为了理解IP路由过程,我们先简要分析IP模块的基本流程。 IP模块工作流程...

walkerkalr的专栏 2726

无源定位之时差估计的精确时差估计算法(ETDE)及MATLAB实现程序

时差估计算法之精确时差估计(ETDE)欢迎使用Markdown编辑器新的改变功能快捷键合理的创建标题,有助于目录的生成如何改变文本的样式插入链接与图片如何插入一段漂亮的代码片生成一个适合你的列表创建一个表格设定内容居中、居左、居右SmartyPants创建一个自定义列表如何创建一个注脚注释也是必不可少的KaTeX数学公式新的甘特图功能,丰富你的文章UML 图表FLowchart流程图导出与导入导出导入 欢迎使用Markdown编辑器 你好! 这是你第一次使用 Markdown编辑器 所展示的欢迎页。如果你想

伊谢尔伦的林中小路 4255

(1) ip - Policy-based routing (PBR)

(1) ip - Policy-based routing (PBR)

张同光 (Tongguang Zhang):Hello everyone ! 1209

S7-200 SMART Modbus RTU从站配置与调试实战指南

本文提供了一份详细的S7-200 SMART PLC配置为Modbus RTU从站的实战指南。内容涵盖从硬件基础、软件准备、指令库调用、核心编程到地址映射与调试排错的完整流程。重点解析了MBUS_INIT与MBUS_SLAVE指令的关键参数配置,并深入探讨了Modbus地址与PLC内部V存储区的对应关系,帮助工程师快速打通通讯链路,实现与上位机、触摸屏等主站设备的稳定数据交互。

potato的博客 756

QT编程系列1--QT学习前需知

本周学习了一些QT编程方面的知识,学写了几个程序,这里把记录下来。一方面对前面学习的知识做一个总结,便于以后复习、再学习和应用;另一方面也和大家做个交流,有不足的地方请各位看官多指点。   首先是做一些学习之前的交代:一,学习QT需要哪些基础;二,学习QT有哪些用途,QT较其他的开发工具有哪些特点;三,学习QT的思路。

霜月孤鸟&RTEMS&TinyOS 1117

常用Linux路由命令

第一组命令: ifconfig, ifup, ifdown 1) ifconfig 作用:手动启动、观察与修改网络接口的相关参数,包括IP地址以及MTU大小等。 例1.1:暂时修改IP地址 # ifconfig eth0 192.168.100.100 例1.2:修改IP地址、掩码和MTU # ifconfig eth0 192.168.100.100 netmask 255.255.

sevedk的专栏 1226

67、全球导航卫星系统授时弹性分析与建议

本文分析了全球导航卫星系统(GNSS)在授时过程中面临的问题,包括系统自身异常和外部干扰欺骗,并探讨了提升授时弹性的关键技术与解决方案。文章介绍了美国、欧洲及中国在弹性授时系统建设方面的进展,重点剖析了高精度原子钟、时间同步、干扰检测与识别等核心技术,提出了GNSS与其他授时系统互补的集成化发展路径。最后展望了未来授时系统向更高精度、更强弹性、更广应用的发展趋势,为构建安全可靠的国家授时体系提供参考。

corn8的博客 185

Linux `ip route get 1.1.1.1` 命令解析:快速确认 Internet 流量出口

本文介绍了在Linux多网卡环境中,如何使用ip route get 1.1.1.1命令判断访问Internet的流量出口。通过Ubuntu虚拟机实验环境,说明该命令可显示内核计算的路由结果,包括下一跳网关、出口接口和源IP地址。实验结果显示正确路由应为通过NAT网卡ens37和VMware NAT网关192.168.133.2。文章还澄清了NAT接口概念、为何使用1.1.1.1测试地址,以及该命令与ping的区别,推荐配合使用ip -br addr、ip route和ping进行完整网络检查。

supernealrei的博客 430

Keras中神经网络可视化模块keras.utils.visualize_util安装配置方法

Keras中神经网络可视化模块keras.utils.visualize_util安装配置方法

jacke121的专栏 2759

NTscan扫描工具

ntscan是一个扫描器,可以扫描没有密码和弱密码的共享,先到配置文件中填写猜测的用户名和密码,扫描过程中右侧出现的是扫描日志。

Linux常用命令大全(非常全!!!)

本文整理了Linux系统中最常用的命令大全,涵盖系统信息查看、关机重启操作、文件和目录管理、文件搜索、磁盘空间监控、用户权限设置、文件压缩解压、软件包管理、文本处理、网络配置等各个方面。 主要内容包括:1)系统信息查看命令如arch、uname、lspci等;2)文件和目录操作命令如ls、cd、cp、mv等;3)软件包管理命令如rpm、yum、apt等;4)网络配置命令如ifconfig、route、netstat等;5)文本处理工具如grep、sed、awk等;

ywl470812087的博客 12万+

文档:亲测可用解决vnc灰屏,黑屏,鼠标大黑叉情况

主要解决vnc-viewer灰屏,黑屏,鼠标大黑叉等现象,详细见文档。

LVS负载调度

LVS(Linux Virtual Server)是Linux内核层实现的高性能负载均衡技术,支持NAT、DR、TUN和FULLNAT四种工作模式。NAT模式通过修改目标IP实现转发,但性能受限于调度器;DR模式由RS直接响应客户端,效率更高;TUN模式通过IP隧道实现跨网络调度;FULLNAT同时修改源/目标IP。LVS提供RR、WRR、LC等调度算法,支持会话保持和防火墙标记解决HTTPS轮询问题。关键配置包括VIP设置、ARP抑制、权重调整和持久连接,适用于高并发Web服务集群场景。

pengxiaolin_yi的博客 301

数学建模模型总结

这是本人在两年内准备参加数学建模竞赛搜集到的模型资料,已经经过了本人的筛选和整理,希望能够对准备参加数学建模竞赛的学弟学妹们提供一些帮助!

假人有限元模型

假人模型,车辆碰撞假人有限元模型,适合做乘员安全的研究者利用

制作RootFS

本文介绍了Linux系统中RootFS(根文件系统)的概念及其制作方法。RootFS是内核默认创建的顶层挂载实例,通过initramfs加载最小工具和驱动后,再切换到真正的业务根文件系统。文章详细演示了使用debootstrap工具在Ubuntu/Debian系统中制作ARM架构嵌入式设备的RootFS步骤,包括环境准备、QEMU模拟支持、chroot配置、基础软件安装和打包过程。同时解释了内核启动所需的三个核心文件(内核镜像、initrd和业务RootFS)的作用,并探讨了initrd与initramfs

fanged的专栏 1820

手撕ARM64启动栈(一):QEMU + TF-A → OP-TEE → U-Boot → Linux 全链路总览

ARM 官方提供的参考固件实现,本文用作 BL1/BL2/BL31:开源 TEE 实现,本仓库用作 BL32,运行在 S-EL1,通过 opteed(SPD)与 BL31 交互,提供 TA 运行环境U-Boot:本仓库用作 BL33/Normal World bootloader,通过 ARM semihosting(,非网络/非fw_cfg)从宿主机文件系统读取内核与 initrd,bootm跳转内核。

Fifty的博客 498

渗透测试 ( 3 ) --- Metasploit Framework (MSF)

Metasploit专业版和精简版的主要差别在于专业版上面集成了全自动攻击模块,通过远程API集成网络分割测试模块、标准基线审计向导模块、闭环漏洞验证优先处理功能、动态载荷规避防病毒解决方案、钓鱼意识管理和鱼叉式网络钓鱼模块、对OWASP Top 10漏洞的Web应用程序测试模块、高级命令行和Web界面的选择模块。但是,专业版是必须要付费的,所以除非用到非个人的功能,否则没有必要去使用专业版,而且,专业版和精简版的渗透攻击模块是一样的。.........

freeking101的博客 1万+

AI Agent Runtime:从 Session 事件日志到沙盒即牲畜的架构革命

AI Agent Runtime 是指支撑大模型智能体执行、状态管理与安全隔离的底层运行时环境,其核心原理在于将传统依赖上下文窗口的状态存储解耦为持久化事件日志(Event Log),并以无状态执行器(Harness)驱动按需生成的轻量级沙盒(Sandbox)。这种设计借鉴了云原生与操作系统抽象思想,显著提升可观测性、可调试性与默认安全性。技术价值体现在故障隔离、水平扩展、合规审计与混合云部署能力上;典型应用场景包括金融尽调、销售线索分发、客服自动化等需高可靠性与强治理的B2B服务。本文深入剖析 Anthr

weixin_34226706的博客 443
上一篇: linux man ip-rule
下一篇: iptables -- administration tool for IPv4 packet filtering and NAT
LinuxKernelCiscoIOS
博客等级 码龄11年 35粉丝 101原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值