[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

More complicated ipv6 routing with radvd



I have a slightly more complicated network topology than normal:


                   Debian box as
(Internet) <-----> firewall/router <-------- Ethernet LAN ---------> etc
                        (1)                      |
                                                 |
                                             Debian box
                                             as router (2)
                                                 |
                                                 |
                                             Wireless LAN
                                                 |
                                                 |
                                                etc

(I decided long ago that I felt much safer if I had the wireless net on
a separate subnet: I can use box (2) to protect my Ethernet net).

I set up ipv6 on the network for internal use (to gain experience with
it) last year some time, and ran radvd on box (2) to do its usual stuff,
including routing information. It set itself up as a default router, but
that didn't matter at the time since I wasn't planning on going to the
Internet on ipv6.

I've now set up a tunnel with Hurricane Electric and got it working on
box (1). The next step is to set up routing so that I can use IPv6 from
other machines on the network, and here's where I ran into problems.

I presume box (1) is the right place to run radvd advertising itself as
a default route. That part works. radvd will, I suppose, also need to
run on box (2) to work with machines on the wireless subnet. That part
works too, but how do I set up radvd on that box to advertise the route
to the wireless subnet on the Ethernet subnet? I can only get it to
advertise itself as a default route, which is clearly wrong.

Apologies if I'm not too clear with this; I'm new to ipv6.

One other thing: I'm a little uneasy trying to do this without a
firewall on the ipv6 side (gShield is working fine these days for ipv4).
Anyone have any suggestions about this, or am I being too paranoid?

Thanks,

 .....Ron


-- 
Ron Murray   (rjmx@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint:
  F2C1 FC47 5EF7 0317 133C  D66B 8ADA A3C4 D86C 74DE

The ultimate reason is "because."


Reply to: