LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 11-06-2003, 04:23 AM   #1
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Rep: Reputation: 15
I Give Up; Linux Just Isn't Ready For Primetime


Got you didn't I? Well, that's just about how I feel now. I'm running Mandrake 9.1, and my LAN won't work. I've tried both dynamic and static IPs. I've configured my network six times(three times each for DHCP and static)in total; I've used drakconnect, and it didn't work. I've tried ifconfig, and it didn't work. I've edited the relevant .conf files, and they didn't work. So WTF am I supposed to do now? I'm using a CNet(some cheap brand from Taiwan. Don't ask me to change it; I'm not the one in charge of hardware)router. My assigned IP address should be 192.168.1.4, although dynamic IPs are acceptable, and indeed, preferred. My router's IP is 192.168.1.1. Can anyone help me?
 
Old 11-06-2003, 04:37 AM   #2
ashjam10
Member
 
Registered: Sep 2003
Location: UK
Distribution: Mandrake 10.0
Posts: 121

Rep: Reputation: 15
Have you tried disabling iptables on your mandrake machine?
 
Old 11-06-2003, 04:43 AM   #3
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Original Poster
Rep: Reputation: 15
Iptables? Never heard of them. Enlighten me please. I'm just a .
 
Old 11-06-2003, 04:51 AM   #4
ashjam10
Member
 
Registered: Sep 2003
Location: UK
Distribution: Mandrake 10.0
Posts: 121

Rep: Reputation: 15
I'm afraid I don't know how to go about disabling iptables in Mandrake as I've not gotten round to installing it yet. I'm still a newbie myself, had Red Hat on my PC for a couple of weeks before I had to lend someone the drive for a bit.

Anyway, you should be able to bring up a list of services and from there you should be able to deactivate iptables. I'm sure someone else here could tell you how to do it from the terminal, but until they do perhaps you could try looking around in the control centre... there must be a list of services in there somewhere. Iptables is a firewalling system, this may be blocking your access to the internet.
 
Old 11-06-2003, 04:55 AM   #5
robartes
Member
 
Registered: Oct 2003
Location: Mechelen, BE
Distribution: Mandrake as base, most software hand rolled
Posts: 80

Rep: Reputation: 15
Re: I Give Up; Linux Just Isn't Ready For Primetime

Quote:
Originally posted by johnleemk
Got you didn't I? Well, that's just about how I feel now. I'm running Mandrake 9.1, and my LAN won't work. I've tried both dynamic and static IPs. I've configured my network six times(three times each for DHCP and static)in total; I've used drakconnect, and it didn't work. I've tried ifconfig, and it didn't work. I've edited the relevant .conf files, and they didn't work. So WTF am I supposed to do now? I'm using a CNet(some cheap brand from Taiwan. Don't ask me to change it; I'm not the one in charge of hardware)router. My assigned IP address should be 192.168.1.4, although dynamic IPs are acceptable, and indeed, preferred. My router's IP is 192.168.1.1. Can anyone help me?
What does not work *exactly*? What error messages do you get? Do you see the interface with ifconfig ...

To start with, post the output from ifconfig -a and netstat -rn .
 
Old 11-06-2003, 04:56 AM   #6
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
Just to see if you can get it working, log in as root in a shell to avoid any path problems:

su -

<then enter password>

then enter:

iptables -F

iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT

ifconfig eth0 192.168.1.4

make sure no other computer has this IP address

then do

ifconfig

to see if it has accepted this IP address

If there's nothing for eth0 at all after doing ifconfig then you'll have to get your card going/recognised if it has try and ping the router or another computer
 
Old 11-06-2003, 06:50 AM   #7
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Original Poster
Rep: Reputation: 15
I will boot into my Mandrake partition later; thanks for the help guys. My particular problem was being unable to ping other computers or the router itself; either I was told the network was unavailable, or the destination was unreachable. I'll inform you on my progress ASAP; hopefully from my Linux machine itself.
 
Old 11-06-2003, 07:12 AM   #8
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Original Poster
Rep: Reputation: 15
It still failed. At least ifconfig outputted something. I cannot ping other computers or the router; I am told the destination was unreachable. I would post the output of ifconfig -a and netstat -rn, but apparently KWrite didn't save them correctly on my Windows drive; the files never showed up. I'll have to boot again into Linux and save the files to a floppy I guess.
 
Old 11-06-2003, 07:57 AM   #9
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
Remember as well if you do have a firewall on Mandrake and it hasn't been disabled everytime you reboot it'll go back to what it was before

iptables --list

will show you what you've got

Check you can ping the actual interfaces on Mandrake whilst using it

ping 127.0.0.1

and

ping 192.168.1.4

Also maybe a wee bit obvious but try a cable that you know for sure is working

The more details from the output of commands such as route -n and ifconfig et.c that you post , the more people will be able to help, no guarantees on success of course

Double check that you're routers ip really is 192.168.1.1 , although there's no reason to doubt constantly reviewing things does no harm.
 
Old 11-06-2003, 08:01 AM   #10
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Original Poster
Rep: Reputation: 15
Thanks, Looking_Lost. I've had this hardware for a few months already, and I'm pretty comfortable with it, as well as sure that it's not the hardware's problem. The cables work fine; I'm just dual-booting; this machine was running Linux ten minutes ago. I got the output at last:
Code:
ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:08:A1:1B:67:B5
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:5493 (5.3 Kb)  TX bytes:8119 (7.9 Kb)
          Interrupt:11 Base address:0x9400

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:493 errors:0 dropped:0 overruns:0 frame:0
          TX packets:493 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:32748 (31.9 Kb)  TX bytes:32748 (31.9 Kb)
Code:
netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 eth0
 
Old 11-06-2003, 08:19 AM   #11
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
Well, that looks fine.

I guess when you boot in Windows everything is fine, yeah? (Assuming you are dual-booting with windows) You can use the internet , ping the router as well as other computers on the Lan?

Even though you probably can you can ping 127.0.0.1 and 192.168.1.4 while actually on the Mandrake computer just confirm

and what's the output of

iptables --list

immediately after you've booted Mandrake

 
Old 11-06-2003, 08:36 AM   #12
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Original Poster
Rep: Reputation: 15
Will do. I'm wondering about netstat's output, however. Shouldn't 192.168.1.1 correspond as a gateway to the destination of 192.168.1.0?
 
Old 11-06-2003, 08:44 AM   #13
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
No, for all ip's in the same subnet/wire setting a gateway shouldn't be necessary although
you will need it to get outside your own network.

Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

this says I am on the 192.168.1.0 network and I should be able to talk directly to any other
computers in the same ip range that I have a direct physical path too, although not in so many words. No other computers are having any problems I assume.
 
Old 11-06-2003, 08:54 AM   #14
johnleemk
Member
 
Registered: Sep 2003
Location: Malaysia
Distribution: Slackware 9.1
Posts: 145

Original Poster
Rep: Reputation: 15
This is the output I got:
Code:
iptables --list
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
detect_in  all  --  anywhere             anywhere
eth0_in    all  --  anywhere             anywhere
common     all  --  anywhere             anywhere
LOG        all  --  anywhere             anywhere           LOG level info prefix `Shorewall:INPUT:REJECT:'
reject     all  --  anywhere             anywhere

Chain FORWARD (policy DROP)
target     prot opt source               destination
detect_fwd  all  --  anywhere             anywhere
eth0_fwd   all  --  anywhere             anywhere
common     all  --  anywhere             anywhere
LOG        all  --  anywhere             anywhere           LOG level info prefix `Shorewall:FORWARD:REJECT:'
reject     all  --  anywhere             anywhere

Chain OUTPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     icmp --  anywhere             anywhere
fw2net     all  --  anywhere             anywhere
fw2masq    all  --  anywhere             anywhere
common     all  --  anywhere             anywhere
LOG        all  --  anywhere             anywhere           LOG level info prefix `Shorewall:OUTPUT:REJECT:'
reject     all  --  anywhere             anywhere

Chain all2all (2 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
newnotsyn  tcp  --  anywhere             anywhere           state NEW tcp flags:!SYN,RST,ACK/SYN
common     all  --  anywhere             anywhere
LOG        all  --  anywhere             anywhere           LOG level info prefix `Shorewall:all2all:REJECT:'
reject     all  --  anywhere             anywhere

Chain common (5 references)
target     prot opt source               destination
icmpdef    icmp --  anywhere             anywhere
DROP       tcp  --  anywhere             anywhere           state INVALID
REJECT     udp  --  anywhere             anywhere           udp dpts:netbios-ns:netbios-ssn reject-with icmp-port-unreachable
REJECT     udp  --  anywhere             anywhere           udp dpt:microsoft-ds reject-with icmp-port-unreachable
reject     tcp  --  anywhere             anywhere           tcp dpt:135
DROP       udp  --  anywhere             anywhere           udp dpt:1900
DROP       all  --  anywhere             255.255.255.255
DROP       all  --  anywhere             224.0.0.0/4
reject     tcp  --  anywhere             anywhere           tcp dpt:auth
DROP       all  --  anywhere             192.168.1.255

Chain detect_fwd (1 references)
target     prot opt source               destination
dynamic    all  --  anywhere             anywhere
net2all    all  --  anywhere             anywhere

Chain detect_in (1 references)
target     prot opt source               destination
dynamic    all  --  anywhere             anywhere
net2all    all  --  anywhere             anywhere

Chain dynamic (4 references)
target     prot opt source               destination

Chain eth0_fwd (1 references)
target     prot opt source               destination
dynamic    all  --  anywhere             anywhere
masq2net   all  --  anywhere             anywhere

Chain eth0_in (1 references)
target     prot opt source               destination
dynamic    all  --  anywhere             anywhere
masq2fw    all  --  anywhere             anywhere

Chain fw2masq (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
newnotsyn  tcp  --  anywhere             anywhere           state NEW tcp flags:!SYN,RST,ACK/SYN
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:ipp
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:printer
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:netbios-ns
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:netbios-dgm
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:netbios-ssn
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:ipp
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:printer
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:netbios-ns
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:netbios-dgm
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:netbios-ssn
all2all    all  --  anywhere             anywhere

Chain fw2net (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
newnotsyn  tcp  --  anywhere             anywhere           state NEW tcp flags:!SYN,RST,ACK/SYN
ACCEPT     all  --  anywhere             anywhere

Chain icmpdef (1 references)
target     prot opt source               destination

Chain masq2fw (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
newnotsyn  tcp  --  anywhere             anywhere           state NEW tcp flags:!SYN,RST,ACK/SYN
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:domain
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:bootps
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:http
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:https
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:ipp
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:imap
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:pop3
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:smtp
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:nntp
ACCEPT     tcp  --  anywhere             anywhere           state NEW tcp dpt:ntp
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:domain
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:bootps
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:http
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:https
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:ipp
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:imap
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:pop3
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:smtp
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:nntp
ACCEPT     udp  --  anywhere             anywhere           state NEW udp dpt:ntp
all2all    all  --  anywhere             anywhere

Chain masq2net (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
newnotsyn  tcp  --  anywhere             anywhere           state NEW tcp flags:!SYN,RST,ACK/SYN
ACCEPT     all  --  anywhere             anywhere

Chain net2all (2 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
newnotsyn  tcp  --  anywhere             anywhere           state NEW tcp flags:!SYN,RST,ACK/SYN
common     all  --  anywhere             anywhere
LOG        all  --  anywhere             anywhere           LOG level info prefix `Shorewall:net2all:DROP:'
DROP       all  --  anywhere             anywhere

Chain newnotsyn (6 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere

Chain reject (6 references)
target     prot opt source               destination
REJECT     tcp  --  anywhere             anywhere           reject-with tcp-reset
REJECT     all  --  anywhere             anywhere           reject-with icmp-port-unreachable

Chain shorewall (0 references)
target     prot opt source               destination
And yes, for all other computers, everything is fine.
 
Old 11-06-2003, 09:07 AM   #15
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
Holy, schmoly! Houston we have a problem!! That must qualify for most iptables rules of the year award or at least it must come a close second!!!

Get rid of that firewall I'm not even going to attempt to interpret it all



I notice it's saying shorewall on it which I'm not familiar with but either way take the time to find out how to completely clear out your iptables and leave them deactivated on Mandrake, unfortunately I don't have the info off hand as I don't use it, but I'd put money on this being your problem as was originally suggested at the start of the thread. You'll get there, you're probably one simple step away, so just a little more patience
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
BSD=not ready for primetime dhlawrence *BSD 3 08-03-2005 09:41 PM
Almost ready to give up!! :( tecnolover Mandriva 24 02-27-2005 12:46 AM
HELP!! I ready to give up on Linux Wolfy Linux - Newbie 104 07-15-2004 07:56 PM
That is it, I give up, Linux is truely not ready for prime time.... MAWipf General 175 11-10-2003 05:42 AM
Can't add hard drive- simple task- about ready to give up linux saxblue Linux - Hardware 4 07-30-2003 12:23 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 09:09 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration