Cannot use the same IP twice.

[acid45]

Slackware 10.1
D-Link DWL-G520
Linksys WRT54G
madwifi CVS

Here is as far as I've gotten. I can get an IP, and I've had it working for two months before on slackware 10. However, when I reboot, I haven't done other testing. I can't get that IP anymore. Instead I have to request another IP that I didn't have before.

If I try to get an IP using
dhclient ath0
it works fine, unless I had the IP before then it continues trying until it says
No
DHCPOFFERS received
No working leases in persistent database -sleeping

Then I can reset it to how it was and try for another IP and it works fine. I don't want to use it because I don't know what's going to happen to it when I get to use all 253 available IPs, I can't reuse any.

I've tried google. Serisouly I don't know WTF I'm looking for.

I tried setting static IPs for both computers. Looking into that I don't know enough about networking to do that on my router. I don't even know if it would fix the problem, I doubt it. I'll try anyway it's not like I have any other ideas.

I have MAC filtering enabled but disabling it doesn't fix the problem.

I found this that might point me in the right direction.

DHCP locks its IP address
"lease" on the mac address of the network card.

If you're interested in any further info I won't be far away...

I found an instance where a windows XP machine lost it's IP and couldn't renew, followed by a bunch of windows xp error messages.

Of the solutions it provided only these two weren't windows specific.

1 - The firewall on your computer is blocking out network broadcast traffic.

I've never even tried learning linux iptables yet so I don't think I changed anything here.

2 - Your computer's network interface card or driver is not functioning correctly.

I'm prety sure it's working, it could be the madwifi driver. I don't see why a newer driver wouldn't work when the older one did. The card works flawlessly with d-link driver under windows.

I'm checking into this now, until someone else posts I'll just keep editing this post.

[soulestream]

???????????????????

what is the least time for dhcp on your router. Technically it should release the IP when you shut the pc off. how long have you been having this problem.

as far as static IPs you can set any IP on them as long as it is on the same network as your router

IE if your routers IP address is 192.168.100.1
then you can set your static addresses between
192.168.100.2 and 192.168.100.254

then just set the nameserver and gateway

soule

[acid45]

Lease time is set to 0 which is 1 day. I was deleting them manually. I don't remember how that worked. I don't think it did.

Well, I have tried fixing it for about a week and gave up about a month ago. I've been looking for info on the net without any luck. I don't think it's a router issue.

When I log into windows I don't have any problems getting the regular IP I can't get in slackware. I forget exactly what I have done to exhaust my efforts but I tried everything I know, althoguht that probably isn't enough for this situation.

I remember working in /etc with .lease files.

I tried dhcpcd as suggested from some guy I know from school. That didn't work, he never used dhclient is why he suggested it.

Well on my router there is a basic setup page for dynamic ip and pppoe settings, which I have now disabled and set up for advanced router in on the P3 and it's working. I still have the pppoe settings.

For static IPs I go to advanced routing. This is what I'm going to try, my brother has school in the AM.

Op. Mode: Gateway
Entry: 1()
Name: "posP3"
Dest. LAN IP: 192.168.1.234?

Subnet Mask:
255.255.255.0?

Default Gateway:
192.168.1.1?

Interface:
LAN & WIRELESS?

Entry: 2()
Name: "mine"
Dest. LAN IP: 192.168.1.235?

Subnet Mask:
255.255.255.0?

Default Gateway:
192.168.1.1?

Interface:
LAN & WIRELESS?

Nothing is automatic except LAN & WIRELESS vs WAN(Internet)
and Gateway vs Router

[soulestream]

okay

static routing in a router is not for setting up pc to router. it is for setting up router to router. to setup static ips on your local network.

i use static so if i log into my network remotely i can use port forwarding and always get to the right machine.

all you need to do is get the IP address of the router
say 192.168.100.1
subnet 255.255.255.0

then setup your PC with static IP addresses.

IP 192.168.100.2-254
subnet 255.255.255.0
gateway 192.168.100.1
DNS ; your ISPs dns or your dns if you have one

soule

[acid45]

Okay I got the static IPs working on the windows computer so now I have access to the internet independant of the results I get in slackware to find mor einformation.

For the DNS & static IP the DNS server is the router you are using, same as the default gateway IP for me.

Would I do this also in slackware /etc/resolv.conf? Normally with DHCP I would add the same IPs that the router acquired from the Modem into my /etc/resolv.conf. My guess is no and that's what I'm going to try.

[acid45]

okay here is some new info that I've gathered while playing with these static IP's. If there is anything missing just let me know.

There is a problem I noticed happening when I stopped being able to access the net. That is that when I set a route using

route add default gw 192.168.1.1

and then following it with

route

It lists the first two items,192.168.1.0 and another, freezes for about 20 seconds and then lists the default gw.

I can't figure how to get it to text file.

route > /mnt/floppy/route.txt didn't display any info nor did it write any to file. It did create the file.

I found this weird. I though RX was recieved packets and TX was transfered packets.

RX packets:1 errors:52 dropped:0 overruns:0 frame:52


Here are some of my files settings and outputs that I see to try and figure this out.

/etc/resolv.conf. The first nameserver is my router, same setting I used in DNS field to get windows to use a static IP. The rest are the DNS settings on the router.

search rox.net
nameserver 192.168.1.1
nameserver 192.168.254.2
nameserver 192.168.253.2
nameserver 142.177.1.2


ping -c 10 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.101 icmp_seq=1 Destination Host Unreachable
From 192.168.1.101 icmp_seq=2 Destination Host Unreachable
From 192.168.1.101 icmp_seq=3 Destination Host Unreachable
From 192.168.1.101 icmp_seq=4 Destination Host Unreachable
From 192.168.1.101 icmp_seq=5 Destination Host Unreachable
From 192.168.1.101 icmp_seq=6 Destination Host Unreachable
From 192.168.1.101 icmp_seq=7 Destination Host Unreachable
From 192.168.1.101 icmp_seq=8 Destination Host Unreachable
From 192.168.1.101 icmp_seq=9 Destination Host Unreachable
From 192.168.1.101 icmp_seq=10 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 9022ms
, pipe 3



ifconfig, lo removed

ath0 Link encap:Ethernet HWaddr 00:0D:88:8B:C3:A5
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:52 dropped:0 overruns:0 frame:52
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:14 (14.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Memory:f8bab000-f8bbb000


iwconfig

ath0 IEEE 802.11g ESSID:<essid> Nickname:"roxbox"
Mode:Managed Frequency:2.462GHz Access Point: <AP MAC>
Bit Rate=36Mb/s Tx-Power:50 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:28/94 Signal level:-67 dBm Noise level:-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


/etc/rc.d/rc.local

#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:
echo "Finishing wireless network configuration"
ifconfig ath0 192.168.1.101
route add default gw 192.168.1.1


additions to /etc/rc.d/rc.wireless, it tried to use $IWPATH/iwconfig to configure IWPRIV settings. This allowed me to set all wireless settings without using rc.local.

IWPRIVCOMMAND="$IWPATH/iwpriv ${INTERFACE}"
...
if [ -n "$IWPRIV" ] ; then
echo "$0: $IWPRIVCOMMAND $IWPRIV" | $LOGGER
$IWPRIVCOMMAND $IWPRIV
fi


/etc/rc.d/rc.wireless.conf

# Wireless LAN adapter configuration
#
# Theory of operation :
#
# The script attempts to match a block of settings to the specific wireless
# card inserted, the *first* block matching the card is used.
# The address format is "hwaddr", with * as a wildcard.
# 'hwaddr' is the unique MAC address identifier of the wireless card.
# The MAC address is usually printed on the card, or can be found via ifconfig.
# Some examples here use only half of the MAC address with a wildcard to
# match a whole family of cards...
#
# All the Wireless specific configuration is done through the Wireless
# Extensions, so we will just call 'iwconfig' with the right parameters
# defined below.
# Of course, you need to have iwconfig installled on your system.
# To download iwconfig, or for more info on Wireless Extensions :
# http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
#
# Note : you don't need to fill all parameters, leave them blank, in most
# cases the driver will initialise itself with sane defaults values or
# automatically figure out the value... And no drivers do support all
# possible settings...
#
# -- This is a modified '/etc/pcmcia/wireless.opts' script --
#

VERBOSE=1

case "$HWADDR" in

## NOTE : Comment out the following five lines to activate the samples below ...
## --------- START SECTION TO REMOVE -----------
## Pick up any Access Point, should work on most 802.11 cards
## ---------- END SECTION TO REMOVE ------------


# Here are a few examples with a few Wireless LANs supported...
# The matching is done on the first 3 bytes of the MAC address
# Generic example (decribe all possible settings)
*)
#operation mode must be first: Ad-Hoc, Managed, Master, Repeater, Secondary auto
MODE="Managed"
INFO="D-LINK G-520 rev.B..."
# ESSID (extended network name) : My Network, any
ESSID="<essid>"
# NWID/Domain (cell identifier) : 89AB, 100, off
NWID=""
# Operation mode : Ad-Hoc, Managed, Master, Repeater, Secondary, auto
#MODE="Managed"
# Frequency or channel : 1, 2, 3 (channel) ; 2.422G, 2.46G (frequency)
FREQ="2.462G"
CHANNEL=""
# Sensitivity (cell size + roaming speed) : 1, 2, 3 ; -70 (dBm)
SENS=""
# Bit rate : auto, 1M, 11M
RATE="36M"
# Encryption key : 4567-89AB-CD, s:password
KEY=""
# RTS threshold : off, 500
RTS=""
# Fragmentation threshold : off, 1000
FRAG=""
# Other iwconfig parameters : power off, ap 01:23:45:67:89:AB
IWCONFIG="ap <AP>"
# iwspy parameters : + 01:23:45:67:89:AB
IWSPY=""
# iwpriv parameters : set_port 2, set_histo 50 60
IWPRIV="mode 3, authmode 1"
;;
esac



P.S.
I wish I could write to my windows partition rather than fooling around looking for a floppy that works.

[soulestream]

you have to forgive my wireless knowledge, i have none(on linux) and havent set it up on anyones system and I wont use it on mine so, cant help much there.

as far as nameserver all you need is

nameserver xxx.xxx.xxx.xxx of your ISP DNS SERVER. not routers. routers are not DNS servers. if your gateway is set for your router it will find the dns server.

if your router is setup not to return ping packets then it wont

[acid45]

Would havng extra nameservers break it I don't think so but I also don't know much about networking.

Block anonymous WAN request, identified as blocking pings by my router is not checked/disabled. Pinging from windows works.

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms


nameserver xxx.xxx.xxx.xxx of your ISP DNS SERVER. not routers. routers are not DNS servers. if your gateway is set for your router it will find the dns server.


So I do have to set up static routes on the router? I'll try that.

[acid45]

I've added a static route to my router. It looks like this.

Op. Mode: Gateway
Entry: 1(roxbox)
Name: roxbox
Dest. IP: 192.168.1.101 #IP assigned to ath0
SNMask: 255.255.255.0
Gateway: 192.168.1.1 #router IP
Interface: LAN & Wireless

Didn't change anything when I tried what I know.

Here is route output.


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 ath0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 ath0


In between the output for loopback and default there is a 20-30 second pause.

/etc/resolv.conf has been fixed to only include ISP DNS addresses.

search rox.net
nameserver 192.168.254.2
nameserver 192.168.253.2
nameserver 142.177.1.2


I've exhausted my efforts on google, I just don't know how/what I'm looking for.

[Satanic Atheist]

Okay, I'm not too hot on the technical side of networking (particularly the depth you're going into), so instead, I'm going to clarify some of the systems and how a normal, NAT router communicates between a computer and itself and the Internet and itself.

First off, DHCP - Dynamic Host Configuration Protocol. This is a special ICMP and UDP transport system that sends the MAC address on a broadcast to the network. Since the computer does not have an IP address at boot up (unless one is statically configured for it), it doesn't know where it is. Once a DHCP_REQUEST packet is received by the DHCP server (your router, in this case), it sends back an offer of a DHCP_OFFER packet to the MAC address that is broadcasting. Leases only serve to issue the same IP address to a specific MAC address if the computer needs to re-obtain its IP (say, after a reboot). If the lease is one day, then from the first time that IP is offered to the machine, then for 24 hours after, no matter how many times you reboot, you will always receive the same IP. Once 24 hours have passed, you will most likely receive a new IP.

Your router works the same way on it's WAN port - but this time, it requests an IP from your ISP's servers. This time, the router is the client, not the server. Be careful to distinguish the both when discussing them. As long as the router can access the Internet (which it can in Windows) then the router's DHCP Client configuration is correct.

DNS Servers (or nameservers) translate IP addresses into "http://www.google.co.uk" into your web browser instead of "http://66.249.87.99" (i.e. you don't have to remember the IP address of every page you visit).

DNS Server settings are usually offered as part of a DHCP configuration, so once the client is configured over DHCP, then it automatically updates it's DNS Server locations for name resolving.

In your list of nameservers, you should have your ISPs name server top of the list and then the router (if your router supports DNS forwarding/proxying). When your computer needs to go and resolve a name, it will ask the server at the top of the list. If it doesn't reply, then it goes down the list until it either runs out of servers or gets a reply.

Note that DNS and DHCP are two different things.

The IP address range you are using (192.168.xxx.yyy) is known as a Class C network on a private network. The only system that has a public IP is the router. No-one can use the 192.168.xxx.yyy publicly on the Internet. Your router rewrites the address of packets destined to the Intenet to appear as though it is the origining system but it "remembers" which machine sent the packet so it can pass the reply on correctly. Your router is performing Network Address Translation or NAT to accomplish this.

Overall, if you haven't bought a static IP from your ISP, then you need to leave DHCP configuration on for your router and DHCP server on to configure clients.

Hope this helps to clarify the situation. I personally never had this kind of trouble...

James

[acid45]

Well, as mentioned I use PPPoE not DHCP to acquire my IP from my ISP, this hasn't changed.

I have the DHCP server on the router turned off and I have a static route, my router doesn't explain this very well.

A static route is a pre-determined pathway that network information must travel to reach a specific host or network.

This route points to the computer I'm using now, I think. I still have access to the net wthout it On two boxes I have windows using specified/static info instead of automatic/DHCP info.

I just had an idea. I haven't tried NEW IPs since I tried a static configuration. I'll be back with an edit of how that worked...

Yay now even changing IP's doesn't work. I'm getting out the DVD and floppies now...

[soulestream]

I think maybe some of the confusion comes from the fact that you think a static route and a static IP are the same thing. they are not only different they are mostly unrelated.

static routing tells routers what NETWORK to send packets to. not what machine. if router has port A(hooked to your modem) and port B hooked to your network(usually hooked to a built in switch in the home style router) if a machine sends a packet to the router it looks at its route and asks if it goes out port A or back to port B. setting the route statically means you tell the router what Networks it is hooked to. in you case your home network and your isp network. it doesnt care what pc are hooked up or their Ip addresses.

setting static IP are for the pc to communicate with each other pc. it basically just says pc1 is 254 pc2 is 246 and the router is 247. then it just says im going to send a packet to router it knows where to send it, but it doesnt really care that the router is a router, only that it is at 192.168.1.247.

I would reset your router completely(usually a reset to orginal defaults feature) leave static and dynamic routing alone. as a matter of fact if you router has a gateway only feature turn that on. resetup pppoe. then just set static ip addresses on your network to the same network as your router. I actally set up a wireless network today for a custy, this works well(after banging my head over wep for awhile)

ie

if router address is 192.168.123.1/255.255.255.0
then setup your pc with static ip addresses

192.168.123.2/255.255.255.0
192.168.123.3/255.255.255.0
etc

all with gateway of 192.168.123.1
and nameserver of your ISP DNS server(you stated IP above)

that is all you have to do, no more router config.


hope this helps

soule

btw for any body reading this I know static routing is more entailed and router do care where packets come from, but not really relevant for this purpose

[acid45]

Yeah, confused is my middle name.

Yeah that router suggestions didn't work as I expected. I had to wait 30 minutes on the phone for customer service to reset my password because someone changed it and didn't write it down.

Probably me :o

So I gave up and siad I'm reinstlalling slackware.

I couldn't find my slackware 10.1 cd so I used my slackware 10.0 dvd and floppies using ataraid kernel image, I have a sata raid card and my motherboard doesn't let me boot from DVD rom although it has a sataraid card.

The instalation went fine then I booted into slackware all ready to come here from there with a static ip when I remembered why I bothered getting slackware 10.1 in the first place. Keyboard goes dead after lilo if I choose slackware. This didn't always used to happen.

I'm sure there is a solution to this on the net but I couldn't solve my IP problems so why bother?

I'm going to have a hard look, or make a new slackware 10.1 discs and re-install AGAIN.

:o

my computer hates me

[Satanic Atheist]

Originally posted by acid45
Well, as mentioned I use PPPoE not DHCP to acquire my IP from my ISP, this hasn't changed.
Well, PPPoE is Point-to-Point Protocol over Ethernet. It's the connection that you have over broadband to your ISP. TCP/IP runs on top of this connection and DHCP is a client/server relationship that fits neatly into TCP/IP. As a result, you do use DHCP to get an IP from your ISP.

Anyhow, sorry to hear that you haven't managed to solve the problem, but I have to admit, with your confusion, working out what's happening is extremely difficult.

Hope you have better luck with Slackware.

James

[acid45]

Oh, I thought PPPoE was generaly DHCP+
Extra layers for the obvious login and whatever else PPPoE has, I don't know anythin about PPPoE but it's an option on my router instead of DHCP.
I had a network class and we didn't go into anything in great detail and did a lot of scripting since we were a programming class.
My mistake. It was a linux netowrking course but all we did was set dhcp up in redhat 6 and run a printer then we got into scripting and that's about it. Oh and the teacher decided to teach us windows netowrking to fill in time? not very many students like this.

[Satanic Atheist]

No probs. I don't know much about PPPoE (it's not used in the UK) but I daresay someone will rip me to shreds...

PPPoE uses the same standards that are used to connect two modems together on a dial-up connection (i.e. PPP) but in this case, it's sent over a dedicated Ethernet line which is much faster (hence broadband and the "oE" extension).

You can assume that the PPPoE link is a pipeline that links your computer to your ISP so that data can "flow" down it. Unlike a real pipeline, ours can be instantly created and destroyed (to reflect connections and disconnections). Now, to look at a pipe, it's quite boring. You cannot really tell what's in it (reading the label on the outside won't help you here) unless you are standing at either end and are responsible for putting some liquid into it or removing it. The liquid is the TCP/IP data.

So, the PPPoE pipeline encapsulates the liquid data to get it from A to B.

Without the pipeline, you can't send data (well, you can, it just won't go where you want it to. It'll head to the lowest point it can which I guess is some porn server in Nevada ;) ).

(You can have loads of fun with this analogy, such as what happens to a burst pipe?)

However, can anyone explain what PPPoE offers and why it is the choice medium?

Thanks,

James

[acid45]

uh it's a discovery process for ppp protocol sessions usage using ethernet, I don't know enough about netowrking to learn a protocol though and I don't know where to start.

[Fryguy8]

For static IPs, you do not need to change ANYTHING on your router. AT ALL. Ignore that static routing stuff, and preferably set it back to the defaults.

Go to your linux box, run whatever network config script your have, your gateway is the IP of your router (192.168.0.1 or 1.1), the subnet is 255.255.255.0, broadcast is 192.168.0.255 or .1.255, dns is the dns of your isp, and IP is whatever you want in the right range (my router does 192.168.0.100-199). That's IT.

Also, i'd venture to guess that your lease time is wrong if they aren't releasing.

[acid45]

I've given up on this, my configuration matches what you're saying. There must have been something else in the way. I'm downloading slackware 10.1 again.

[Satanic Atheist]

Originally posted by Fryguy8
Also, i'd venture to guess that your lease time is wrong if they aren't releasing.
Would this make a difference? If he's connecting with the same MAC address then he shouldn't have this problem as even if the lease was very high, he'd only end up receiving the same IP address.

The only last thing I can think of is some weird security setting that prevents reassignment of a used MAC address until the lease has expired, but even this would have to ignore identical MAC addresses (which would re-lease the same IP address to the same MAC target). Clearly, this is client-side since Windows works fine, but Linux doesn't.

James

[soulestream]

I think it is a lease time issue, but not with the router. he has mentioned messing with .lease files in slackware(which im not familar with), but id venture to guess slackware has a different lease time than the router, so the slack box is saying i have this IP, so the router is saying well this is the next IP so you have it. i didnt think this was possible, but that usually means it is

as far as the keyboard issue is you saved your xorg configuration or upgrade from 10 to 10.1 you have to change your keyboard driver name in xorg from keyboard to kb. no idea why they changed that


soule

btw fryguy thanks for shortening all the crap i wrote:D

[acid45]

Clearly, this is client-side since Windows works fine, but Linux doesn't.

that's what I though

I found this while looking for a solution to this
IBM e-business architect Chris Walden is your guide through a nine-part developerWorks series on moving your operational skills from a Windows to a Linux environment. He covers everything from logging to networking, and from the command-line to help systems -- even compiling packages from available source code. We begin our transition by examining some of the differences and similarities between Linux and Windows, and learn to stop rebooting all the time. - http://www-106.ibm.com/developerworks/linux/library/l-roadmap1.html

I wasn't "messing" with them I was reading what goes into them and making sure everything I understood in the man was correct to my knowledge. Backed up and replaced them when I was done. I can't post them anymore, I reinstalled. I'll try again.

For now I'm going to be reading that guide by IBM and see where that leads me.


overcoming the reboot habit will probably be the hardest.

hahaha

[Satanic Atheist]

Originally posted by soulestream
I think it is a lease time issue, but not with the router. he has mentioned messing with .lease files in slackware(which im not familar with), but id venture to guess slackware has a different lease time than the router, so the slack box is saying i have this IP, so the router is saying well this is the next IP so you have it. i didnt think this was possible, but that usually means it is
If I remember from working with DHCP, the .leases file is for the server only. I'm not sure that the client receiving an IP is aware (or even cares) how long the lease time is.

I don't think there's a conflict here.

James

[acid45]

Whatever it was it's gone now. I installed slackware 10.1 this morning including the gpm option, which was causing my keyboard issues.

I installed my madwifi drivers and I'm humming along, on lynx anyway.

I've gota figure a way to get a startx command going for my user.

I didn't fix it afterall. it's stupid i don't know what im doing wrong.

[soulestream]

If I remember from working with DHCP, the .leases file is for the server only.


that makes more sense


soule

[acid45]

I still can't figure this out...I've been looking and looking and everyone seems to have a similar problem but their solution is not my problem.

I've spent hours in google searching though various linuxquestions.org archives and came up empty handed.

I have reinstalled and tried two slackware 10.0 and 10.1 and both do the same thing. I have tried deleting the /var/state/dhcp/*.leases in case there was a conflict, they were empty.

Something I noticed is when I type IWLIST scan it shows my router with a connectivity of 24/94. When I type IWCONFIG it shows as 0/94.

When I type ROUTE ADD DEFAULT GW 192.168.1.1 it seems to work fine. When I type ROUTE it shows the first two entries one is an ip 192.168.1.0. After that there is a five or six second pause and then it shows the defaukt route entry. When I type PING -C 6 192.168.1.1 it comes back 100% failure.

When I try to use DHCLIENT ATH0 it failes 6 times and then my if config reveals ath0 no longer has an IP and the default route has been removed.

If there is any information other than posted above, I've abandoned USING the OS and when I checked the settings seem to be the same as above, even though I've been tasting everything under the sun.

I try to solve this problem at least three times a week and I'm comming up empty handed. Re-installing doesn't work. I reset factory defaults on the router and it's set to DHCP, except for it to get it's information via PPPoE.

There is one minor change to /etc/resolv.conf, it no longer has my router as a nameserver. I don't this this file is relevant, I'm not even trying to get that far yet.

I'm using the slackware 10.0(kernel 2.4.26) ataraid driver and currently is installed the slackware 10.1(2.4.29) sata driver, which now marks the drives as /dev/sda and /dev/hde(slackware 10.0)