Announcement

Collapse
No announcement yet.

IPv6 Subnetting

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 67GTA
    replied
    I've looked around, and I think only tomato has full ipv6 support, but you still have to fiddle with it. It wasn't worth the trouble to me. I just added this to the list of "Honey, this is why I need a new router".

    Leave a comment:


  • SteveRiley
    replied
    We're living in an IPv4-IPv6 transition world right now. It will be almost impossible to avoid tunnels until IPv6 is running natively everywhere.

    Leave a comment:


  • GreyGeek
    replied
    Originally posted by 67GTA View Post
    If you are using dd-wrt, the dev has stopped including IPV6 support. This drove me nuts for a while until I figured it out.>
    I did some searching and found this:http://www.dd-wrt.com/wiki/index.php...D-WRT%3F#Notes
    (5)Apparently, IPv6-related features DO NOT work by default in DD-WRT v24. See IPv6 on v24.
    That link led to this one:
    http://www.dd-wrt.com/wiki/index.php/IPv6_on_v24
    This link states:
    IPv6 On V24


    UPDATE: If you are just trying to get IPv6 working (6to4) on v24 sp1, please view this page:
    http://www.dd-wrt.com/wiki/index.php/IPv6#6to4_Setup

    ...
    The currently recommended K2.6 big images ship with basic IPv6 support. That means that you're able to activate the IPv6 IP stack for routing and static tunnels. What's missing are the ip6tables kernel modules and the userland tools needed. It's possible to add the missing parts but that requires some basic Linux system knowledge. It's assumed here that you have /jffs mounted and a few megs of space available and you know how to use ipkg.Please note: What you've to download still depends a lot on the hardware you're running on!

    Kernel modules

    The currently recommended build r14929 ships with a patched Linux kernel with a version number set to 2.6.24.111. Since the kernel modules from OpenWRT have the magic version information set you can't use the kmod packages from OpenWRT. Because of the version mismatch insmod won't load those modules.
    This leaves you with two options:
    1. Trust lazytom and download his set of modules from the forum http://www.dd-wrt.com/phpBB2/download.php?id=16285
    2. If you don't trust random people on the internet (which is a good thing) you'll find an introduction on how to build these modules yourself in this blog post http://blog.dest-unreach.be/2010/12/...kernel-modules

    .....
    Which leads to:
    6to4 is a mechanism which assigns a large block of IPv6 addresses to every IPv4 address on the Internet. You can use 6to4 with DD-WRT to give every computer on your network a globally-accessible IPv6 address without the need to configure explicit tunneling. This should be the simplest method to add IPv6 to your entire network.
    Important Reminders :
    • In order to use ipv6, you need the Standard or VoIP version of DD-WRT, as these are currently the only ones which support both IPv6 and radvd.
    • The detailled configuration steps are targeted toward users with a basic DHCP connection for the WAN part. So, if using PPPoE will require replacing vlan1 with ppp0 in each instance. Other connection types will vary.
    • When using DD-WRT standard on a router with 4MB Flash, there is no space available for jffs.
    • This guide only relies on nvram variables, so that jffs is not needed.
    • The configuration shown below has been verified to work properly on v24 sp1 stable (standard)

    ...
    and we are back to tunnels again.

    Leave a comment:


  • GreyGeek
    replied
    Originally posted by SteveRiley View Post
    What about OpenWRT? Might be a suitable alternative.
    Apparently the same way I get it with Kubuntu: http://wiki.openwrt.org/doc/howto/ipv6
    Obtain IPv6 support

    Follow ipv6.essentials to obtain full IPv6 support. Then come back and read about the configuration here:
    There are two big, different steps:
    1. Set up a working IPv6 connection on the OpenWrt router, either by tunneling (SixXs, TSP, 6to4), or natively
    2. Propagate the IPv6 subnet to the LAN with RADVD or DHCPv6.


    Native IPv6 access

    For this, you need to obtain an IPv6 address from your ISP. Technically this could be a /128 prefix (exactly one IPv6 address), but according to rfc6177 this should be a /64 prefix. You may also get bigger range, like /56 or /48. Within this range you may use all the IPv6 addresses to your liking without any NAT-induced headaches.
    Here is someone's attempt: https://forum.openwrt.org/viewtopic.php?id=27541
    I was looking for information about configuring my router (originally Netgear WNDR3700) for supporting a static 6in4 tunnel from SixXS for getting the IPv6 connectivity. The router is currently running OpenWrt Backfire 10.03.1-rc4, published in November 2010, the rc4 version of the forthcoming Backfire Interim Release 1.

    Current OpenWrt Backfire 10.03.1-rc4 has an installable package for supporting the 6in4 tunnels, which should make the process relatively easy. However, finding the exactly correct configuration is not that easy. I found useful information in internet, but it was scattered around and to some extent also outdated or incomplete. I write this article to summarize my findings and to list my configuration as an example for others trying to do the same.

    Additionally, the rc4 version does not enable configuring some of the required steps through the Luci GUI, so some tasks have to be done by editing configuration files manually.

    Background assumptions: you have a "Static" 6in4 tunnel with a fixed tunnel endpoint from SixXS. You also have a subnet, which is routed through that tunnel. You also have installed the OpenWrt to the router.

    Main steps in the process:
    Configuring the tunnel
    Configuring iptables to make sure that the tunnel stays up
    Configuring IPv6 address autoconfiguration inside local LAN by using RADVD
    Configuring ipv6 firewall - ip6tables
    ...
    ... and it goes on. With that advice and installing miredo I can get a dual stack.

    Leave a comment:


  • SteveRiley
    replied
    What about OpenWRT? Might be a suitable alternative.

    Leave a comment:


  • 67GTA
    replied
    I haven't found any official statement. I ran across a post on their forums where every one was asking where IPV6 had gone. All of the older builds had support, but was dropped somewhere down the line. You are supposed to be able to set it up, but my Linksys WRT160n doesn't have the ram. I already have to use the mini build to run dd-wrt on it. http://www.dd-wrt.com/wiki/index.php/IPv6

    Leave a comment:


  • GreyGeek
    replied
    Originally posted by 67GTA View Post
    If you are using dd-wrt, the dev has stopped including IPV6 support. This drove me nuts for a while until I figured it out.>
    Did the dev say why?

    Leave a comment:


  • 67GTA
    replied
    If you are using dd-wrt, the dev has stopped including IPV6 support. This drove me nuts for a while until I figured it out.>

    Leave a comment:


  • GreyGeek
    replied
    An aside: Somehow my Chromium browser stopped preferring IPv6 over IPv4, and I't get an error message from some sites saying that I didn't have IPv6 so they couldn't display the page. I tried with FireFox it the page would display. I also "ping6"ed the websites and both ends of my tunnel and got echos back.

    FireFox has a setting one can use to enable a preference for either IPv6 or IPv4. Chromium *used* to have such a setting (in the url enter "chrome://net-eternals" and on that page select "DNS". The DNS page did have a button that enabled IPv6. Now, it doesn't. Chromium now shows "ADDRESS_FAMILY_UNSPECIFIED", which causes it to consult /etc/gai.conf to determine which IP protocol to try first. It used to prever IPv6. Now it trys IPv4 first.

    The man pages to gai.conf are not very extensive nor are they understandable. An example is given but no explanation. After some experimentation/trial/error I come across settings that worked to make Chromium try IPv6 first:

    Code:
    label ::1/128       0
    label 2002::/16     1
    label 2001:0::/32 2
    label ::/0          3
    label ::/96         4
    #label ::ffff:0:0/96 5
    #label fec0::/10     6
    #label fc00::/7      7
    
    
    #
    .....
    #
    precedence  ::1/128       50
    precedence  ::/0          40
    precedence 2001:0::/32  35
    precedence  2002::/16     30
    precedence ::/96          20
    #precedence ::ffff:0:0/96  10
    I added the "... 2001:0::/32 2" lines to both label and precedence. My assumption is that getaddressinfo() would try them in the order of the index numbers at the end of each line. True or not, Chromium now tries the IPv6 protocol first.

    Leave a comment:


  • Jonas
    replied
    Originally posted by GreyGeek View Post
    [FONT=courier new]
    Ah, then your IPv6 connectivity is totally dependent on the Teredo tunnel and your DNS servers (which give you the 10th 10) are supplied by your ISP. This suggests that IF your cable modem is DOCSIS 3.0 compatible, since your ISP is IPv6 already, that:

    https://wiki.ubuntu.com/IPv6#Native_IPv6_connections


    and you could use DHCPv6 to dispense an IPv6 address.
    I have fiber cable - only thing I "plug in" is the router a D-Link DIR 655, which is quite a old model. Sites seem to load slower with IPv6 enabled , I've had this trouble before so I used to disable it.

    b.r

    Jonas

    Leave a comment:


  • GreyGeek
    replied
    Originally posted by Jonas View Post
    sudo ifconfig teredo down & sudo service miredo stop

    Give me IPv6 result of 0/10

    Ah, then your IPv6 connectivity is totally dependent on the Teredo tunnel and your DNS servers (which give you the 10th 10) are supplied by your ISP. This suggests that IF your cable modem is DOCSIS 3.0 compatible, since your ISP is IPv6 already, that:

    https://wiki.ubuntu.com/IPv6#Native_IPv6_connections
    Native IPv6 connections

    Contact your Internet Service Provider to see if they offer IPv6 yet. Only a few Internet Service Providers (ISP) currently offer native IPv6 service, though by 2015 probably all of them will.
    If your uplink involves a wifi router or broadband modem, those devices will need to support IPv6. Cable-Modems need to support DOCSIS 3.0 or 2.0+IPv6. As of 2010, very few DSL-Modems support IPv6; this will change by 2012.
    If your hardware or ISP does not support native IPv6, which is the best kind, you might still be able to use IPv6 tunneled over IPv4 instead.


    and you could use DHCPv6 to dispense an IPv6 address.

    Leave a comment:


  • Jonas
    replied
    sudo ifconfig teredo down & sudo service miredo stop

    Give me IPv6 result of 0/10

    b.r

    Jonas

    Leave a comment:


  • GreyGeek
    replied
    Originally posted by Jonas View Post
    Here's my route -6:
    Code:
    jonas@kubacer:~$ route -6
    Kernel IPv6 routing table
    Destination                    Next Hop                   Flag Met Ref Use If
    fe80::/64                      ::                         U    256 0     0 eth1
    ::/0                           ::                         !n   -1  1     1 lo
    ::1/128                        ::                         Un   0   1     1 lo
    fe80::1af4:6aff:fe23:7b76/128  ::                         Un   0   1     0 lo
    ff00::/8                       ::                         U    256 0     0 eth1
    ::/0                           ::                         !n   -1  1     1 lo
    Sorry for not being able to help more, this is all greek to me :S
    ....
    So, I't pretty much greek to me as well, Jonas. I'm just tinkering around... luckily IPv6 isn't toxic or explosive.

    I noticed that your setup doesn't have a UG on your IPv6 ff00::/8 eth1 connection.

    And, the ip addr command shows a teredo address of 2001:0 ..... but your IPv6 routing table doesn't include it. Yet, you get out and have a 10/10 connection.

    Code:
    [COLOR=#333333]4: teredo: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500[/COLOR]
    [COLOR=#333333]link/none [/COLOR]
    [COLOR=#333333]inet6 [/COLOR][COLOR=#ff0000]2001:0[/COLOR][COLOR=#333333]:53aa:64c:c47:3ccc:d1c4:ceb7/32 scope global [/COLOR]
    [COLOR=#333333]valid_lft forever preferred_lft forever[/COLOR]
    [COLOR=#333333]inet6 fe80::ffff:ffff:ffff/64 scope link [/COLOR]
    [COLOR=#333333]valid_lft forever preferred_lft forever
    [/COLOR]
    Mine shows I have my IPv6 sixxs device as a gateway:
    Code:
    ::/0                           2001:4978:f:580::1         U[COLOR=#ff0000]G[/COLOR]   1024 0     0 sixxs
    Apparently without a gateway and no IPv6 DNS, you communicate with IPv6 networks and have DNS resolution in them. It must all be due to your ISP.

    Question:
    If you do:
    sudo ifconfig teredo down
    or
    sudo service miredo stop

    do you still get 10/10?
    Last edited by GreyGeek; Jun 18, 2012, 09:18 AM.

    Leave a comment:


  • Jonas
    replied
    Here's my route -6:
    Code:
    jonas@kubacer:~$ route -6
    Kernel IPv6 routing table
    Destination                    Next Hop                   Flag Met Ref Use If
    fe80::/64                      ::                         U    256 0     0 eth1
    ::/0                           ::                         !n   -1  1     1 lo
    ::1/128                        ::                         Un   0   1     1 lo
    fe80::1af4:6aff:fe23:7b76/128  ::                         Un   0   1     0 lo
    ff00::/8                       ::                         U    256 0     0 eth1
    ::/0                           ::                         !n   -1  1     1 lo
    Sorry for not being able to help more, this is all greek to me :S

    I'm happy to help in anyway I can, just gimme the lines to analyse, and maybe learn a thing or two

    b.r

    jonas

    Leave a comment:


  • GreyGeek
    replied
    Originally posted by Jonas View Post
    Code:
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
    169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0
    192.168.0.0     0.0.0.0         255.255.255.0   U     1      0        0 eth0
    Jonas,
    I'm still trying to understand why I don't get a 10/10, i.e., why my IPv6 DNS addresses are not honored.

    What do you get when you use "route -6"?

    Here's what I get while running SixXS:
    Code:
    :~$ route -6
    Kernel IPv6 routing table
    Destination                    Next Hop                   Flag Met Ref Use If
    [COLOR=#ff0000]::/96                          ::                         Un   256 0     0 sit0   [/COLOR]
    2001:4978:f:580::/64           ::                         U    256 0     1 sixxs
    fe80::/64                      ::                         U    256 0     0 wlan0
    fe80::/64                      ::                         U    256 0     0 sixxs
    [COLOR=#ff0000]::/0                           2001:4978:f:580::1         UG   1024 0     0 sixxs[/COLOR]
    ::/0                           ::                         !n   -1  1   140 lo
    ::1/128                        ::                         Un   0   1     3 lo
    ::127.0.0.1/128                ::                         Un   0   1     0 lo
    ::192.168.1.101/128            ::                         Un   0   1     0 lo
    2001:4978:f:580::2/128         ::                         Un   0   1    63 lo
    fe80::4878:f:580:2/128         ::                         Un   0   1     0 lo
    fe80::76de:2bff:fe36:e435/128  ::                         Un   0   1     0 lo
    ff00::/8                       ::                         U    256 0     0 wlan0
    ff00::/8                       ::                         U    256 0     0 sixxs
    ::/0                           ::                         !n   -1  1   140 lo
    
    
                   ::                         !n   -1  1   131 lo
    StixXS creates a gateway (UG) from default to the SixXS tunnel. Also, SixXS creates a "sit0" device, but it is down. I can bring it up with "ifconfig sit0 up", which then puts it into the route listing, but I have no idea what it is supposed to do. The tunnel works the same whether it is up or down, and with either I still get 9/10 on the ipv6test.

    When I use miredo, on the other hand, there does NOT appear to be a gateway created, yet miredo still gives me a 9/10 on ipv6test, the same as sixxs. Here's the routing table with miredo loaded and functioning"
    Code:
    :~$ route -6
    Kernel IPv6 routing table
    Destination                    Next Hop                   Flag Met Ref Use If
    2001::/32                      ::                         U    256 0     0 teredo
    fe80::/64                      ::                         U    256 0     0 wlan0
    fe80::/64                      ::                         U    256 0     0 teredo
    ::/0                           ::                         U    1029 0     0 teredo
    ::/0                           ::                         !n   -1  1   124 lo
    ::1/128                        ::                         Un   0   1     3 lo
    2001:0:53aa:64c:3cef:1324:e720:544/128 ::                         Un   0   1     0 lo
    2001:4978:f:580::2/128         ::                         Un   0   1    53 lo
    fe80::ffff:ffff:ffff/128       ::                         Un   0   1     0 lo
    fe80::4878:f:580:2/128         ::                         Un   0   1     0 lo
    fe80::76de:2bff:fe36:e435/128  ::                         Un   0   1     0 lo
    ff00::/8                       ::                         U    256 0     0 wlan0
    ff00::/8                       ::                         U    256 0     0 teredo
    ::/0                           ::                         !n   -1  1   124 lo
    Both urls give me an extensive whois listing:
    Code:
    :~$ [COLOR=#ff0000][FONT=courier new]whois 2001:4978:f:580::1[/FONT][/COLOR]
    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=2001:4978:f:580::1?showDetails=true&showARIN=false&ext=netref2
    #
    
    
    
    
    # start
    
    
    NetRange:       2001:4978:: - 2001:4978:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
    CIDR:           2001:4978::/32
    OriginAS:       
    NetName:        YOURORG-NB6-AR-1
    NetHandle:      NET6-2001-4978-1
    Parent:         NET6-2001-4800-0
    NetType:        Direct Allocation
    RegDate:        2005-10-20
    Updated:        2012-03-02
    Ref:            http://whois.arin.net/rest/net/NET6-2001-4978-1
    
    
    OrgName:        YOUR.ORG, INC.
    OrgId:          YOURO
    Address:        840 W Lake St #406
    City:           Roselle
    StateProv:      IL
    PostalCode:     60172
    Country:        US
    RegDate:        2002-12-18
    Updated:        2011-09-24
    Ref:            http://whois.arin.net/rest/org/YOURO
    
    
    OrgTechHandle: KDA6-ARIN
    OrgTechName:   Day, Kevin 
    OrgTechPhone:  +1-312-884-7618 
    OrgTechEmail:  noc@your.org
    OrgTechRef:    http://whois.arin.net/rest/poc/KDA6-ARIN
    
    
    OrgAbuseHandle: KDA6-ARIN
    OrgAbuseName:   Day, Kevin 
    OrgAbusePhone:  +1-312-884-7618 
    OrgAbuseEmail:  noc@your.org
    OrgAbuseRef:    http://whois.arin.net/rest/poc/KDA6-ARIN
    
    
    RTechHandle: KDA6-ARIN
    RTechName:   Day, Kevin 
    RTechPhone:  +1-312-884-7618 
    RTechEmail:  noc@your.org
    RTechRef:    http://whois.arin.net/rest/poc/KDA6-ARIN
    
    
    RNOCHandle: KDA6-ARIN
    RNOCName:   Day, Kevin 
    RNOCPhone:  +1-312-884-7618 
    RNOCEmail:  noc@your.org
    RNOCRef:    http://whois.arin.net/rest/poc/KDA6-ARIN
    
    
    RAbuseHandle: KDA6-ARIN
    RAbuseName:   Day, Kevin 
    RAbusePhone:  +1-312-884-7618 
    RAbuseEmail:  noc@your.org
    RAbuseRef:    http://whois.arin.net/rest/poc/KDA6-ARIN
    
    
    # end
    
    
    
    
    # start
    
    
    NetRange:       2001:4978:F:: - 2001:4978:F:FFFF:FFFF:FFFF:FFFF:FFFF
    CIDR:           2001:4978:F::/48
    OriginAS:       AS19255
    NetName:        YOUR-ORG-SIXXS-CHI02-TUNNELS
    NetHandle:      NET6-2001-4978-F-1
    Parent:         NET6-2001-4978-1
    NetType:        Reassigned
    Comment:        SixXS allocation for Your.org Chicago,IL PoP - This allocation is used for tunnels. - For more details, query whois.sixxs.net - More information can be found at http://www.sixxs.net/ - Abuse reports should go to abuse@sixxs.net
    RegDate:        2007-10-29
    Updated:        2007-10-29
    Ref:            http://whois.arin.net/rest/net/NET6-2001-4978-F-1
    
    
    OrgName:        SixXS
    OrgId:          SIXXS
    Address:        Swiss Post Box 100285
    Address:        Zurcherstrasse 161
    City:           Zurich
    StateProv:      
    PostalCode:     CH-8010
    Country:        CH
    RegDate:        2007-10-29
    Updated:        2011-11-30
    Comment:        Website: http://www.sixxs.net
    Comment:        Abuse contact: abuse@sixxs.net
    Comment:        Inquiries: info@sixxs.net
    Ref:            http://whois.arin.net/rest/org/SIXXS
    
    
    ReferralServer: rwhois://whois.sixxs.net:43
    
    
    OrgTechHandle: STRA1-ARIN
    OrgTechName:   SixXS Technical Role Account
    OrgTechPhone:  +41325129742 
    OrgTechEmail:  info@sixxs.net
    OrgTechRef:    http://whois.arin.net/rest/poc/STRA1-ARIN
    
    
    OrgAbuseHandle: STRA1-ARIN
    OrgAbuseName:   SixXS Technical Role Account
    OrgAbusePhone:  +41325129742 
    OrgAbuseEmail:  info@sixxs.net
    OrgAbuseRef:    http://whois.arin.net/rest/poc/STRA1-ARIN
    
    
    # end
    
    
    
    
    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #
    
    
    
    
    
    
    Found a referral to whois.sixxs.net:43.
    
    
    % This is the SixXS Whois server.
    % SixXS - http://www.sixxs.net.
    %
    % The objects are in RPSL format.
    %
    % Objects not beginning with SIXXS- or ending in
    % -SIXXS are cached responses from remote sources.
    %
    % This server outputs referto's when a object from a
    % known registry (ARIN,RIPE,LACNIC,APNIC,AFRINIC,6BONE)
    % is not locally available.
    
    
    % Searching for prefix
    
    
    inet6num:     2001:4978:f:580::/64
    netname:      SIXXS-USCHI02-TUN1409
    descr:        ayiya tunnel to 24.223.250.187
    
    
    descr:        Tunnel XXXXXX goes to an endpoint of JLK6-SIXXS.
    country:      US
    remarks:      Userstate: enabled
    remarks:      Adminstate: enabled
    admin-c:      JLK6-SIXXS
    admin-c:      KDA6-ARIN % (PoP admin-c)
    tech-c:       JLK6-SIXXS
    tech-c:       KDA6-ARIN % (PoP tech-c)
    remarks:      Prefixtype: Tunnel
    remarks:      MTU: 1280
    remarks:      This object is generated from the SixXS database
    remarks:      Abuse must be reported to abuse@sixxs.net
    remarks:      Information can be found at http://www.sixxs.net/
    changed:      info@sixxs.net 20120609
    mnt-by:       SIXXS-MNT
    source:       SIXXS
    
    
    person:       Kevin Day
    address:      P.O. 326
    address:      Round Lake Beach
    address:      IL
    address:      60073
    country:      US
    phone:        +1-312-884-7618
    e-mail:       noc@your.org
    nic-hdl:      KDA6-ARIN
    remarks:      State: Enabled
    remarks:      This object is generated from the SixXS database
    remarks:      Abuse must be reported to abuse@sixxs.net
    remarks:      Information can be found at http://www.sixxs.net/
    changed:      info@sixxs.net 20070324
    changed:      info@sixxs.net 20071025
    remarks:      This object is partially cached into the SixXS database
    remarks:      and is not a 1:1 representation of the original object
    source:       SIXXS
    
    
    person:       Jerry Lynn Kreps
    address:      XXXXXXXXXXXXXXXXXXX
    address:      Lincoln, NE  XXXXX
    address:      USA
    country:      US
    phone:        +1402XXXXXXX
    e-mail:       greygeek@earthlink.net
    nic-hdl:      JLK6-SIXXS
    remarks:      State: Enabled
    remarks:      This object is generated from the SixXS database
    remarks:      Abuse must be reported to abuse@sixxs.net
    remarks:      Information can be found at http://www.sixxs.net/
    changed:      info@sixxs.net 20120608
    changed:      info@sixxs.net 20120609
    mnt-by:       SIXXS-MNT
    source:       SIXXS
    
    
    mntner:       SIXXS-MNT
    descr:        SixXS Maintainer
    admin-c:      JRM1-RIPE
    admin-c:      PBVP1-RIPE
    tech-c:       PBVP1-RIPE
    tech-c:       JRM1-RIPE
    upd-to:       info@sixxs.net
    mnt-nfy:      info@sixxs.net
    auth:         CYPHERKEY XXXXXXXXXXXXXXXXXXXXXXXXXXX/
    remarks:      Maintains all data generated from the SixXS database.
    remarks:      This object is generated from the SixXS database
    remarks:      Abuse must be reported to abuse@sixxs.net
    remarks:      Information can be found at http://www.sixxs.net/
    changed:      info@sixxs.net 19780225
    mnt-by:       SIXXS-MNT
    source:       SIXXS
    
    
    % Thank you for using the SixXS Whois Service
    My end of the miredo tunnel, 2001:0:53aa:64c:3cef:1324:e720:544, just gives me a querying for my IPv4 endpoint, 24.223.250.187, of a Teredo IPv6 address, which is nothing more than my IPv4 IP address. Checking on the other end of the tunnel given in the /etc/miredo.conf file:

    Code:
    :~$ [FONT=courier new][COLOR=#ff0000]nslookup teredo-debian.remlab.net[/COLOR][/FONT]
    Server:         127.0.0.1
    Address:        127.0.0.1#53
    
    
    Non-authoritative answer:
    teredo-debian.remlab.net        canonical name = teredo.remlab.net.
    Name:   teredo.remlab.net
    Address: 83.170.6.76
    
    
    jerry@jerry-Aspire-7739:~$ [FONT=courier new][COLOR=#ff0000]whois 83.170.6.76[/COLOR][/FONT]
    % This is the RIPE Database query service.
    % The objects are in RPSL format.
    %
    % The RIPE Database is subject to Terms and Conditions.
    % See http://www.ripe.net/db/support/db-terms-conditions.pdf
    
    
    % Note: this output has been filtered.
    %       To receive output for a database update, use the "-B" flag.
    
    
    % Information related to '83.170.6.64 - 83.170.6.79'
    
    
    inetnum:        83.170.6.64 - 83.170.6.79
    netname:        DE-IABG-TELEPORT-BSC
    descr:          Bernhard Schmidt
    country:        DE
    admin-c:        BSC-RIPE
    tech-c:         BSC-RIPE
    status:         ASSIGNED PA
    mnt-by:         IABG-MNT
    mnt-lower:      IABG-MNT
    source:         RIPE # Filtered
    
    
    person:          Bernhard Schmidt
    address:         Karl-Richter-Str. 8
    address:         80939 Muenchen
    address:         Germany
    phone:           +49 89 74140493
    nic-hdl:         BSC-RIPE
    mnt-by:          IABG-MNT
    source:          RIPE # Filtered
    
    
    % Information related to '83.170.0.0/18AS29259'
    
    
    route:        83.170.0.0/18
    descr:        IABG mbH
    origin:       AS29259
    mnt-lower:    IABG-MNT
    mnt-routes:   IABG-MNT
    mnt-by:       IABG-MNT
    source:       RIPE # Filtered
    
    
    % This query was served by the RIPE Database Query Service version 1.12.2 (WHOIS3)




    And, another way to get routing tables:
    Code:
    :~$ [FONT=courier new][COLOR=#ff0000]ip  route[/COLOR][/FONT]
    default via 192.168.1.1 dev wlan0  proto static 
    169.254.0.0/16 dev wlan0  scope link  metric 1000 
    192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.101  metric 2
     
    :~$ [FONT=courier new][COLOR=#ff0000]ip -6  route[/COLOR][/FONT]
    ::/96 via :: dev sit0  metric 256 
    2001:4978:f:580::/64 dev sixxs  proto kernel  metric 256 
    fe80::/64 dev wlan0  proto kernel  metric 256 
    fe80::/64 dev sixxs  proto kernel  metric 256 
    default via 2001:4978:f:580::1 dev sixxs  metric 1024 
    jerry@jerry-Aspire-7739:~$

    Leave a comment:

Users Viewing This Topic

Collapse

There are 0 users viewing this topic.

Working...
X