I'm running snv_134, for the most part straight out of the box, on a small home 
LAN. The global zone is fine and is having no issues at all, but the networking 
does not work properly in any non-global zone that I create. Maybe I'm doing it 
wrong?

Here are some of the symptoms of the weirdness:

- Domain lookups are all unsuccessful. For example, outgoing pings to a domain 
name fail immediately with: "ping: unknown host <hostname>"
- Outgoing pings to an IP address take a few "tries" to go through. The first 
few pings are unsuccessful, but are followed by successful pings. ping reports 
the failed pings as packet loss.
- Incoming pings from another client on the LAN behave the same way.
- Incoming pings from the global zone work fine.
- traceroutes from within the zone (to an IP address) take forever with the 
three asterisks on each line. Traceroutes to a hostname fail with "unknown 
host."
- The global zone, as well as all other clients on the LAN work fine.

10.2.4.1: Router (Linksys WRT54GL)
10.2.4.10: Global zone (sol)
10.2.4.11: Non-global zone (h)

----------

al...@sol:~# ifconfig -a (from global zone)
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        inet 127.0.0.1 netmask ff000000 
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        zone h
        inet 127.0.0.1 netmask ff000000 
e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 
2
        inet 10.2.4.10 netmask ffffff00 broadcast 10.2.4.255
        ether 0:1b:21:2d:e7:66 
e1000g0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        zone h
        inet 10.2.4.11 netmask ffffff00 broadcast 10.2.4.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 
index 1
        inet6 ::1/128 
lo0:1: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 
index 1
        zone h
        inet6 ::1/128 
e1000g0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
        inet6 fe80::21b:21ff:fe2d:e766/10 
        ether 0:1b:21:2d:e7:66 

----------

/etc/resolv.conf is the same in the global and non-global zone:

domain mydomain
nameserver 10.2.4.1

I'm using the default /etc/nsswitch.dns as my /etc/nsswitch.conf in both the 
global and non-global zone.

----------

Zone config:

al...@sol:~# zonecfg -z h
zonecfg:h> info
zonename: h
zonepath: /zones/h
brand: ipkg
autoboot: true
bootargs: 
pool: 
limitpriv: 
scheduling-class: 
ip-type: shared
hostid: 
net:
        address: 10.2.4.11/24
        physical: e1000g0
        defrouter: 10.2.4.1

----------

netstat -rn from global zone:

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface 
-------------------- -------------------- ----- ----- ---------- --------- 
default              10.2.4.1             UG        2        181 e1000g0   
10.2.4.0             10.2.4.10            U         6      62078 e1000g0   
127.0.0.1            127.0.0.1            UH        4         28 lo0       

Routing Table: IPv6
  Destination/Mask            Gateway                   Flags Ref   Use    If   
--------------------------- --------------------------- ----- --- ------- ----- 
::1                         ::1                         UH      2       4 lo0   
fe80::/10                   fe80::21b:21ff:fe2d:e766    U       2       0 e1000g

----------

IPv4/IPv6 routing & forwarding are disabled according to routeadm.

----------

This has got me stumped. Then again, I don't know my butt from my shoulder when 
it comes to TCP/IP networking, so it's probably something simple. I would be 
happy to provide more info. Any ideas?

Thanks,
Alex
-- 
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org

Reply via email to