Next ensure that your router has a arp entry for your servers with the correct mac. To connect the servers to the bridge, we have a switch 3com between them so all servers are on the same port 2 of the bridge. Very strange stuff indeed here Yes, I see all the MAC addresses correectly. Please try again now or at a later time. The whole setup works, the servers receive their IP addresses correctly, they have the Vigor router also correclty in their arp table.
|Date Added:||8 July 2007|
|File Size:||62.27 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Performance is quite nice. Do not post advertisements, offensive materials, profanity, or personal firmwars. This will imply you have very basic networking correctly working.
CentOS 6 with Cisco WET200 (wireless bridge)
Looks as though you have done eet200 the stuff I would have done. This static IP setup is ok for me, but still it would be nice to have an explanation. If you do not have a arp entry then something is blocking it. Sorry, there was a problem flagging this post.
There are wired and wireless systems connected to the Vigor. The only difference I can see to the failed ping is the slightly different data part, and the fact that CentOS seems to set the Id field in the IP header always to 0 no increments and sets the don’t fragment bit. We recently got a Cisco WET bridge firmware 2.
Cisco – wetfirmware Stacks & Vulnerabilities
This would be an indication that the bridge has an issue. Required Question General discussion. Just not the router itself.
This shows that ethernet frames between those addresses can cross the bridge successfully. Qet200 you for helping us maintain CNET’s great community. I tried an additional test and replaced the switch on the side of the servers by a hub so I can at least sniff all traffic on this side of the bridge.
Yes, I see all the MAC addresses correectly. Then I set a filter to see only packets betwen the ethernet addresses of the CentOS server and the router.
Cisco Small Business WET200 – bridge – 802.11b/g – desktop Specs
Possibly some MTU size issue? If you see the mac a packet has to have passed though that port with the source mac set to it. Next I would do the same with a ping packet from the router to the server. Follow Follow this discussion and email me when there are updates Stop following this discussion. Only one thing does not work: I am betting since it works firmwrae the bridge you will see a issue at this disco. If you see the ping get sent back then you at least know that it received the packet and processed it and the packet is getting lost going back.
So I tried to mirror the wired wte200 also wireless port on the Cisco to port 1 and sniffed there.
Unfortunately I can’t sniff directly at the Vigor to see what reaches it, because there is only a wireless connection there. You should see your server send a response to the arp even though you do not see the request in the sniffer It would be nice if you could see the packet coming but at least you eliminate part of the path.
Thanks for any advice, Andy. I think I already tried it earlier without success, but maybe I forgot to remove the systems from the router DHCP list.
Thanks for your help anyway, I hope the “solution” helps others. Promote cracked software, or other illegal content Offensive: The whole setup works, the servers receive their IP addresses correctly, they have the Vigor router also correclty in their arp table. Cancel Preview Submit Follow.