configuring routing for ipv6 - simple case.

From: paul van den bergen (pvandenbergen_at_swin.edu.au)
Date: 10/27/03

  • Next message: Mike Silbersack: "Changes to PCBPORTHASH wrt TCP, review needed" 
    To: freebsd-net@freebsd.org
Date: Mon, 27 Oct 2003 17:24:32 +1100

    Hi all,
    I feel like a dufus for asking because this should be simple, but I'm stuck at
    the point where I cannot see what I am doing...

    attempting to set up an IPv6 mobile IP test bed.

    currently I am using site local addresses, specifically fec0:0:0:229::,
    fec0:0:0:10:: and fec0:0:0:172:: for each of the three networks I wish to set
    up.

    I do not want global connectivity as such (yet).

    these are running over an existing (single) ipv4 network, so I only wish to
    configure IPv6 routing, etc., with no IPv4to6 or 6to4 translation.

    I have 4 PCs to configure. Three are on the 229 network, one is a standalone
    node, the other two should be gateways to the 172 and 10 networks
    respecitvely.

    AFAICS, this should be a fairly simple set up...

    so, with nothing more than this, can someone please outline how to set up IPv6
    routing in this situation?

    I believe I should not need to use route6d or similar just to do this static
    routing?

    to make matters somewhat complicated, I am running the KAME snap for MIP6
    connectivity, which afaict requires rtadvd. does this mean that I need to set
    net.inet6.ip6.accept_rtadv=1 ??? since I have net.inet6.ip6.forwarding=1
    because I am using wifi cards on the 10 and 172 networks as APs in hostap
    mode, is this going to cause a problem?
    I did see a table of net.inet6.ip6.forwarding and net.inet6.ip6.accept_rtadv
    settings last week (and do you think I can find it again this week?) that
    suggested that having both to 1 is either invalid or experimental... 

    -- 
Dr Paul van den Bergen
Centre for Advanced Internet Architectures
caia.swin.edu.au
pvandenbergen@swin.edu.au
IM:bulwynkl2002
"And some run up hill and down dale, knapping the chucky stones 
to pieces wi' hammers, like so many road makers run daft. 
They say it is to see how the world was made."
Sir Walter Scott, St. Ronan's Well 1824 
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: Mike Silbersack: "Changes to PCBPORTHASH wrt TCP, review needed"

    Relevant Pages

    • Re: INET6 -- and why I dont use it
      ... command output, to let programs to bind on IPv6 addresses, etc. ... Reading off an IPv4 ... The NAT is very important in function of hiding internal network ... NAT is absent, but source routing resurrected! ...
      (freebsd-net)
    • Re: INET6 -- and why I dont use it
      ... command output, to let programs to bind on IPv6 addresses, etc. ... Reading off an IPv4 ... The NAT is very important in function of hiding internal network ... NAT is absent, but source routing resurrected! ...
      (freebsd-stable)
    • [Full-disclosure] Lets make a spy-proof communications infrastructure
      ... cell phone network which will run like a peer to peer network, ... If we devised some private communicator, ... While truly global routing might require some relays to bridge areas ...
      (Full-Disclosure)
    • [Full-disclosure] Lets design a spy-proof communications infrastructure
      ... cell phone network which will run like a peer to peer network, ... If we devised some private communicator, ... While truly global routing might require some relays to bridge areas ...
      (Full-Disclosure)
    • Re: [Full-disclosure] Lets make a spy-proof communications infrastructure
      ... cell phone network which will run like a peer to peer network, ... If we devised some private communicator, ... While truly global routing might require some relays to bridge areas ... of the government and the intelligence services. ...
      (Full-Disclosure)