Solaris

You cannot directly route from a private IP address to a public ip address. You need to use NAT orther proxy mechanism.

Well, actually he can if the next step does that NAT, isn't it?
In fact that request should go throgh the default route... I think a

Code:

traceroute -n 203.162.0.181

would give us more information. Perhaps is another network device who is denying communications.

It is also possible that the ICMP traffic is not allowed...

We' it is possible however traffic is not generally routed to ANY public addres from a private address.

... well, if you are inside a private network, and you ping any website on the internet, you'll get a response, because your NAT knows to act as a gateway when it gets the request.

The problem this user is having, is that the user can't ping addresses both inside and outside the private network from a specific box (I take it) inside the private network.

Now, looking at the netstat output, we need to get better information from the user, because the original post is vague and without knowing the exact setup, it'd be hard to make a diagnose.
All of these NICs are connected to a private network: neither network is publicly routable.
We need to know where this pings are actually being executed and where they are going.
We need confirmation of gateways (I take it the 192.168. networks are flat??)
We do need to see the masks for each interface, so I do agree the output of inconfig -a is needed.
And, confirmation of of the gateway IP.

Incorrect, NAT will only be provided for network adresses for which it is configured, if for example it is configured to provide NAT for 10.0.0.0 it will not automatically do the same for 192.169 addresses.

Some type of NAT/proxying is being done on some network connected to bge0, so far there does not seem to ba a problem, but we don't really care abouot that.

10.0.0.0 10.0.0.6 U 1 1 bge0
default 10.0.0.2 UG 1 2

There are two additional private networks:

192.168.1.0
192.168.100.0

The client in question is on the 192.169.1.0

route add default 192.169.1.113 should allow the required routing to see the 10.0.0.0 network, but I doubt that it will be possible to contact the ISP ip.

I'm really not going to get too much into this, but, duh! ...

Hi,

Here is ouput of the "ifconfig -a":

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.0.0.6 netmask ffffff00 broadcast 10.0.0.255
ether 0:3:ba:60:ac:1b
bge1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 192.168.1.113 netmask ffffff00 broadcast 192.168.1.255
ether 0:3:ba:60:ac:1c
bge2: flags=1100803<UP,BROADCAST,MULTICAST,ROUTER,IPv4> mtu 1500 index 4
inet 192.168.100.113 netmask ffffff00 broadcast 192.168.100.255
ether 0:3:ba:60:ac:1d
#
#

192.168.100.113 and 192.168.1.113 are private IP

Thanks,

Tinh