Click to See Complete Forum and Search --> : IPv6 killed my dsl - suggestions?


lazarus777
06-26-2004, 09:46 AM
So I was working away online the other day, and went to take a nap - woke up, and all of a sudden, could not connect to anything. After browsing various logs and googling alot, it would appear that my computer decided that no matter what I want, it wants to run IPv6 - only problem with this, is it would seem my dsl provider doesn't support it (or I am missing something simple).

some messages from /var/log/messages from a fresh reboot right around the time this started happening -



Jun 23 08:42:28 Lazarus kernel: eth0: VIA VT6102 Rhine-II at 0xe800, 00:40:63:ca:9a:15, IRQ 11.
Jun 23 08:42:28 Lazarus kernel: eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
Jun 23 08:42:28 Lazarus kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.

Jun 23 08:42:31 Lazarus kernel: IPv6 v0.8 for NET4.0
Jun 23 08:42:31 Lazarus kernel: IPv6 over IPv4 tunneling driver
Jun 23 08:42:42 Lazarus kernel: eth0: no IPv6 routers present
Jun 23 08:42:49 Lazarus kernel: PCI: Setting latency timer of device 00:11.5 to 64



lsmod shows the ipv6 module loaded - when I try to unload it, I get this:

Lazarus:~ # modprobe -r ipv6
ipv6: Device or resource busy
Lazarus:~ # rmmod ipv6
ipv6: Device or resource busy


any ideas/help/links to something simple I missed would be greatly appreciated.


a largish number of these are showing up in various logs as well, I do not know if it is related, but anything is possible I suppose -

Jun 24 02:51:10 Lazarus kernel: eth0: Oversized Ethernet frame c2261000 vs c2261000.

XiaoKJ
06-26-2004, 11:13 AM
try giving us the output of ifconfig

then try rebooting your router or modem or whatever, if it has its own power.

those aren't telling you that you can't run ipv6, just that it can't find ipv6 compliant routers anywhere.

lazarus777
06-27-2004, 11:37 PM
thanks for suggestions - I had tried resetting the dsl modem a couple times already, gave it another go anyhow, no luck :)

any other thoughts/suggestions would be appreciated... I am not a huge fan of using my dialup backup :)


Lazarus:/var/log # ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:63:CA:9A:15
inet6 addr: fe80::240:63ff:feca:9a15/10 Scope:Link
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:1 dropped:1 overruns:0 frame:19857
TX packets:4693 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:2758510 (2.6 Mb)
Interrupt:11 Base address:0xe800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:47164 errors:0 dropped:0 overruns:0 frame:0
TX packets:47164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3301676 (3.1 Mb) TX bytes:3301676 (3.1 Mb)

Lazarus:/var/log # ifstatus eth0
dhcpcd running
eth0 not up

XiaoKJ
06-28-2004, 03:44 AM
do you have a home network? I.E. your ip address falls between 192.168.x.x or 10.x.x.x or something like that?

if so, try manually setting an ip for a while.

ifconfig eth0 192.168.0.2 up

maybe your new settings prohibit DHCP to enter your computer, instead of ipv6 which should do no harm. if your system cannot handle IPv6 it will just take up some memory and do nothing.

lazarus777
06-28-2004, 03:51 AM
my home network is on a separate switch - this is just this computer and dsl connection (which used to work), which isn't working, and shouldn't be using ipv6 in the first place :P no clue how it happened, and cannot get dsl to work now.

JohnT
06-28-2004, 04:17 AM
What distro are you using? Have you a recompiled kernel?

XiaoKJ
06-28-2004, 04:28 AM
I would like to state again that IPv6 would not have destroyed your connection.

try putting it on the home network as you know whether it works.

lazarus777
06-28-2004, 05:41 AM
running SuSE 8.1.. and have not recompiled kernel recently.

ok, if ipv6 did not kill it (altho that is only thing i can see in logs that changed) do you have suggestions on what might have? dsl provider swears up and down it's not a problem with my line or anything on their end.

and i would rather not put it on my home network - i have no interest in playing with ipv6 whatsoever, just wanna get silly dsl working again :)

XiaoKJ
06-28-2004, 08:11 AM
I mean, if you put it in your home network, you know for sure what is the problem -- your home network is definitely up isn't it?

I suggest you put it there for a while and test if you can go online, and be sure all other computers on the network can too.

If you couldn't, check the ip address of the box -- best if windows -- you can see the automatic private ip which is a definite no-no. In linux just see that the machine keeps saying those things like broadcast for DHCP...

once I had to manually set eth0 to 192.168.10.3 so that it can get on the net...

ifconfig eth0 192.168.10.3 up

and it was ok. in windows I had to set the alternate config to 192.168.10.20 to get a temporary line before I could even get on the network. I did this, then I could repair the line for a DHCP lease.

If you can see, I am very determined that IPv6 is not your problem, and I am sure that firewall or something did it.

BTW, as I have mentioned, and I am very naggy I know :D, IPv6 just turns off if it can't find a IPv6 address and will assign itself one. It will stay dormant untill something works...

XiaoKJ
06-28-2004, 08:19 AM
Oh, and your avatar is nice... :D linux instead, is not a bug like pentium is :D

hard candy
06-28-2004, 08:19 AM
I would do these first:
1. Check all the connections
2. Reinstall the ethernet card driver
3. Check in Suse's equivalent of /etc/resolv.conf and see if any DNS servers are listed.
3. If still no go, try a different ethernet card