Shulou(Shulou.com)06/01 Report--

Received a call from the customer, said that the wireless changed the address segment is not good! This is impossible! I communicated with the customer on the phone and learned that the customer modified the original network, replanned the IP address, cancelled the original 192.168 address segment on the WLC, and switched to the 10.120 address segment. After the change, the client connected to the wireless, can get the address from the DHCP, can also PING the gateway, but can not get on the network.

In order to verify that there is no problem with this IP address, the customer delimits a port on the switch to this network segment, connects to the Internet line, obtains the address, opens the web page, and finds that it can surf the Internet unexpectedly! What's going on? Wired access to the address can be online, wireless access to the address can not be connected to the Internet?

Because this project is too early, I don't know where the documents in the later stage of the project have gone, so I can only connect to the user remotely through QQ, log in to the core switch and WLC for troubleshooting, and ask the user which side has been changed. After a search, it is found that there is no problem with the configuration of the core switch and WLC, and the user insists on changing only one network segment and nothing else. What's the problem?

As it is QQ remote, I have no way to see the situation after the wireless connection over there. So I can only negotiate with the user to go to the scene to see the shield the next day.

*

The next day, arrived at the user site, connected to the wireless, it is true to get the address, but the phenomenon is also as the customer said, can not be on the Internet, the web page can not be opened! To the network center, the customer said that at present, there are two exits in the network center. now the Internet is connected to China Unicom, the exit is a soft route made of routerOS, and the other is equivalent to a backup. I logged in to the core switch again and found that the default route did point to routerOS. Could that be the problem?

In order to further verify, I deleted the default route. At this time, all the traffic going out of the core went out the backup port. I ran down the stairs with my laptop and went to the fault site again. I found that it was good to use the backup interface wireless at this time! It works! It seems that the problem lies in routerOS.

After reacting with the customer, the customer asked me to log on to routerOS to check, to be honest, I never touched this thing once. After logging in, I first learned about the interface, which is graphical. From the IP address, to the routing, to the firewall, and then to the arp, I looked at it, and finally found that there seemed to be problems in the IP address and routing configuration. In the IP address, an IP address was configured six times, but the network was still different when it was configured. It is strange that it can still be configured! In addition, in routing, the system generates six directly connected routes according to these six configurations.

According to the configuration of the network equipment, I delete the same IP address, keep only one, and manually point to a static route in the routing configuration. I feel that there should be no problem at this time. Once again, I ran downstairs with my notebook, and before I got into the building, I found that 360 popped up the vulnerability repair page. Hehe. Looks like the wireless is working!

*

At this point, the problem is solved!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.