Connecting to Internet with new DSL

benrose111488 · 09-12-2006, 07:19 PM

Hello all... I recently upgraded from dial-up to 4.0 Cable after 17 years! allright! BUT - I can't connect in Linux! This machine dual-boots, so I'm in Windows now, which (as you can see) connects just fine. output of "ifup eth0" produces "RTNETLINK: Invalid Argument". I did my research, and read that this is the result of the kernel being compiled without the CONFIG_IP_MULTIPLE_TABLES flag set as true.

Now, up until this point, I've been using the generic Yum RPM's to update my kernel. Dunno if that's frowned upon, but it's always worked, so I've always done it. Regardless, does this mean I have to compile a kernel for myself? Can this be modified without recompiling my kernel?

If I must compile a kernel, can someone provide me with the generic file that a config would produce (or the file used by the yum RPM maintainers)?

Thanks in advance

benrose111488 · 09-12-2006, 07:38 PM

Oop. Interesting. In /usr/src/kernels/mykernelversion/.config I found the following code:

Code:

CONFIG_IP_MULTIPLE_TABLES=y

So this sets me back to step one... this may not be a problem with my kernel, but I can't get online! I know the modem works... I'm using it in Windows right now.

Any ideas?

BogusTrumper · 09-12-2006, 11:55 PM

You're connecting using Ethernet, right? Some cable modems connect with USB... just making sure you're not doing that. Otherwise, try running "dhclient eth0"; that might give you some more success. Just for curiosity's sake, how were you using yum before? Over dial-up? Is this a custom kernel, or do you use standard versions?

benrose111488 · 09-13-2006, 11:39 AM

yup, over ethernet.

this is a standard kernel, downloaded over dial-up from yum.

dhclient is called by ifup, when called seperately, this is the error it reports.

BogusTrumper · 09-14-2006, 10:56 AM

OK.

So do you get this when you try to use ifup, or do you get this at boot as well? Do you get any messages about eth0 at boot? Also, thinking backwards, did you have to alter any config settings to use dialup, or was that done at install time?

J.W. · 09-14-2006, 12:17 PM

What specific NIC (make/model) are you using, and what is the output from

Code:

lsmod
ifconfig

The first command will list the kernel modules that have been loaded, and the second will display some basic info about your connection. Lastly, do you have both an onboard LAN as well as a NIC? If so, try disabling the onboard through BIOS

benrose111488 · 09-14-2006, 05:58 PM

Well, I think I half solved the problem. I was reading some posts online about this exact matter, and they all seemed to say you need to load some more kernel modules or recompile your kernel. So I ended up loading the following modules, regardless of whether or not I need them:

Code:

sch_htb
sch_sfq
sch_ingress
cls_fw
cls_u32

This still did not work. I was looking at the kernel routing table, which read:

Code:

[root@Darkflame ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
70.44.84.0      *               255.255.252.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0

So I ran "route add default gw 70.44.84.0 eth0" and what would you know, it worked! However, now when I try to connect to websites, I can't due to reason: Lack of buffer space available. This happens if I use more than one internet program, and is extremely annoying. I did some research on this, and it turns out that this may be caused by a messed up kernel routing table. Funny how that works out =P.

So maybe someone can help me resolve this matter... I'm not sure I did the routing correctly... here's the output that you requested:

lsmod:

Code:

[root@Darkflame ~]# lsmod
Module                  Size  Used by
sch_htb                21825  0
sch_sfq                10177  0
sch_ingress             8773  0
cls_fw                  9537  0
cls_u32                12613  0
joydev                 14081  0
analog                 16001  0
parport_pc             32428  1
lp                     17153  0
parport                41993  2 parport_pc,lp
autofs4                26181  1
sunrpc                168421  1
nls_utf8                6337  2
ntfs                  220564  1
dm_mod                 65749  0
video                  21829  0
button                 11089  0
battery                14789  0
ac                      9157  0
nvidia               4562324  12
ipv6                  269761  148
usblp                  18881  0
ohci_hcd               26461  0
amd76x_edac             8385  0
edac_mc                18701  1 amd76x_edac
i2c_amd756             10949  0
i2c_core               26817  2 nvidia,i2c_amd756
emu10k1_gp              8129  0
gameport               20553  3 analog,emu10k1_gp
snd_emu10k1_synth      11969  0
snd_emux_synth         40129  1 snd_emu10k1_synth
snd_seq_virmidi        12225  1 snd_emux_synth
snd_seq_midi_emul      10689  1 snd_emux_synth
snd_emu10k1           128965  5 snd_emu10k1_synth
snd_rawmidi            30145  2 snd_seq_virmidi,snd_emu10k1
snd_ac97_codec         99041  1 snd_emu10k1
snd_ac97_bus            6593  1 snd_ac97_codec
snd_seq_dummy           8133  0
snd_seq_oss            38565  0
snd_seq_midi_event     11841  2 snd_seq_virmidi,snd_seq_oss
snd_seq                60845  8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul ,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss            44625  0
snd_mixer_oss          22465  2 snd_pcm_oss
snd_pcm                90309  4 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device         13261  7 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd _rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer              29381  3 snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc         15049  2 snd_emu10k1,snd_pcm
snd_util_mem            9665  2 snd_emux_synth,snd_emu10k1
snd_hwdep              14149  2 snd_emux_synth,snd_emu10k1
snd                    60737  18 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd _seq_device,snd_timer,snd_hwdep
soundcore              14241  2 snd
e1000                 118073  0
e100                   41285  0
mii                     9793  1 e100
floppy                 65597  0
ext3                  141769  1
jbd                    65365  1 ext3

ifconfig:

Code:

[root@Darkflame ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:E0:81:28:06:D3
          inet addr:70.44.85.154  Bcast:255.255.255.255  Mask:255.255.252.0
          inet6 addr: fe80::2e0:81ff:fe28:6d3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10796536 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9912791 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3647612184 (3.3 GiB)  TX bytes:3773727606 (3.5 GiB)

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:129684 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129684 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:44609247 (42.5 MiB)  TX bytes:44609247 (42.5 MiB)

[root@Darkflame ~]#

and for good measure, route thrown in, as this may be the problem:

Code:

[root@Darkflame ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         70.44.85.154.re 255.255.252.0   UG    0      0        0 eth0
70.44.84.0      *               255.255.252.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         70.44.85.154.re 0.0.0.0         UG    0      0        0 eth0
[root@Darkflame ~]#

Thank you guys so much for helping me. I truly appreciate it. I simply can't believe that when I called my cable company, they told me to call the service provider, and when I called them, they said that they "unofficially" support Linux, which is another way of them saying, "hey, some people have gotten it to work with Linux, so we'll advertise that it works with it, but we won't tell you how to make it work!"

BTW: forgot to mention that now when i run ifup eth0, there are no errors. There are also no more errors on boot. Odd.

[EDIT]Both eth0 and eth1 are onboard Intel network adapters, on the Tyan S2469 motherboard. I believe they are the IntelPRO 100/1000 MS/MT or something like that. I have never had a problem using them in Linux before.[/EDIT]

Again, thank you very much!

J.W. · 09-15-2006, 12:01 AM

Cool - I'll take it that the problem has been resolved, so congrats benrose111488 on solving the problem, and many thanks for posting back with the solution that worked for you

benrose111488 · 09-15-2006, 04:04 PM

Fully solved now! I originally said load the modules, then add the IP in route as default gw. This only half-fixes the problem.

Where it says in the route that a destination is "70.44.84.0", simply take the last number and add one.

So the command would be "route add default gw 70.44.84.1 eth0". The reason the socket was having problems was an IP address conflict on the network. This 100% solves the problems. I'm not even sure that those modules stated above need to be loaded - I haven't restarted yet to test it.

Hope this helps someone eventually!