yingfeng
The heart is as bright as a mirror. If you don't, you won't be welcomed

Share an embarrassing case in work

Share an embarrassing case. It's really embarrassing....

This is a real case, which has been adapted for the reasons to be published.

During the first two weeks, two test devices were put on the shelves in a hospital: one firewall and one Internet behavior management.
The customer's network is a 10M dedicated line, and the firewall is deployed at the exit as a gateway.
Downlink behavior management, transparent deployment of bridge mode, and setting a bridge IP for management.

The topology is as follows (too lazy to draw)

 

Public network

|

|

firewall

|

|

Behavior management

|

|

Switch

|

|

Intranet PC

 

When setting the behavior management IP, the customer said: xx. xx. xx. 120-139, choose an IP at random.
Then I chose one randomly and set xx. xx. xx. 125.

After the strategy is set, it is put on the shelf, the network connection is normal, and after the handover is completed, go home for dinner.
After a period of time, the customer reported that the network that deployed our firewall could not access their OA system (their OA system server had two network cards, two IPs, two networks), but it was no problem to access from their other network
I am confused. The LAN traffic goes directly to the switch without going through the gateway. In other words, the traffic does not go through our behavior management and firewall. How can it be related to us???

Muddleheaded....


Because I arranged my colleagues to deal with it during my compensatory leave, they were not free and could not handle it remotely.

Until today, I finally went to check this problem.

Me: What is the IP address of your OA system?
Customer: xx.xx.xx.125
Me: I'm a little familiar with the IP...
Take out the notebook from the package, connect it to the switch, and input the IP address...
Automatically jump to https ⊙ ﹏ ⊙‖ to enter the behavior management web console ( ̄ _  ̄ | | |)
I:........

Then the address of the behavior management bridge was changed and returned to normal.

It suddenly reminds me of a sentence from Nanling Dada (thousands of developers listening quietly and quickly): "Focus is the most important thing, and details are the most important thing"

This article is published at: yingfeng Blog >> Share an embarrassing case in work , please indicate the source for reprinting.

comment ten

  • Nickname (required)
  • Email (required)
  • website
  1. #0

    Any ip, the root of 233 evil

    Feng Xiaoxian Six years ago (2018-10-18) reply
    • This is a big hole, which is easy to step on. The DHCP environment has a fixed IP. The fixed IP is not powered on, and other devices are occupied by DHCP. Then the PC with a fixed IP is powered on, emmmm

      yingfeng Six years ago (2018-10-18) reply
  2. #0

    I had a problem before. The light sequence of a brand of line measuring instrument was reversed. I didn't know at that time. All the 100 megabit lines were 3678 lines, which almost led to a big mistake at that time

    Flute sound Six years ago (2018-02-06) reply
    • This kind of line measuring instrument should be lost. It will be misled sooner or later 🌚

      yingfeng Six years ago (2018-02-06) reply
    • What brand

      yfresh Three years ago (2021-10-28) reply
  3. #0

    You will be embarrassed.. Your idea at that time was the same as that of the router... It seems that you have built a space-time tunnel

    Germinal core Seven years ago (2017-10-27) reply
    • It's really embarrassing. This kind of detail is wrong...

      yingfeng Seven years ago (2017-11-11) reply
  4. #0

    Come and have a look, friend

    running Seven years ago (2017-09-28) reply
    • To listen to because of blowing

      yingfeng Seven years ago (2017-10-16) reply