Weird routing problems

[SSSnail]

http://img374.imageshack.us/img374/5334/routeya4.png

Looking at the image, you'll see the interface highlighted, and I can't delete the route for some reasons. I can't access the web if just going by wireless, and another weird thing is that the gateway of the wire connection will sometimes do the same.

How do I fix it? What do I need to do?

Thanks.

 

[Qacer]

The IP address that you highlighted is a special type of IP address for limited broadcast. When a packet is sent to this address, it will be sent to all devices in the LAN only. I'm not sure what Interface 10006 and 3 refer. It could be related to some network management tool... just my guess.

You also mentioned that you can't get on the "web if just going by wireless." On your route table, I see that the routing protocol prefers sending other IP packets to 192.168.150.1. What is associated with this IP address? It may be possible that any IP packets sent to 192.168.150.1 just goes to a black hole (i.e. this device may not know where to route the packets).

 

[mcmilljb]

Wow. Are you running some multicast applications/virtual machines? I'm betting 192.168.1.1 is your router's ip address. I guess it goes by the lowest metric. In the top example, you have 192.168.150.1 as the lowest metric with 20 which is getting preferred over the 192.168.1.1. It seems also that 192.168.150.1 is an ip address assigned to an interface because in line to it lists it as a gateway and interface. In the bottom example, It's using 192.168.105 as your source interface and 192.168.1.1 as the gateway since it has a lower metric and probably getting binded first since it has the lower ip address. I would try to figure out what the hell the 192.168.150.1 interface is coming from.

Hmmm. I take some of that back. I just looked at my routing table, and I have some of those same routes. I don't remember XP listening for 224.0.0.0 by default. But yeah, your main problem is that 192.168.150.1 Gateway. Get that out of there. You can't hit 192.168.150.1 from 192.168.1.100 or 192.168.1.105 plus it says your gateway is also an interface 😕

 

[SSSnail]

Well, I never had this problems before. I have VMWare on my machine and the 192.168.150.1 is VMNet8 (NAT), and 192.168.1.1 is VMNet1 (Host only), I changed VMNet1 to 192.168.5.1 now and somehow, it fixed itself even though the routing table still shows the same. I THINK I know where the problem lies, because my router's IP is also 192.168.1.1.

The weird thing about all this is that I can't delete or edit any of the routes. To answer Qacer, when I had VMNet1 at 192.168.1.1, it would assign IPs to the physical and wireless connection, that has never happened before. I guess I need to sniff all this stuffs to see what the hell is going on.

I'll just change the default IP of the router, that should fix everything.