• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 漏洞说明
  • 全部
  • 全部
  • 大数据引擎
  • 知了引擎
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式
高级搜索

ssh无法连接

1天前提问
  • 0关注
  • 0收藏,52浏览
粉丝:0人 关注:0人

问题描述:

华三S5560交换机 version 7.1.070, Release 6126P13

本地局域网连接正常,总部无法连接

设备debug日志

 

The current terminal is enabled to display debugging logs.

*Aug 14 10:40:22:952 2026 zbl SSHS/7/MESSAGE: Received packet type 94.

<zbl>*Aug 14 10:40:32:436 2026 zbl SSHS/7/EVENT: Connection from 10.106.7.79 port 57273

*Aug 14 10:40:32:440 2026 zbl SSHS/7/EVENT: Client protocol version 2.0, client software version SecureCRT_7.1.1 (build 264) SecureCRT

*Aug 14 10:40:32:440 2026 zbl SSHS/7/EVENT: Start new child 480673.

*Aug 14 10:40:32:441 2026 zbl SSHS/7/EVENT: Enabling compatibility mode for protocol 2.0

*Aug 14 10:40:32:441 2026 zbl SSHS/7/EVENT: Local version string SSH-2.0-Comware-7.1.070

*Aug 14 10:40:32:441 2026 zbl SSHS/7/EVENT: Pki-domain-name is not configure.

*Aug 14 10:40:32:442 2026 zbl SSHS/7/EVENT: Pki-domain-name is not configure.

*Aug 14 10:40:32:447 2026 zbl SSHS/7/EVENT: Hostkey string is : ssh-rsa,ssh-dss

*Aug 14 10:40:32:448 2026 zbl SSHS/7/MESSAGE: Prepare packet[20].

*Aug 14 10:40:32:449 2026 zbl SSHS/7/MESSAGE: Received packet type 20.

*Aug 14 10:40:32:449 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_KEXINIT.

*Aug 14 10:40:32:450 2026 zbl SSHS/7/EVENT: My proposal kex:

*Aug 14 10:40:32:450 2026 zbl SSHS/7/EVENT: Kex strings(0): ecdh-sha2-nistp256,ecdh-sha2-nistp384,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

*Aug 14 10:40:32:450 2026 zbl SSHS/7/EVENT: Kex strings(1): ssh-rsa,ssh-dss

*Aug 14 10:40:32:451 2026 zbl SSHS/7/EVENT: Kex strings(2): aes128-ctr,aes192-ctr,aes256-ctr,AEAD_AES_128_GCM,AEAD_AES_256_GCM,aes128-cbc,3des-cbc,aes256-cbc,des-cbc

*Aug 14 10:40:32:451 2026 zbl SSHS/7/EVENT: Kex strings(3): aes128-ctr,aes192-ctr,aes256-ctr,AEAD_AES_128_GCM,AEAD_AES_256_GCM,aes128-cbc,3des-cbc,aes256-cbc,des-cbc

*Aug 14 10:40:32:451 2026 zbl SSHS/7/EVENT: Kex strings(4): hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96

*Aug 14 10:40:32:451 2026 zbl SSHS/7/EVENT: Kex strings(5): hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96

*Aug 14 10:40:32:452 2026 zbl SSHS/7/EVENT: Kex strings(6): none,zlib,zlib@openssh.com

*Aug 14 10:40:32:452 2026 zbl SSHS/7/EVENT: Kex strings(7): none,zlib,zlib@openssh.com

*Aug 14 10:40:32:452 2026 zbl SSHS/7/EVENT: Kex strings(8): 

*Aug 14 10:40:32:452 2026 zbl SSHS/7/EVENT: Kex strings(9): 

*Aug 14 10:40:32:453 2026 zbl SSHS/7/EVENT: Peer proposal kex:

*Aug 14 10:40:32:453 2026 zbl SSHS/7/EVENT: Kex strings(0): diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1

*Aug 14 10:40:32:453 2026 zbl SSHS/7/EVENT: Kex strings(1): ssh-dss,ssh-rsa,x509v3-sign-rsa,x509v3-sign-dss

*Aug 14 10:40:32:453 2026 zbl SSHS/7/EVENT: Kex strings(2): aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,twofish-cbc,blowfish-cbc,3des-cbc,arcfour

*Aug 14 10:40:32:454 2026 zbl SSHS/7/EVENT: Kex strings(3): aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,twofish-cbc,blowfish-cbc,3des-cbc,arcfour

*Aug 14 10:40:32:454 2026 zbl SSHS/7/EVENT: Kex strings(4): hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,umac-64@openssh.com

*Aug 14 10:40:32:455 2026 zbl SSHS/7/EVENT: Kex strings(5): hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,umac-64@openssh.com

*Aug 14 10:40:32:455 2026 zbl SSHS/7/EVENT: Kex strings(6): none

*Aug 14 10:40:32:456 2026 zbl SSHS/7/EVENT: Kex strings(7): none

*Aug 14 10:40:32:456 2026 zbl SSHS/7/EVENT: Kex strings(8): 

*Aug 14 10:40:32:456 2026 zbl SSHS/7/EVENT: Kex strings(9): 

*Aug 14 10:40:32:457 2026 zbl SSHS/7/EVENT: Kex: client->server, Encrypt: aes256-ctr, HMAC: hmac-sha1, Compress: none

*Aug 14 10:40:32:457 2026 zbl SSHS/7/EVENT: Kex: server->client, Encrypt: aes256-ctr, HMAC: hmac-sha1, Compress: none

*Aug 14 10:40:32:594 2026 zbl SSHS/7/EVENT: Expecting packet type 30.

*Aug 14 10:40:32:595 2026 zbl SSHS/7/MESSAGE: Received packet type 30.

*Aug 14 10:40:32:682 2026 zbl SSHS/7/MESSAGE: Prepare packet[31].

*Aug 14 10:40:32:683 2026 zbl SSHS/7/MESSAGE: Prepare packet[21].

*Aug 14 10:40:32:683 2026 zbl SSHS/7/EVENT: Set new keys: mode=1

*Aug 14 10:40:32:684 2026 zbl SSHS/7/EVENT: Expecting packet type 21.

*Aug 14 10:40:32:701 2026 zbl SSHS/7/EVENT: Set new keys: mode=0

*Aug 14 10:40:32:701 2026 zbl SSHS/7/MESSAGE: Received packet type 21.

*Aug 14 10:40:32:701 2026 zbl SSHS/7/EVENT: KEX done.

*Aug 14 10:40:32:702 2026 zbl SSHS/7/MESSAGE: Received packet type 5.

*Aug 14 10:40:32:702 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_SERVICE_REQUEST.

*Aug 14 10:40:32:703 2026 zbl SSHS/7/MESSAGE: Prepare packet[6].

*Aug 14 10:40:32:705 2026 zbl SSHS/7/MESSAGE: Received packet type 50.

*Aug 14 10:40:32:706 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_USERAUTH_REQUEST.

*Aug 14 10:40:32:706 2026 zbl SSHS/7/EVENT: Username: xfzjwd, service: ssh-connection, method: none

*Aug 14 10:40:32:707 2026 zbl SSHS/7/EVENT: PAM: initializing for "xfzjwd", service:login, domain:

*Aug 14 10:40:33:043 2026 zbl SSHS/7/EVENT: Try authentication method none.

*Aug 14 10:40:33:043 2026 zbl SSHS/7/EVENT: Failed none for xfzjwd from 10.106.7.79 port 57273.

 

*Aug 14 10:40:33:044 2026 zbl SSHS/7/EVENT: Get authentication methods: password

*Aug 14 10:40:33:044 2026 zbl SSHS/7/MESSAGE: Prepare packet[51].

*Aug 14 10:40:33:049 2026 zbl SSHS/7/MESSAGE: Received packet type 50.

*Aug 14 10:40:33:049 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_USERAUTH_REQUEST.

*Aug 14 10:40:33:050 2026 zbl SSHS/7/EVENT: Username: xfzjwd, service: ssh-connection, method: password

*Aug 14 10:40:33:050 2026 zbl SSHS/7/EVENT: Try authentication method password.

*Aug 14 10:40:33:050 2026 zbl SSHS/7/EVENT: Password authentication and authorization.

*Aug 14 10:40:33:088 2026 zbl SSHS/7/EVENT: PAM: Get work directory flash:.

*Aug 14 10:40:33:089 2026 zbl SSHS/7/EVENT: PAM: Get role list network-admin,network-operator.

*Aug 14 10:40:33:089 2026 zbl SSHS/7/EVENT: PAM: password authentication accepted for xfzjwd.

*Aug 14 10:40:33:089 2026 zbl SSHS/7/EVENT: PAM: accounting.

*Aug 14 10:40:33:091 2026 zbl SSHS/7/EVENT: PAM: account management : 0 (success)

%Aug 14 10:40:33:091 2026 zbl SSHS/6/SSHS_LOG: Accepted password for xfzjwd from 10.106.7.79 port 57273.

 

*Aug 14 10:40:33:091 2026 zbl SSHS/7/MESSAGE: Prepare packet[52].

*Aug 14 10:40:33:092 2026 zbl SSHS/7/EVENT: Entering interactive session for SSH2.

*Aug 14 10:40:33:093 2026 zbl SSHS/7/EVENT: Initiate server message dispatch, compatibility:1/0 

*Aug 14 10:40:33:113 2026 zbl SSHS/7/MESSAGE: Received packet type 90.

*Aug 14 10:40:33:114 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_OPEN: ctype session, rchan 0, win 131072, max 32768

*Aug 14 10:40:33:117 2026 zbl SSHS/7/EVENT: Received session request.

*Aug 14 10:40:33:117 2026 zbl SSHS/7/EVENT: Channel 0: new [server-session]

*Aug 14 10:40:33:117 2026 zbl SSHS/7/EVENT: Session id 0 unused.

*Aug 14 10:40:33:119 2026 zbl SSHS/7/EVENT: Session opened: session 0, link with channel 0

*Aug 14 10:40:33:119 2026 zbl SSHS/7/MESSAGE: Prepare packet[91].

*Aug 14 10:40:33:130 2026 zbl SSHS/7/MESSAGE: Received packet type 98.

*Aug 14 10:40:33:130 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_REQUEST: channel 0, request pty-req, reply 1

*Aug 14 10:40:33:130 2026 zbl SSHS/7/EVENT: Channel request: user xfzjwd, service type 1 rtype:pty-req

*Aug 14 10:40:33:152 2026 zbl SSHS/7/EVENT: Open pty: pseudo-terminal-master(35), pseudo-terminal-sub(34)

*Aug 14 10:40:33:154 2026 zbl SSHS/7/MESSAGE: Prepare packet[99].

*Aug 14 10:40:33:178 2026 zbl SSHS/7/MESSAGE: Received packet type 98.

*Aug 14 10:40:33:178 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_REQUEST: channel 0, request shell, reply 1

*Aug 14 10:40:33:179 2026 zbl SSHS/7/EVENT: Channel request: user xfzjwd, service type 1 rtype:shell

*Aug 14 10:40:33:192 2026 zbl SSHS/7/EVENT: Channel 0: read_fd 37 is a TTY.

*Aug 14 10:40:33:192 2026 zbl SSHS/7/MESSAGE: Prepare packet[93].

*Aug 14 10:40:33:199 2026 zbl SSHS/7/MESSAGE: Prepare packet[99].

*Aug 14 10:40:33:418 2026 zbl SSHS/7/ERROR: Read error from remote host 10.106.7.79: Connection reset by peer

%Aug 14 10:40:33:419 2026 zbl SSHS/6/SSHS_DISCONNECT: SSH user xfzjwd (IP: 10.106.7.79) disconnected from the server.

*Aug 14 10:40:33:419 2026 zbl SSHS/7/EVENT: PAM: cleanup

*Aug 14 10:40:33:430 2026 zbl SSHS/7/EVENT: Close pty: pseudo-terminal-master(-1), pseudo-terminal-sub(34)

*Aug 14 10:40:54:910 2026 zbl SSHS/7/EVENT: Connection from 10.106.7.79 port 57289

*Aug 14 10:40:54:914 2026 zbl SSHS/7/EVENT: Start new child 480676.

*Aug 14 10:40:55:037 2026 zbl SSHS/7/EVENT: Client protocol version 2.0, client software version OpenSSH_10.2

*Aug 14 10:40:55:037 2026 zbl SSHS/7/EVENT: Enabling compatibility mode for protocol 2.0

*Aug 14 10:40:55:037 2026 zbl SSHS/7/EVENT: Local version string SSH-2.0-Comware-7.1.070

*Aug 14 10:40:55:038 2026 zbl SSHS/7/EVENT: Pki-domain-name is not configure.

*Aug 14 10:40:55:038 2026 zbl SSHS/7/EVENT: Pki-domain-name is not configure.

*Aug 14 10:40:55:043 2026 zbl SSHS/7/EVENT: Hostkey string is : ssh-rsa,ssh-dss

*Aug 14 10:40:55:044 2026 zbl SSHS/7/MESSAGE: Prepare packet[20].

*Aug 14 10:40:55:051 2026 zbl SSHS/7/MESSAGE: Received packet type 20.

*Aug 14 10:40:55:052 2026 zbl SSHS/7/EVENT: Received SSH2_MSG_KEXINIT.

*Aug 14 10:40:55:052 2026 zbl SSHS/7/EVENT: My proposal kex:

*Aug 14 10:40:55:052 2026 zbl SSHS/7/EVENT: Kex strings(0): ecdh-sha2-nistp256,ecdh-sha2-nistp384,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

*Aug 14 10:40:55:053 2026 zbl SSHS/7/EVENT: Kex strings(1): ssh-rsa,ssh-dss

*Aug 14 10:40:55:053 2026 zbl SSHS/7/EVENT: Kex strings(2): aes128-ctr,aes192-ctr,aes256-ctr,AEAD_AES_128_GCM,AEAD_AES_256_GCM,aes128-cbc,3des-cbc,aes256-cbc,des-cbc

*Aug 14 10:40:55:054 2026 zbl SSHS/7/EVENT: Kex strings(3): aes128-ctr,aes192-ctr,aes256-ctr,AEAD_AES_128_GCM,AEAD_AES_256_GCM,aes128-cbc,3des-cbc,aes256-cbc,des-cbc

*Aug 14 10:40:55:054 2026 zbl SSHS/7/EVENT: Kex strings(4): hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96

*Aug 14 10:40:55:054 2026 zbl SSHS/7/EVENT: Kex strings(5): hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96

*Aug 14 10:40:55:054 2026 zbl SSHS/7/EVENT: Kex strings(6): none,zlib,zlib@openssh.com

*Aug 14 10:40:55:055 2026 zbl SSHS/7/EVENT: Kex strings(7): none,zlib,zlib@openssh.com

*Aug 14 10:40:55:055 2026 zbl SSHS/7/EVENT: Kex strings(8): 

*Aug 14 10:40:55:055 2026 zbl SSHS/7/EVENT: Kex strings(9): 

*Aug 14 10:40:55:055 2026 zbl SSHS/7/EVENT: Peer proposal kex:

*Aug 14 10:40:55:056 2026 zbl SSHS/7/EVENT: Kex strings(0): mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@***.***,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com

*Aug 14 10:40:55:056 2026 zbl SSHS/7/EVENT: Kex strings(1): rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com

*Aug 14 10:40:55:056 2026 zbl SSHS/7/EVENT: Kex strings(2): chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr

*Aug 14 10:40:55:056 2026 zbl SSHS/7/EVENT: Kex strings(3): chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr

*Aug 14 10:40:55:057 2026 zbl SSHS/7/EVENT: Kex strings(4): umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1

*Aug 14 10:40:55:057 2026 zbl SSHS/7/EVENT: Kex strings(5): umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1

*Aug 14 10:40:55:057 2026 zbl SSHS/7/EVENT: Kex strings(6): zlib@openssh.com,none

*Aug 14 10:40:55:057 2026 zbl SSHS/7/EVENT: Kex strings(7): zlib@openssh.com,none

*Aug 14 10:40:55:058 2026 zbl SSHS/7/EVENT: Kex strings(8): 

*Aug 14 10:40:55:058 2026 zbl SSHS/7/EVENT: Kex strings(9): 

*Aug 14 10:40:55:058 2026 zbl SSHS/7/EVENT: Kex: client->server, Encrypt: aes128-ctr, HMAC: hmac-sha2-256, Compress: zlib@openssh.com

*Aug 14 10:40:55:059 2026 zbl SSHS/7/EVENT: Kex: server->client, Encrypt: aes128-ctr, HMAC: hmac-sha2-256, Compress: zlib@openssh.com

%Aug 14 10:40:55:059 2026 zbl SSHS/6/SSHS_ALGORITHM_MISMATCH: SSH client 10.106.7.79 failed to log in because of public key mismatch.

*Aug 14 10:40:55:060 2026 zbl SSHS/7/ERROR: No host_key algorithm

%Aug 14 10:40:55:060 2026 zbl SSHS/6/SSHS_DISCONNECT: SSH user (null) (IP: 10.106.7.79) disconnected from the server.

 

 

2 个回答
粉丝:9人 关注:6人

换个软件试试呢  本地正常的话  配置是没问题的  

mobaxterm和SecureCRT都不行

zhiliao_NsRq63 发表时间:1天前 更多>>

mobaxterm和SecureCRT都不行

zhiliao_NsRq63 发表时间:1天前
粉丝:14人 关注:9人

排查步骤及关键命令
1. 基础连通性验证
总部终端ping交换机管理地址,确认无丢包、延迟正常;同时检查中间网络(防火墙/路由器)是否放通TCP 22端口,可在交换机侧抓包或查看会话:

display tcp status | include 22

2. SSH服务与配置检查
确认SSH服务已启用、VTY线路支持SSH协议:

display current-configuration | include ssh server enable
display line vty

若未启用则配置:

system-view
ssh server enable
line vty 0 63
protocol inbound ssh

3. 用户与认证排查
确认SSH用户存在、认证方式正确(password/publickey)、服务类型为ssh:

display ssh user-information
display local-user

缺失则配置(以password认证为例):

local-user admin class manage
password simple xxx
service-type ssh
authorization-attribute user-role network-admin
ssh user admin service-type stelnet authentication-type password

4. 版本兼容排查
日志显示客户端为SecureCRT 7.1.1,旧版本可能与交换机SSH密钥交换算法不兼容。可在交换机放宽算法配置:

ssh server key-exchange algorithm dh-group14-sha1 dh-group1-sha1
ssh server encryption-algorithm aes128-cbc 3des-cbc

5. 路由与源地址检查
确认交换机到总部10.106.7.79的回程路由可达:

display ip routing-table 10.106.7.79

若SSH绑定了源接口/地址,需确认总部访问的是绑定地址:

display current-configuration | include ssh server source

编辑答案

你正在编辑答案

如果你要对问题或其他回答进行点评或询问,请使用评论功能。

分享扩散:

提出建议

    +

亲~登录后才可以操作哦!

确定

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作

举报

×

侵犯我的权益 >
对根叔社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 pub.zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明