Hi.

I've got a routing issue with Solaris 10 Update 5 and I don't know if
I can solve it. Basically I've got a multihomed server:

enr...@server0:~$ ifconfig -a
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 zone1
        inet 127.0.0.1 netmask ff000000
bge0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
        inet 192.168.1.50 netmask ffffe000 broadcast 192.168.31.255
nge1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
        inet 192.168.96.77 netmask ffffe000 broadcast 192.168.127.255
nge1:1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu
1500 index 3
        zone zone1

which also acts forwards packets between the two subnets and acts as a router:
enr...@server0:~$ routeadm
              Configuration   Current              Current
                     Option   Configuration        System State
---------------------------------------------------------------
               IPv4 routing   enabled              enabled
               IPv6 routing   disabled             disabled
            IPv4 forwarding   enabled              enabled
            IPv6 forwarding   disabled             disabled

           Routing services   "route:default ripng:default"

Routing daemons:

                      STATE   FMRI
                   disabled   svc:/network/routing/legacy-routing:ipv4
                   disabled   svc:/network/routing/legacy-routing:ipv6
                   disabled   svc:/network/routing/ndp:default
                   disabled   svc:/network/routing/rdisc:default
                   disabled   svc:/network/routing/ripng:default
                   disabled   svc:/network/routing/ripng:quagga
                     online   svc:/network/routing/route:default
                   disabled   svc:/network/routing/zebra:quagga
                   disabled   svc:/network/routing/rip:quagga
                   disabled   svc:/network/routing/ospf:quagga
                   disabled   svc:/network/routing/ospf6:quagga
                   disabled   svc:/network/routing/bgp:quagga

bge0 is up on a subnet (192.168.0.0/19) and nge1 is up on another
subnet (192.168.96.0/19). The routing table is:
enr...@reacciona0:~$ netstat -rn

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              192.168.96.1         UG        1    2682544
default              192.168.96.1         UG        1    2680065 nge1
192.168.0.0          192.168.1.50         U         1      24343 bge0
192.168.96.0         192.168.96.77        U         1      11327 nge1
224.0.0.0            192.168.1.50         U         1          0 bge0
127.0.0.1            127.0.0.1            UH        2       8810 lo0

Zones running on subnet 192.168.96.0/19 have no problem because they
see the default route through gateway 192.168.96.1 such as, for
example:
enr...@server0:~$ ssh enr...@zone1 netstat -rn
Password:

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              192.168.96.1         UG        1    2682596
default              192.168.96.1         UG        1    2680117 nge1
192.168.96.0         192.168.96.53        U         1         58 nge1:1
224.0.0.0            192.168.96.53        U         1          0 nge1:1
127.0.0.1            127.0.0.1            UH        4         44 lo0:1

The problem I have is when creating shared IP zones on another subnet,
such as the 192.168.0.0/19: subnet 192.168.96.0/19 is unreachable and
they cannot connet to the outside world through 192.168.96.1. I
thought that there would be a way to accomplish this because server0
is acting as a router and packet forwarder between these two subnets
but I found no way to configure the zones. Other workstations on the
192.168.0.0/19 subnet have indeed no problem using server0 as default
gateway.

Is there any way to use server0 as a router from inside the shared IP
zone so that the global zone forwards packets from one subnet to the
other and be able to reach 192.168.96.1?

Thanks,
Enrico

-- 
Ελευθερία ή θάνατος
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the Universe trying
to produce bigger and better idiots. So far, the Universe is winning."
GPG key: 1024D/FD2229AF
fpr: 9E07 D40E 33A5 5993 6FC5  09A8 5BCF B1F2 FD22 29AF
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to