streeter

According to ifconfig, the network IS up, and has been assigned an IP address...

Try pinging eth0 from the same machine, then pinging the other machine.

Post output of route -n

Have a look at the pinned post at the top of the networking forum for a howto.

Chris

Are you starting networking on boot?

Type drakxservices as root (or go to system->services in the control centre) and make sure network is being run at startup.

If it is:

What make/model of card is it?

Is the module getting loaded? (type lsmod and look for the module name - if unsure, we can tell you from the card type)

Output of ifconfig before network is started

Chris

That should be ONBOOT=yes

See man ifcfg

Chris

You need to set the default gateway to the device you wish to use.

To view the routing table, type route -n

If you look at this when on/off line you should see what's happening.

To change the default gateway manually, use

route add default gw <ip address> <interface>

So for eth0 with a gateway of 192.168.0.1, use route add default gw 192.168.0.1 eth0

For dial up, it gets set automatically, but you may find you need to remove the current default gateway first with

route del default

This can be entered in the kppp pre-dialup code box as

kdesu route del default

if you need it.

To stop eth0 taking over the gateway, remove the line GATEWAY=xxx.xxx.xxx.xxx in /etc/sysconfig/network.

I think there may be a graphical way to do all this using profiles - anyone?

You could also write a script to do the job.

All commands to be entered as root.

Chris

Glad it's sorted!

The gateway is dynamic - it will change each time you dial up, and gets set in the routing table after you dial up - to see what happens, type

route -n

before and after dialling.

Chris

For dial-up, you don't want an initial gateway address set up on PC1 - this will get set automatically when you dial up, so remove the GATEWAY= line in /etc/sysconfig/network.

For the rest have a look at my ICS with a modem howto :http://www.iwpcs.co.uk/ics_modem.html

for PC1

and the simple net setup at http://www.iwpcs.co.uk/simple_net_setup.html for the client.

You can create a new (empty) /etc/sysconfig/network-scripts/ifcfg-eth0 with

touch /etc/sysconfig/network-scripts/ifcfg-eth0
chmod 766 /etc/sysconfig/network-scripts/ifcfg-eth0

Follow the howtos through - if it still doesn't work, there are a couple of commands at the bottom. Post the results of these here, and we can help more. If you are unsure about any of it, or it is unclear, let me know so I can improve it!

Good luck!

When you say the DHCP server assigns an address, are you getting this information from the DHCP server itself, or from the client?

Could this be a speed/duplexing auto-negotiation problem?

Try

mii-tool -F 100baseTx-FD eth0

(or one of the options, depending on whether you have 100 or 10 Mbs, half or full duplex : 100baseTx-HD, 100baseTx-FD, 10baseT-FD or 10baseT-HD)

Chris

Hi derxen

Can you post the output of

ifconfig eth0

and

route -n

for us? We need to make sure that eth0 is coming up correctly.

As ianw says, you could also try DHCP - Install the dhcp-client package (if it's not already installed) and type

dhclient eth0

. This should get the IP set up from the WAG54G even if you have set it up to come up manually - no need to change ifcfg-eth0 at this stage.

Have you any other machines on the network?

There should be a link light on the FRONT of the WAG54G, corresponding to the port used by the ethernet cable - which should be a straight through type (1-1, 2-2 etc)

Chris

Have a look in /etc/nsswitch.conf - mine has a line

hosts:      files nisplus nis dns

This tells the machine to look at the hosts file first (files) then nis etc. when doing hostname lookups.

If yours is different, i.e no files entry, or dns is listed first, this may be the problem.

Chris

Here's what I use for general backups:

I have a file called backup.list containing a list of the folders to back up, one per line, e.g.

/home/chris

/root

/etc

Another called exclude_from_backup.list containing a list of subfolders and files to exclude, e.g.

/home/chris/backup/*

/home/chris/downloads/*

/home/chris/temp/*

/home/chris/.kde/share/fonts/*

/home/chris/.kde/share/cache/*

*~*

core*

This is some of it - you will want to add more...

Then a file called backup.sh containing the tar command:

#!/bin/sh
tar -cvzV `date +%Y_%m_%d_%H:%M:%S` -f backup.tar.gz --files-from=/home/chris/backup/backup.list -X/home/chris/backup/excludefrombackup.list

This needs to be executeable, so

chmod 775 /home/chris/backup/backup.sh

I get an error message when the backup finishes, but it seems to work OK - must look at it closer sometime...

All stored in /home/chris/backup/

Run as root (so you can back up any file) by typing /home/chris/backup/backup.sh and it should write a nice big backup.tar.gz file to /home/chris/backup/ which I then copy to another PC or CD.

Works for me...

Chris

Hi - are we going off at a tangent here...

Ignoring the XBox, have you actually set up normal internet connection sharing? You say you have allowed forwarding, but I assume you will also need to set up NAT (masquerading) - have you done this?

Try typing this as root:

iptables -t nat -I POSTROUTING 1 -o ppp0 -j MASQUERADE

I don't have an XBox to try this with, and don't know anything about them, but this is standard network address translation stuff (assuming the XBox will need this).

Any chance of testing it with a normal PC?

The output of iptables -nvL would be useful to us.

Chris

What you want to do is very possible - known as internet connection sharing. Your laptop will be running as a router.

But first, you need to get the interfaces working. From your posts, I assume that you can ping both the built in card and the PCMCIA card (after it has been set up).

What is happening is the card is not being recognised properly at boot time, and when you reconfigure it, the 'wizard' (if that's what you are using) inserts the driver module for you. This can be done by hand by typing modprobe <module_name> as root, but can also be set up to work automatically. It could be complicated further if the modules to make the PCMCIA slot work are also not being loaded.

Before trying out the rest of this post, try typing "cardctl insert" as root - this may get it working.

If not, we need to find out what modules are needed:

As root, without the card inserted, type

lsmod > test.lsmod

This just sends a list of the loaded drivers to a file.

Then set up the PCMCIA card so it is working, and type

lsmod > test2.lsmod
diff test.lsmod test2.lsmod

Post the result here - this will list all the modules that have been loaded to get the card to work.

You could try adding these modules to /etc/modprobe.preload - I expect the order matters. The driver module for the PCMCIA ethernet card would come last presumeably. You may only have to add the one driver if the PCMCIA slot drivers get loaded already.

Chris

Shorewall does tend to write reams of rules...

You can save the output of the command to a file with

iptables -nvL >> tables.txt

and email it to me at linux@iwpcs.co.uk if you like, together with a brief description of how it's all connected (which ports go where, IP addresses etc...)

Chris

Is it the outgoing connection that is being rejected, or the reply?

If you post the output of iptables -nvL I could probably give you a rule to type in to enable this (I don't do shorewall, but the rule will add to your config, and can be undone after doing the stuff you need if you like)

You may need to install iptables if it's not already installed.

Chris

I have written a small howto for your situation - have a look here: http://www.iwpcs.co.uk/simple_net_setup.html

It goes through a manual set up, and then has some diagnostic commands to run if it still doesn't work...

Chris

First thing I would do is remove one of the cards or disable it in the BIOS.

In any case, the IP addresses of the 2 cards should be on different networks - 192.168.0.2 and 192.168.1.2 for instance.

I have a howto here for what you are trying to do: http://www.iwpcs.co.uk/simple_net_setup.html

Hope it helps!

Chris

Its that same rule in the all2all table again...

try:

iptables -I OUTPUT 3 -o eth0 -s 127.0.0.1 -j ACCEPT

I think that will allow anything from localhost to go out eth0. The return is already taken care of in the other 'addon' rule...

Chris

iptables -I INPUT 2 -i eth0 -s 192.168.1.0/24 -j ACCEPT
iptables: Index of insertion too big

 

Apparently iptables didn't like that.

<{POST_SNAPBACK}>

You must have cleared the tables out - reboot first so that shorewall has done it's stuff

The rule is in addition to shorewall.

Chris

For the record:

Just followed the chains through - this is the rule stopping Samba (and other stuff) from communicating into eth0:

Chain all2all (2 references)

pkts bytes target prot opt in out source destination

xxxxxxxxxxxxxxxxxxxxx

2 120 Reject all -- * * 0.0.0.0/0 0.0.0.0/0

Chris

Nearly there...

If you put the following rule at the end of /etc/rc.d/rc.local it should allow all communication coming in eth0:

iptables -I INPUT 2 -i eth0 -s 192.168.1.0/24 -j ACCEPT

It will insert the rule just below the one allowing all comms from localhost, and should be quite safe to leave in place.

Either reboot, or type it in at the command line for it to work straight away.

Don't know how to configure shorewall to do the same - had a look and didn't like what I saw...

Chris

You will lose ICS, as it is a netfilter thing - we just disabled it :)

I personally dislike shorewall - read the iptables howtos and write your own rules - you will probably only need 10 lines or so, not all those shorewall ones that jump from table to table and are difficult to follow...

Chris

Looks like our posts just crossed over..

Don't you just love ALL those rules shorewall makes :)

You need to type iptables -nvL for us to read the netfilter tables properly - the v adds more info, like interface info.

e.g. the very first rule

ACCEPT all -- anywhere anywhere

could just be on one interface, or all of them... (if it is all, you are already wide open anyway)

Chris

Have a look at my howto here:

How to disable your firewall

You may need to install iptables first (urpmi iptables).

You cannot 'just stop' the firewall, as shorewall (or other firewall, including custom rule sets) just set the netfilter rules, then exit. So you need to clear the rules and set the defaults for 'allow'. This is obviously not recommended for a running environment - just for testing.

Chris

Also, what's in your routing table ( route -n ) ?

Chris

You need the masquerading rule.

Have a look at my 'work in progress' ICS_with_modem repair howto page - I am writing it for exactly your situation...

I don't use shorewall, so can't comment on the reappearance of rules - use iptables rules in /etc/rc.d/rc.local to disable them for now - this file is read after everything else when you boot up. See the howto.

Chris