Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[oocyte]

Update: Issue was with DNS Relay.  Turned it off, all is well.

Cheers =)


I have DIR 655 servicing 192.168.0.1/24.

I'm pulling my hair trying to get this fixed  , would anyone have any pointers on what I should be looking for?  Any help is appreciated.

So the problem.  I have a couple of hosts:
192.168.0.5 - main machine - windows vista
192.168.0.7 - laptop - wireless - windows xp
192.168.0.25 - vmware server - solaris 10
192.168.0.40 - vmware server - rhel 5

Pinging from .5
.7 reachable, .25 and 40 unreachable.

Pinging from .7
.5, .25 and .40 all reachable

Pinging from .25
.7 and .40 reachable, .5 unreachable

Pinging from .40
.7 and .25 reachable, .5 unreachable

However, if I configure the router to Port Forward WAN connection on .25 port 22, I can ssh from .5 to .25 (via WAN IP).





Some Router Settings:
Firmware 1.32NA
WAN = Static IP from modem
DMZ is off
QOS is off
Firewall - SPI Enabled, NAT - UDP Address Restricted, TCP Port/Address Restricted
AntiSpoofing Off
WAN Ping is off
SecureSpot is off
Guest Zone is off
Advanced DNS is off

[basementjack]

are solaris and rhel vms on your esx box? if so what is the IP of the esx box and is that pingable by 5 and 7?

it almost looks as if .5 is your main machine, and you have your vm network setup not to talk to the host.
that would explain to two way blockage between 5 and 25/40.

If that's the case, I would have a look at how your VM network is setup.

the reason it works with the port forward is that you're going 'outside the box' (.5) and sending traffic to the router, which forwards it back in -


hope that helps

[oocyte]

Thanks basementjack.  Yeah, .5 is VM Host.  All machines used to be able to ping each other prior to me fudging with the router.

I didn't suspect this is a VM Network problem because the only change I have made was on my router, but now that you mentioned it, I did a quick test by connecting another physical machine, and it turns out the communication is only broken between VMware host and VMware guests.  I'll take this matter to VMware forums.

However, since the only change I made was to the router, I don't really understand what could have happened with VMware.  To sum it up, I made the following changes:

1. Previously, I had my router talk to the radius server getting the public IP assigned via DHCP directly.
2. I changed that setting by letting the DSL modem register the IP with my DSL Provider.
3. DSL modem (192.168.1.254) acts as a gateway between Internet and DIR 655 (192.168.1.64)
4. DIR 655 is now acting as a router/gateway to 192.168.0.x network
5. All internet traffic is routed to 192.168.1.254 by the router.

My vmnet is on a bridged interface (the primary interface on 192.168.0.5).

Thanks!