Alan Hughes wrote:
James Knott wrote:
I've decided to try experimenting with IPv6. I can ping the interface on the computer, but nothing on my network. I assume the address listed in ifconfig should be available over the lan. Ethereal, at the far end, shows ICMPv6 Neighbor solicitations being received, but no response being sent. Ping6 says "Destination unreachable: Address unreachable". Is there something else required to enable this? Also, how does one get the apps, such as a browser or ssh to work with an IPv6 address?
tnx jk
Is anything else on your network configured to support IPv6? Do you have an IPv6 router? IPv4 protocol stacks will not respond to an IPv6 ping (or anything else).
It's just a local network. All computers involved are sitting on my desk, to there's only the switch to worry about. As I mentioned in other notes, the computers receive the ping, but don't respond. This is shown by ethereal. They do respond to their own pings. All systems are running SuSE 9.2 or 9.1, which support IPv6.
James Knott wrote:
Alan Hughes wrote:
James Knott wrote:
I've decided to try experimenting with IPv6. I can ping the interface on the computer, but nothing on my network. I assume the address listed in ifconfig should be available over the lan. Ethereal, at the far end, shows ICMPv6 Neighbor solicitations being received, but no response being sent. Ping6 says "Destination unreachable: Address unreachable". Is there something else required to enable this? Also, how does one get the apps, such as a browser or ssh to work with an IPv6 address?
tnx jk
Is anything else on your network configured to support IPv6? Do you have an IPv6 router? IPv4 protocol stacks will not respond to an IPv6 ping (or anything else).
It's just a local network. All computers involved are sitting on my desk, to there's only the switch to worry about. As I mentioned in other notes, the computers receive the ping, but don't respond. This is shown by ethereal. They do respond to their own pings. All systems are running SuSE 9.2 or 9.1, which support IPv6.
But are you sure your switch can handle the IPv6? If your switch is not IPv6 enabled, I doubt that you will get it to work. - James W.
James Wright wrote:
James Knott wrote:
Alan Hughes wrote:
James Knott wrote:
I've decided to try experimenting with IPv6. I can ping the interface on the computer, but nothing on my network. I assume the address listed in ifconfig should be available over the lan. Ethereal, at the far end, shows ICMPv6 Neighbor solicitations being received, but no response being sent. Ping6 says "Destination unreachable: Address unreachable". Is there something else required to enable this? Also, how does one get the apps, such as a browser or ssh to work with an IPv6 address?
tnx jk
Is anything else on your network configured to support IPv6? Do you have an IPv6 router? IPv4 protocol stacks will not respond to an IPv6 ping (or anything else).
It's just a local network. All computers involved are sitting on my desk, to there's only the switch to worry about. As I mentioned in other notes, the computers receive the ping, but don't respond. This is shown by ethereal. They do respond to their own pings. All systems are running SuSE 9.2 or 9.1, which support IPv6.
But are you sure your switch can handle the IPv6? If your switch is not IPv6 enabled, I doubt that you will get it to work. - James W.
To see if it is your switch that is causing the problems, you can try using a crossover cable to directly connect two of the computers directly, and see if you can establish some communication. If you can, it is probably your switch. If it is your switch, you can try to find a firmware upgrade that allows IPv6. Or put a second network card in each computer and forget the switch, but using a switch would be much easier to manage. - James W.
James Wright wrote:
To see if it is your switch that is causing the problems, you can try using a crossover cable to directly connect two of the computers directly, and see if you can establish some communication. If you can, it is probably your switch. If it is your switch, you can try to find a firmware upgrade that allows IPv6. Or put a second network card in each computer and forget the switch, but using a switch would be much easier to manage.
A switch is a layer 2 device, unless it's capable of routing, which is unlikely in this case. All the switch cares is that a 1500byte packet comes in and is switched to a destination port based on the MAC. It doesn't care if it's IP or IPX or Appletalk or whatever. Check the arp tables on the boxes and check the subnet masks on the boxes. Cheers, George -- George Barnett Reality Engineer m: (+44) 778 884 7205 e: george@alink.co.za A candidate is a person who gets money from the rich and votes from the poor to protect them from each other.
George Barnett wrote:
James Wright wrote:
To see if it is your switch that is causing the problems, you can try using a crossover cable to directly connect two of the computers directly, and see if you can establish some communication. If you can, it is probably your switch. If it is your switch, you can try to find a firmware upgrade that allows IPv6. Or put a second network card in each computer and forget the switch, but using a switch would be much easier to manage.
A switch is a layer 2 device, unless it's capable of routing, which is unlikely in this case. All the switch cares is that a 1500byte packet comes in and is switched to a destination port based on the MAC. It doesn't care if it's IP or IPX or Appletalk or whatever.
Check the arp tables on the boxes and check the subnet masks on the boxes.
As I have mentioned, the ping is being received. The problem is that there's no reply. Given that the ping attempt is seen at the destination, rules out network problems. The situation is as follows Computer A can ping itself and get response. Computer B can ping itself and get response. Computer A can ping B. Ethereal, running on B, shows "Neighbor Solicitation" from A, but does not show any response. Computer A shows "From ::1 icmp_seq=6 Destination unreachable: Address unreachable" A good ping of a computer to itself shows: jknott@linux:~> ping6 -I eth0 fe80::205:5dff:fef6:4ce PING fe80::205:5dff:fef6:4ce(fe80::205:5dff:fef6:4ce) from ::1 eth0: 56 data bytes 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=3 ttl=64 time=0.053 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=4 ttl=64 time=0.050 ms Incidentally, "Neighbor Solicitation" is the IPv6 version of arp request. So, the problem appears to be that the remote system is not responding to the IPv6 version of an arp request.
On Fri, 2005-05-06 at 10:39 -0400, James Knott wrote:
George Barnett wrote: As I have mentioned, the ping is being received. The problem is that there's no reply. Given that the ping attempt is seen at the destination, rules out network problems.
The situation is as follows
Computer A can ping itself and get response. Computer B can ping itself and get response. Computer A can ping B. Ethereal, running on B, shows "Neighbor Solicitation" from A, but does not show any response. Computer A shows "From ::1 icmp_seq=6 Destination unreachable: Address unreachable"
A good ping of a computer to itself shows:
jknott@linux:~> ping6 -I eth0 fe80::205:5dff:fef6:4ce PING fe80::205:5dff:fef6:4ce(fe80::205:5dff:fef6:4ce) from ::1 eth0: 56 data bytes 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=3 ttl=64 time=0.053 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=4 ttl=64 time=0.050 ms
Incidentally, "Neighbor Solicitation" is the IPv6 version of arp request. So, the problem appears to be that the remote system is not responding to the IPv6 version of an arp request.
Check your routing setup. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Fri, 2005-05-06 at 10:39 -0400, James Knott wrote:
George Barnett wrote: As I have mentioned, the ping is being received. The problem is that there's no reply. Given that the ping attempt is seen at the destination, rules out network problems.
The situation is as follows
Computer A can ping itself and get response. Computer B can ping itself and get response. Computer A can ping B. Ethereal, running on B, shows "Neighbor Solicitation" from A, but does not show any response. Computer A shows "From ::1 icmp_seq=6 Destination unreachable: Address unreachable"
A good ping of a computer to itself shows:
jknott@linux:~> ping6 -I eth0 fe80::205:5dff:fef6:4ce PING fe80::205:5dff:fef6:4ce(fe80::205:5dff:fef6:4ce) from ::1 eth0: 56 data bytes 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=3 ttl=64 time=0.053 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=4 ttl=64 time=0.050 ms
Incidentally, "Neighbor Solicitation" is the IPv6 version of arp request. So, the problem appears to be that the remote system is not responding to the IPv6 version of an arp request.
Check your routing setup.
What routing? The computer is receiving the "Neighbor Solicitation" request, but not responding. The computers are sitting on my desk, with only the switch between them. Here's the ifconfig for both systems. eth0 Link encap:Ethernet HWaddr 00:05:5D:F6:04:CE inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::205:5dff:fef6:4ce/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:603728 errors:0 dropped:0 overruns:0 frame:0 TX packets:656548 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:274969413 (262.2 Mb) TX bytes:135805308 (129.5 Mb) Interrupt:10 Base address:0xa800 eth0 Link encap:Ethernet HWaddr 00:00:E2:8A:26:AA inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::200:e2ff:fe8a:26aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5332 (5.2 Kb) TX bytes:5133 (5.0 Kb) And /proc/net/ipv6_route shows 00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 0000002a 80200001 lo fe8000000000000002055dfffef604ce 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 0000009b 80200001 lo fe800000000000000000000000000000 40 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000000 00000000 00000001 eth0 ff000000000000000000000000000000 08 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000000 00000000 00000001 eth0 00000000000000000000000000000000 00 00000000000000000000000000000000 00 00000000000000000000000000000000 ffffffff 00000001 00000006 00200200 lo I don't see any route command info on IPv6.
On Fri, 2005-05-06 at 11:37 -0400, James Knott wrote:
Ken Schneider wrote:
On Fri, 2005-05-06 at 10:39 -0400, James Knott wrote:
Check your routing setup.
What routing? The computer is receiving the "Neighbor Solicitation" request, but not responding. The computers are sitting on my desk, with only the switch between them.
Here's the ifconfig for both systems.
eth0 Link encap:Ethernet HWaddr 00:05:5D:F6:04:CE inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::205:5dff:fef6:4ce/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:603728 errors:0 dropped:0 overruns:0 frame:0 TX packets:656548 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:274969413 (262.2 Mb) TX bytes:135805308 (129.5 Mb) Interrupt:10 Base address:0xa800
eth0 Link encap:Ethernet HWaddr 00:00:E2:8A:26:AA inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::200:e2ff:fe8a:26aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5332 (5.2 Kb) TX bytes:5133 (5.0 Kb)
And /proc/net/ipv6_route shows
00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 0000002a 80200001 lo fe8000000000000002055dfffef604ce 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 0000009b 80200001 lo fe800000000000000000000000000000 40 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000000 00000000 00000001 eth0 ff000000000000000000000000000000 08 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000000 00000000 00000001 eth0 00000000000000000000000000000000 00 00000000000000000000000000000000 00 00000000000000000000000000000000 ffffffff 00000001 00000006 00200200 lo
I don't see any route command info on IPv6.
Still every computer needs a "default" route if it on a network and on linux every machine has two interfaces (if it has a network card or modem), in your case eth0 and lo (the loopback interface). Since the machine can only ping itself it is probably using the lo interface. Just type route -n (as root) for the routing table. The most likely reason that computer "A" can only ping itself but answer ping requests is that the requests will return on the same interface the request was received on but doesn't know where to send the initial request. This is just my guess. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
Still every computer needs a "default" route if it on a network and on linux every machine has two interfaces (if it has a network card or modem), in your case eth0 and lo (the loopback interface). Since the machine can only ping itself it is probably using the lo interface. Just type route -n (as root) for the routing table. The most likely reason that computer "A" can only ping itself but answer ping requests is that the requests will return on the same interface the request was received on but doesn't know where to send the initial request. This is just my guess.
One thing about IPv6, is that it's not supposed to be necessary to configure routing. It's all supposed to happen automagically. Route -n only shows IPv4 routing.
James Knott wrote:
Ken Schneider wrote:
Still every computer needs a "default" route if it on a network and on linux every machine has two interfaces (if it has a network card or modem), in your case eth0 and lo (the loopback interface). Since the machine can only ping itself it is probably using the lo interface. Just type route -n (as root) for the routing table. The most likely reason that computer "A" can only ping itself but answer ping requests is that the requests will return on the same interface the request was received on but doesn't know where to send the initial request. This is just my guess.
One thing about IPv6, is that it's not supposed to be necessary to configure routing. It's all supposed to happen automagically. Route -n only shows IPv4 routing.
Further on this. The problem appears to be happening between 9.2 & 9.1. I just tried between 2 9.2 systems, and ping works. Now to find out how to get applications to work (ssh, browser etc.) over IPv6. tnx
James Knott wrote:
George Barnett wrote:
James Wright wrote:
To see if it is your switch that is causing the problems, you can try using a crossover cable to directly connect two of the computers directly, and see if you can establish some communication. If you can, it is probably your switch. If it is your switch, you can try to find a firmware upgrade that allows IPv6. Or put a second network card in each computer and forget the switch, but using a switch would be much easier to manage.
A switch is a layer 2 device, unless it's capable of routing, which is unlikely in this case. All the switch cares is that a 1500byte packet comes in and is switched to a destination port based on the MAC. It doesn't care if it's IP or IPX or Appletalk or whatever.
Check the arp tables on the boxes and check the subnet masks on the boxes.
As I have mentioned, the ping is being received. The problem is that there's no reply. Given that the ping attempt is seen at the destination, rules out network problems.
The situation is as follows
Computer A can ping itself and get response. Computer B can ping itself and get response. Computer A can ping B. Ethereal, running on B, shows "Neighbor Solicitation" from A, but does not show any response. Computer A shows "From ::1 icmp_seq=6 Destination unreachable: Address unreachable"
A good ping of a computer to itself shows:
jknott@linux:~> ping6 -I eth0 fe80::205:5dff:fef6:4ce PING fe80::205:5dff:fef6:4ce(fe80::205:5dff:fef6:4ce) from ::1 eth0: 56 data bytes 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=3 ttl=64 time=0.053 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=4 ttl=64 time=0.050 ms
Incidentally, "Neighbor Solicitation" is the IPv6 version of arp request. So, the problem appears to be that the remote system is not responding to the IPv6 version of an arp request.
First I apologize for my ignorance about switches. Secondly, here is a troubleshooting list for IPv6 from http://www.cs-ipv6.lancs.ac.uk/ipv6/systems/linux/bieringer/IPv6-HOWTO/IPv6-... that was linked from http://www.cs-ipv6.lancs.ac.uk/ipv6/systems/linux/bieringer/IPv6-HOWTO/IPv6-... I hope this helps. Testing & network Troubleshooting * Make a reboot * Look for correct interface configuration: o ifconfig o Here you should see IPv6 addresses, too. + If not, perhaps you compiled /IPv6/ as module, so do not forget to # Test: lsmod | grep -i ipvg # edit your /etc/conf.modules (or /etc/modules.conf) * Add a line: alias net-pf-10 ipv6 # Load module immediately: modprobe ipv6 + If module is loaded and no IPv6 addresses are displayed (the link local address must be shown without any configuration!): # Perhaps your used set of net-tools is not the one you've compiled for using with IPv6 (perhaps you forgot a "make install"...) * Look for correct IPv6 routing tables: o route -A inet6 o If you get an error, you're using the old only IPv4 ready net-tools set, see ifconfig section for details * Test primitive socket operation (if ping6 has SUID bit not set, you can only use it as root): o Loopback address: + ping6 */::1/* o Link local address: + e.g.: ping6 fe80::2e0:18ff:fe90:9205 + On 2.4.x kernels, you will mostly get an error message like "/connect: Invalid argument/". In this case you have to specify the interface, too, like: # ping6 *-I eth0* fe80::2e0:18ff:fe90:9205 o Other addresses: + ping6 */your-ip6-address/* * If you have problems, look at your interfaces: o tcpdump -i {interface} -t -e Now you can see the link-layer addresses, packet types {ipv6|ip|arp}and {host addresses | resolved hostnames} If tcpdump won't work and you compiled /Paket Socket/ as module, do not forget to + Edit your /etc/conf.modules Add a line: alias net-pf-17 af_packet Load module immediately: modprobe af_packet + o For decoding all of the IPv6 information contained in an IPv6 packet (e.g. autoconfiguration packets), you can also use + tcpdump [-i interface] -vv -s 512 * If you have created IPv6 DNS files you can query the information with: nslookup >set querytype=ANY */>hostname/* Using BIND9 (client utilities), you can also use * o host -n /IPv6-address/ for ip6.int. reverse lookup tests * If name resolution works (by DNS or /etc/hosts) you can test this for IPv4: o ping */your-hostname/* * And now for IPv6: o ping6 -n */your-hostname/* * Start the /Router ADVertisement Daemon/ on one host and look at the others with radvdump for incoming /router advertisements/ * Try now some external addresses: *Protocol / Application* *Full Qualified Domain Name (FQDN)* FTP, traceroute, ping ftp.ipv6.uni-muenster.de WWW www.ipv6.uni-muenster.de
James Wright wrote:
James Knott wrote:
George Barnett wrote:
James Wright wrote:
To see if it is your switch that is causing the problems, you can try using a crossover cable to directly connect two of the computers directly, and see if you can establish some communication. If you can, it is probably your switch. If it is your switch, you can try to find a firmware upgrade that allows IPv6. Or put a second network card in each computer and forget the switch, but using a switch would be much easier to manage.
A switch is a layer 2 device, unless it's capable of routing, which is unlikely in this case. All the switch cares is that a 1500byte packet comes in and is switched to a destination port based on the MAC. It doesn't care if it's IP or IPX or Appletalk or whatever.
Check the arp tables on the boxes and check the subnet masks on the boxes.
As I have mentioned, the ping is being received. The problem is that there's no reply. Given that the ping attempt is seen at the destination, rules out network problems.
The situation is as follows
Computer A can ping itself and get response. Computer B can ping itself and get response. Computer A can ping B. Ethereal, running on B, shows "Neighbor Solicitation" from A, but does not show any response. Computer A shows "From ::1 icmp_seq=6 Destination unreachable: Address unreachable"
A good ping of a computer to itself shows:
jknott@linux:~> ping6 -I eth0 fe80::205:5dff:fef6:4ce PING fe80::205:5dff:fef6:4ce(fe80::205:5dff:fef6:4ce) from ::1 eth0: 56 data bytes 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=3 ttl=64 time=0.053 ms 64 bytes from fe80::205:5dff:fef6:4ce: icmp_seq=4 ttl=64 time=0.050 ms
Incidentally, "Neighbor Solicitation" is the IPv6 version of arp request. So, the problem appears to be that the remote system is not responding to the IPv6 version of an arp request.
First I apologize for my ignorance about switches. Secondly, here is a troubleshooting list for IPv6 from http://www.cs-ipv6.lancs.ac.uk/ipv6/systems/linux/bieringer/IPv6-HOWTO/IPv6-...
that was linked from http://www.cs-ipv6.lancs.ac.uk/ipv6/systems/linux/bieringer/IPv6-HOWTO/IPv6-...
I hope this helps.
tnx As I mentioned in another note, I've found that the problem doesn't occur between two SuSE 9.2 systems. Only between 9.2 and 9.1. I'll have to do some more investigating as to why. However, I can still try further experimenting, but it means that I'll have to use my notebook as the 2nd system, since it has 9.2 installed.
What does one do (to modules.conf?) to turn off IPv6 completely? In a world that expects IPv4 it's a complete nuisance. For example I get DNS secondaries that can't get a zone transfer. Turns out they are connecting through IPv6 so of course their address doesn't fit the access list of IPv4 addresses allowed. This has already been covered but I can't find the post, michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 Internet Explorer is fine for downloading Firefox, but after that....
On Monday 09 May 2005 03:24, Michael James wrote:
What does one do (to modules.conf?) to turn off IPv6 completely?
In a 2.4 kernel system you would put alias ipv6 off in modules.conf In a 2.6 kernel system you would put install ipv6 /bin/true in modprobe.conf.local Don't forget to run "depmod -a" afterwards. Also, you may have to reboot the system, since it's rather difficult to unload the ipv6 module
Michael James wrote:
For example I get DNS secondaries that can't get a zone transfer. Turns out they are connecting through IPv6 so of course their address doesn't fit the access list of IPv4 addresses allowed.
Another way to fix this is to simply configure named to not use ipv6 even if it's loaded. listen-on-v6 { none; };
James Wright wrote:
James Wright wrote:
James Knott wrote:
Alan Hughes wrote:
James Knott wrote:
I've decided to try experimenting with IPv6. I can ping the interface on the computer, but nothing on my network. I assume the address listed in ifconfig should be available over the lan. Ethereal, at the far end, shows ICMPv6 Neighbor solicitations being received, but no response being sent. Ping6 says "Destination unreachable: Address unreachable". Is there something else required to enable this? Also, how does one get the apps, such as a browser or ssh to work with an IPv6 address?
tnx jk
Is anything else on your network configured to support IPv6? Do you have an IPv6 router? IPv4 protocol stacks will not respond to an IPv6 ping (or anything else).
It's just a local network. All computers involved are sitting on my desk, to there's only the switch to worry about. As I mentioned in other notes, the computers receive the ping, but don't respond. This is shown by ethereal. They do respond to their own pings. All systems are running SuSE 9.2 or 9.1, which support IPv6.
But are you sure your switch can handle the IPv6? If your switch is not IPv6 enabled, I doubt that you will get it to work. - James W.
To see if it is your switch that is causing the problems, you can try using a crossover cable to directly connect two of the computers directly, and see if you can establish some communication. If you can, it is probably your switch. If it is your switch, you can try to find a firmware upgrade that allows IPv6. Or put a second network card in each computer and forget the switch, but using a switch would be much easier to manage.
Switches don't care about IPv4, IPv6, IPX NetBIOS etc. They only forward ethernet frames, ignoring higher protocols. Also, the "Neighbor Solicitation" packet is being received at the destination.
James Wright wrote:
It's just a local network. All computers involved are sitting on my desk, to there's only the switch to worry about. As I mentioned in other notes, the computers receive the ping, but don't respond. This is shown by ethereal. They do respond to their own pings. All systems are running SuSE 9.2 or 9.1, which support IPv6.
But are you sure your switch can handle the IPv6? If your switch is not IPv6 enabled, I doubt that you will get it to work. - James W.
Swtiches are transparent to IP or any other protocol. The only forward ethernet packets, without regard to higher level protocols. And yes, ethereal shows the "Neighbor Solicitation" packet being received at the destination computer. The problem is that the destination computer is not responding.
participants (7)
-
Anders Johansson -
George Barnett -
James Knott -
James Wright -
Ken Schneider -
mb1-knetdome -
Michael James