I also would change rules 20 and 21 such that it's SOURCE port 22, and
not destination port 22. This would apply if you are trying to permit
inbound ssh requests from those specific hosts.
John
Robyn Orosz wrote:
Hi Alain,
Take a look at this post:
Greg,
From your description, the router appears to be performing its job
properly. You shouldn't need to perform any additional configuration
changes.
I suggest focusing on the host's configuration. What does route -an
appear like? Also, arp -a should yield a MAC address for 10.3.231.1 that
GW,
If you're trying to access the web server from the 192.168.1.x network,
your client's browser should simply point to http://192.168.1.244. It
should not point to the 192.168.10.45:81 location because the traffic
never reaches the router.
John
Go Wow wrote:
Yeah I can view my inside
on the wan interface
to allow everything to go out. Is there a simple rule for this?
Thanks,
Nate
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
--
John Gong
Nathan,
You're halfway there. With NAT, you need to build a second rule so that
the reply packets get NAT'ed as well. At this time, the web server is
likely sending replies to your client, but the client doesn't know why
packets from 192.168.1.77 are hitting it :-).
You'll want to make a
,
John Gong, Systems Engineer
Vyatta
Daren Tay wrote:
Hi guys,
pardon me for these continuous stew of questions...
but for a virtualized environment.. the idea is to install the Virtualizer
(VMware, XEN) first, then the Linux/Vyatta OS itself?
It seats below the kernel?
Or do I need
