networking qn's Slack specific

egag · 07-19-2005, 06:17 PM

all settings there look ok to me.
did you check the resolv.conf file and try it ?
should work...

egag

aikidoist72 · 07-19-2005, 06:53 PM

Yes. Everything should be right. This is why I am wondering if there is another setting I should be looking at regarding security and firewall within the router. The router has a Linux kernel in it

So it has got to be good!!!!!

I have reset the modem to original settings, and then re-entered everything relevant. Could these filters be the issue? If all settings are correct, I will play until I can get access.

gbonvehi · 07-19-2005, 08:20 PM

Ping uses another protocol, but actually it's not a protocol problem.
To connect to somewhere using a name, like linuxquestions.org you've to know the IP address. To do that, there are DNS servers, which provide a table of associated names with IP numbers.
The problem seems your Linux box not using a DNS server (or nameserver) to resolve the IP, you could surf the web using only IP numbers (it's a ugly thing, I experienced it).

aikidoist72 · 07-19-2005, 10:14 PM

Oh

What if the nameserver value was my ISP's primary dns or second dns.

What really hurts is that the modem settings are in place and I am using Xp on the kiddies computer to do this. So the modem must work using static ip address' but my problem is within Slackware. Could it be a kernel option preventing this?

Thanks for all your replies. I am beggining to get an understanding of what I need to do with my setup.

Cheers

Namaseit · 07-19-2005, 11:29 PM

on your xp machine see what the dns servers are. (bear with me while I try to remember how to do this). Open 'My Network Places' then 'View Network Connections' then double click on your network interface and it will bring up a window with 2 tabs. Click the one that says support at the top. Then click 'Details' and listed you should see all the info that is set for the interface. At the bottom of the list you'll see 'DNS Servers'. If its set to something besides 10.1.1.1(probably is) then write these down. Now on your slack box open /etc/resolv.conf and instead of 'nameserver 10.1.1.1' change it to 'nameserver <whatever>' newline 'nameserver <whatever>'. There's usually 2 nameservers given by ISP's. If you look on your modem configuration page you might find something that lists the interface it might also show what it has for dns servers listed in there as well.

aikidoist72 · 07-20-2005, 01:53 AM

SUCCESS !!!!!!!!!!!!!!!!!!!!!

Whilst compiling my kernel I noticed that ipv4 had nat support for a few items

Code:

CC      net/ipv4/netfilter/ip_nat_helper.o
  CC      net/ipv4/netfilter/ip_nat_proto_unknown.o
  CC      net/ipv4/netfilter/ip_nat_proto_tcp.o
  CC      net/ipv4/netfilter/ip_nat_proto_udp.o
  CC      net/ipv4/netfilter/ip_nat_proto_icmp.o

I decided to check my modules. Down the bottom of /etc/rc.d/rc.modules I found

Code:

#IPV6 over IPV4
/sbin/modprobe ipv6

Once I commented this line out, I had full access as a static ip 10.1.1.2 Now The only issue I have is I need to issue

Code:

/etc/rc.d/rc.inet1 restart

in order to get internet access. What else can I do instead of adding this to rc.local??

Thanks everyone for your help. I reakon I can study some networking sites with a little more understanding

Cheers

keefaz · 07-20-2005, 02:30 AM

There is no restart argument for the /etc/rc.d/rc.inet1 script

If I run /etc/rc.d/rc.inet1 restart on my system, that does nothing...

aikidoist72 · 07-20-2005, 03:02 AM

Hi Keefas

You are right! When my system starts up I do not have an internet connection.
if I

Code:

/ect/rc.d/rc.inet1

that also works. So what calls rc.inet1 at startup?

keefaz · 07-20-2005, 03:15 AM

/etc/rc.d/rc.M starts rc.inet1 at boot if rc.inet1 is executable.
(You shouldn't have to run rc.inet1 by hand)

Did you try to compare /sbin/ifconfig -a output before and
after you run rc.inet1 script ?

(Also run /etc/rc.d/rc.inet1 without argument does nothing too)

aikidoist72 · 07-20-2005, 03:52 AM

Good call

before

Code:

eth0      Link encap:Ethernet  HWaddr 00:01:80:36:5D:E0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:22 Base address:0x2000

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:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:100 (100.0 b)  TX bytes:100 (100.0 b)

sit0      Link encap:UNSPEC  HWaddr 00-00-00-00-31-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

after

Code:

eth0      Link encap:Ethernet  HWaddr 00:01:80:36:5D:E0
          inet addr:10.1.1.2  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::201:80ff:fe36:5de0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:308 (308.0 b)
          Interrupt:22 Base address:0x2000

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:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:100 (100.0 b)  TX bytes:100 (100.0 b)

sit0      Link encap:UNSPEC  HWaddr 00-00-00-00-31-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

keefaz · 07-20-2005, 04:26 AM

I still don't understand why your rc.inet1 is not called by rc.M at boot...

Maybe you should try to set DEBUG_ETH_UP="yes" in rc.inet1.conf
then reboot and look output with dmesg | most

aikidoist72 · 07-20-2005, 04:40 AM

Could it be that I built my 8139too driver into the kernel instead of being a module? I am recompiling now so I will tell you soon.

keefaz · 07-20-2005, 05:06 AM

I don't think it is related if the netcard driver is a module or not
from what I read in rc.M script

Also I said that execute rc.inet1 without argument does nothing...
It is not true, I just see the default label *) which mean that
by default rc.inet1 will bring up all interfaces

So execute /etc/rc.d/rc.inet1 without argument or as
/etc/rc.d/rc.inet1 restart is technically correct, but the
restart option won't really restart interfaces settings
You have to do /etc/rc.d/rc.inet1 stop followed by a
/etc/rc.d/rc.inet1 start

aikidoist72 · 07-20-2005, 06:07 AM

That makes more sense. When switching from dhcp to static and back, I used the stop start switch. I used restart only at boot because I thought it had been called by rc.inetd during boot.

Now I have compiled the 8139too as a module. Start up is error free and the network is up automatically.