Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tramker]

Hello,

I've got a problem with DIR-605L HW:Ax FW:1.13

It seems to bridge some IPv6 packets from LAN to WAN, so that mac addresses of LAN stations appear on the WAN network.

Router settings:
Internet type: static IP
Wireless mode: wireless router
SPI: on



Here is an example of a packet captured on WAN network. The MAC address 44:1e:a1:32:48:9f belongs to a station on LAN.

601.814710 fe80::461e:a1ff:fe32:489f -> ff02::1:2    DHCPv6 Solicit

Frame 1 (161 bytes on wire, 161 bytes captured)
    Arrival Time: Jan 16, 2013 14:55:39.173473000
    [Time delta from previous captured frame: 0.000000000 seconds]
    [Time delta from previous displayed frame: 0.000000000 seconds]
    [Time since reference or first frame: 0.000000000 seconds]
    Frame Number: 1
    Frame Length: 161 bytes
    Capture Length: 161 bytes
    [Frame is marked: False]
    [Protocols in frame: eth:ipv6:udp:dhcpv6]
Ethernet II, Src: 44:1e:a1:32:48:9f (44:1e:a1:32:48:9f), Dst: IPv6mcast_00:01:00:02 (33:33:00:01:00:02)
    Destination: IPv6mcast_00:01:00:02 (33:33:00:01:00:02)
        Address: IPv6mcast_00:01:00:02 (33:33:00:01:00:02)
        .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
        .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
    Source: 44:1e:a1:32:48:9f (44:1e:a1:32:48:9f)
        Address: 44:1e:a1:32:48:9f (44:1e:a1:32:48:9f)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
    Type: IPv6 (0x86dd)
Internet Protocol Version 6
    0110 .... = Version: 6
        [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
    .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
    .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
    Payload length: 107
    Next header: UDP (0x11)
    Hop limit: 1
    Source: fe80::461e:a1ff:fe32:489f (fe80::461e:a1ff:fe32:489f)
    Destination: ff02::1:2 (ff02::1:2)
User Datagram Protocol, Src Port: dhcpv6-client (546), Dst Port: dhcpv6-server (547)
    Source port: dhcpv6-client (546)
    Destination port: dhcpv6-server (547)
    Length: 107
    Checksum: 0xf21d [validation disabled]
        [Good Checksum: False]
        [Bad Checksum: False]
DHCPv6
    Message type: Solicit (1)
    Transaction-ID: 0x00d0d8a5
    Elapsed time
        option type: 8
        option length: 2
        elapsed-time: 655350 ms
    Client Identifier
        option type: 1
        option length: 10
        DUID type: link-layer address (3)
        Hardware type: Ethernet (1)
        Link-layer address: 44:1e:a1:32:48:9f
    Identity Association for Non-temporary Address
        option type: 3
        option length: 40
        IAID: 2
        T1: 14400
        T2: 21600
        IA Address
            option type: 5
            option length: 24
            IPv6 address: ::
            Preferred lifetime: 28800
            Valid lifetime: 36000
    Option Request
        option type: 6
        option length: 12
        Requested Option code: Status code (13)
        Requested Option code: Server unicast (12)
        Requested Option code: DNS recursive name server (23)
        Requested Option code: Domain Search List (24)
        Requested Option code: Fully Qualified Domain Name (39)
        Requested Option code: Preference (7)
    Fully Qualified Domain Name
        option type: 39
        option length: 11
        0000 0... = Reserved: 0x00
        .... .0.. = N: N bit cleared
        .... ..0. = O: O bit cleared
        .... ...1 = S: S bit set
        Domain: NPI32489F

[FurryNutz]

Link>Welcome!

What region are you located?
Are you wired or wireless connected to the router?
Has a Factory Reset been performed?

What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Double NAT
To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.
Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask.

Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP if you have this option under Advanced/Firewall.

Set current Time Zone, Date and Time. Use an NTP server feature. Tools/Time.

[tramker]

Europe, Czech Republic. Internet (WAN) is static IP ethernet, no modem. Clients both LAN and wireless. Seems like a bug as I wouldn't expect a router to forward any L2 packets from LAN to WAN.

[FurryNutz]

I'll see if one of our resident IPv6 users can help us out here...

Other than this, is the router working for you?

[PacketTracer]

[1] Are you sure you captured this frame from WAN?
[2] No other layer 2 path from LAN to WAN bypassing the DIR-605L?
[3] Is the HP device that sent the DHCPv6 solicitation connected to both LAN and WAN (via 2 seperated interfaces -- it can use the same MAC address and hence the same link local address on both interfaces, this is no error)?

If your answers are "Yes" for [1] and [2] and "No" for [3], I would agree to you, that the DIR-605L seems to bridge at least multicasts.

In this case: To harden your suspicion you could check if unicasts get also bridged: From a node within your LAN (if possible, say the HP device which sent the captured DHCPv6 solicitation from IPv6 address fe80::461e:a1ff:fe32:489f and MAC address 44:1e:a1:32:48:9f) try to ping6 the link local address fe80::xxxx:xxxx:xxxx:xxxx of another node within your WAN if available. You should get a reply if the DIR-605L operates as a bridge and no firewall drops the ICMPv6 echoes (the MAC address of fe80::xxxx:xxxx:xxxx:xxxx should get resolved via neighbor solicitation and advertisement packets which get bridged either).

[tramker]

FurryNutz: yes, other than this, it seems to be working ok so far.

PacketTracer:
[1] yes
[2] no other path
[3] not possible, there is only one link (cable) from WAN switch and it's connected to the WAN port of the router.

Unfortunately, I can't do much of the testing, as the router is on customer's network (I'm the ISP). But I've seen DHCPv6 packets only, so far. I did try to ping to unknown local IP from the router's web interface, to see if I get arps on the outside, but that didn't happen, so I don't think there is an interconnection between LAN and WAN.

[wi red]

We had exactly the same problem (and I mean exactly), with one of our routers (same model, rev. A), we had to change the router quickly because our ISP warned us about multiple MAC addresses forwarded into their network. We tried to replicate the problem in our network but since we changed the WAN IP, the problem disappeared. I'll post again after several tests.

[FurryNutz]

Keep us posted...
 

PT, is this something that needs to be added here?
http://forums.dlink.com/index.php?topic=58287.0

We had exactly the same problem (and I mean exactly), with one of our routers (same model, rev. A), we had to change the router quickly because our ISP warned us about multiple MAC addresses forwarded into their network. We tried to replicate the problem in our network but since we changed the WAN IP, the problem disappeared. I'll post again after several tests.

[PacketTracer]

PT, is this something that needs to be added here?

No.

[FurryNutz]