LinuxQuestions.org - Solaris 10 Install cannot connect to Internet

- Solaris / OpenSolaris (https://www.linuxquestions.org/questions/solaris-opensolaris-20/)

- - Solaris 10 Install cannot connect to Internet (https://www.linuxquestions.org/questions/solaris-opensolaris-20/solaris-10-install-cannot-connect-to-internet-4175512498/)

Solaris 10 Install cannot connect to Internet

Hello everyone,

I am experiencing a technical problem that I cannot resolve with the available threads or by internet searches. This is the first time I've installed Solaris 10 on my ultra45 and I'm having an internet connectivity issue.

I'm connected to a DLINK DSL-G604T modem/router and can ping addresses both external and local addresses including the gateway and DNS but I cannot connect to the internet via the browser.

Code:

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

        inet 127.0.0.1 netmask ff000000

bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

        inet 10.1.1.245 netmask ffffff00 broadcast 10.1.1.255

        ether 0:14:4f:f:e4:b0

Code:

# cat /etc/resolv.conf

nameserver 10.1.1.1

nameserver 4.2.2.2

nameserver 8.8.8.8

Code:

# cat /etc/defaultrouter

10.1.1.1

bash-3.00#

Code:

# cat /etc/nodename

HALO

bash-3.00#

Code:

# cat /etc/inet/netmasks

#

# The netmasks file associates Internet Protocol (IP) address

# masks with IP network numbers.

#

#      network-number  netmask

#

# The term network-number refers to a number obtained from the Internet Network

# Information Center.

#

# Both the network-number and the netmasks are specified in

# "decimal dot" notation, e.g:

#

#              128.32.0.0 255.255.255.0

#

10.1.1.0    255.255.255.0

Code:

bash-3.00# ping 10.1.1.1

10.1.1.1 is alive

bash-3.00# ping 4.2.2.2

4.2.2.2 is alive

bash-3.00# nslookup google.com

Server:        4.2.2.2

Address:        4.2.2.2#53



Non-authoritative answer:

Name:  google.com

Address: 74.125.239.100

Name:  google.com

Address: 74.125.239.98

Name:  google.com

Address: 74.125.239.102

Name:  google.com

Address: 74.125.239.96

Oddly, I can ping google.com according to

Code:

bash-3.00# ping google.com

google.com is alive

However,

Code:

bash-3.00# ping www.google.com

ping: unknown host www.google.com

Lasty, I've copied nsswitch.dns to nsswitch.conf where

Code:

hosts: files dns

Certainly a perplexing problem that I'm struggling to resolve. Any help I'd be really appreciative.

It doesn't look like a Solaris issue but a DNS one.

Is www.google.com resolved by the DNS service ?

Thanks for the prompt response.

Yes, www.google.com is resolved by the DNS service assigned to 10.1.1.1 (Modem/router).

Code:

bash-3.00# nslookup www.google.com

Server:        10.1.1.1

Address:        10.1.1.1#53



Non-authoritative answer:

Name:  google.com

Address: 74.125.239.176

Name:  google.com

Address: 74.125.239.177

Name:  google.com

Address: 74.125.239.178

Name:  google.com

Address: 74.125.239.179

To add further confusion, every time I run a secession of the Mozilla or Firefox Web browser the connection now times out on some addresses (e.g. www.google.com, www.gmail.com or www.gizmodo.com.au) while others are fine.

What says "getent hosts www.google.com" and "ifconfig -a" ?

It might be an IPv6 routing issue so you might want to disable the IPv6 interface to see if it fix the issue.

Regarding the previous querry,

Code:

bash-3.00# getent hosts www.google.com

74.125.239.212 www.google.com

74.125.239.208 www.google.com

74.125.239.209 www.google.com

74.125.239.210 www.google.com

Code:

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

        inet 127.0.0.1 netmask ff000000

bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

        inet 10.1.1.245 netmask ffffff00 broadcast 10.1.1.255

        ether 0:14:4f:f:e4:b0

How do I identify if IPv6 is enabled? I'm positive IPv4 interface is the only one selected and thus active.

Try removing 10.1.1.1 from /etc/resolv.conf which return a bogus reply.

I can't believe it, the browser is actually now able to resolve addresses with ease. Legendary, thank you!

Code:

# cat /etc/resolv.conf

nameserver 4.2.2.2

nameserver 8.8.8.8

The question now is why? Would this likely be a modem/router issue?

The DNS service returned a bogus reply. If it is implemented by the modem/router, that's indeed where to investigate. You should also look to your ISP DNS, assuming this is where your router takes its information from.

I did a little more investigating and came across an interesting thread that mentioned for Solaris 10 and older distributions may require the MTU/MSS interface to be reconfigured for a smaller value.

I wanted to see if my local gateway/DNS (modem/router) 10.1.1.1 was at fault. So I returned to the original resolv.conf and tried the following script

Code:

ping -s 203.173.50.151 1492

^C

PING 203.173.50.151: 1492 data bytes

----203.173.50.151 PING Statistics----

3 packets transmitted, 0 packets received, 100% packet loss

Then I decreased the data packet size until the following result

Code:

ping -s 203.173.50.151 1464

^C

PING 203.173.50.151: 1464 data bytes

1472 bytes from www.iinet.net.au (203.173.50.151): icmp_seq=0. time=30.6 ms

1472 bytes from www.iinet.net.au (203.173.50.151): icmp_seq=1. time=29.5 ms

1472 bytes from www.iinet.net.au (203.173.50.151): icmp_seq=2. time=29.4 ms

----203.173.50.151 PING Statistics----

3 packets transmitted, 3 packets received, 0% packet loss

round-trip (ms)  min/avg/max/stddev = 29.4/29.8/30.6/0.65

Given my modem/router has the below config could this be also a connecting reason or must sun systems with solaris 10 require an MTU of 1464 data bytes?

Code:

Dlink Router

MTU: 1400 bytes

MTU: 1492 bytes