Well it's an IP problem.

Site Notices

[ARCHIVED THREAD] - Well it's an IP problem.

Posted: 1/7/2006 11:35:29 PM EDT

Baseline,

I have a wireless set up with a router with one device off it via ethernet, one computer pulls off it wireless.

On my end the signal goes through a bridge then to an AP. Picking up off the AP is a laptop with a wireless card also another device coming through a wireless gaming adapter.

I am having constant problems with the devices losing their IP address. The device off the gaming adapter does not seem to have a problem. This does this until the entire system locks up and needs to be rebooted approx every other day.

I am sure you guys are going to need more info but, I have been pulling my hair out.

A little more back story

Posted: 1/7/2006 11:44:50 PM EDT

[#1]

Try to draw the network out for me.
The way you describe it is prety bad.
Sorry.

Posted: 1/7/2006 11:51:58 PM EDT

[#2]

Quoted:
Try to draw the network out for me.
The way you describe it is prety bad.
Sorry.

I knew I was gonna get that.

I will have my network beotch...PCR-00 explain it, when he has a chance.

Posted: 1/7/2006 11:55:19 PM EDT

[#3]

Quoted:
Quoted:
Try to draw the network out for me.
The way you describe it is prety bad.
Sorry.

I knew I was gonna get that.

I will have my network beotch...PCR-00 explain it, when he has a chance.

Its a mess

Posted: 1/7/2006 11:57:41 PM EDT

[#4]

Quoted:
Its a mess

And there ya have it folks!

GOODNIGHT!

Thanks for coming out.

Posted: 1/8/2006 12:18:07 AM EDT

[#5]

I know how to fix your problem, whatever it is....

Buy a new computer.

Problem SOLVED by a woman.

Posted: 1/8/2006 12:49:43 AM EDT

[#6]

You might have more than one device trying to be a DHCP server. That would explain the IP address trouble.

(most ethernet/wireless routers and bridges will act as a DHCP server by default. If you have more than one of these devices on the same network, you'll need to disable the DHCP server in all but one of them).

Posted: 1/8/2006 12:53:36 AM EDT

[#7]

static IP addressing is your friend. unlesss you have 30 computers that need to go from one subnet to another, the heck with it.. plan your network and setup static IPs.

Posted: 1/8/2006 8:22:20 AM EDT

[#8]

Quoted:
static IP addressing is your friend. unlesss you have 30 computers that need to go from one subnet to another, the heck with it.. plan your network and setup static IPs.

+1

DHCP is not for gateway links. Make up a couple subnets in the 192.168 range, or the 172.16 range and use them for point to point connections.

How many interfaces are there between your house and upstream? Let me know and I will give you a group of addys what to put for gateways at each point (called "routing").

Posted: 1/8/2006 8:47:44 AM EDT

[#9]

what is the gateway of both wireless devices ?

Posted: 1/8/2006 9:49:32 AM EDT

[#10]

Quoted:
what is the gateway of both wireless devices ?


Upstream Internet (ISP Router Addy) <--> DHCP1   [router1]  Static1 <-->  Static2   [router2] Static3 -- Home Network 
                22.22.89.142/28          22.22.  (midpt NAT) 192.168.      192.168.   (home inside NAT))  192.168.
                  (guess)              .89.143/28            100.1/28      100.2/28                       1.1/24
                                        (guess)

Setup (quick, you could calculate the 192.168.xx.xx for better allocation, I am in a hurry)         

Router1 (midpoint)
DHCP1:  IP: 22.22.89.143/28 Interface DHCP1, Router1 (ISP Assigned, Guessed here) 
Static1:  IP: 192.169.100.1/28 Interface Static1, Router1(NAT to inside address space of 192.168.100.xxx)
Routing: IP route 192.168.0.0/16 192.168.100.2
Default Gateway = 22.22.89.142 (ISP Assigned/DHCP from ISP) 

Router2 (home net/endpoint)
Static2:  IP 192.168.100.2/28 Interface Static2, Router2
Static3:  IP 192.168.1.1/24 Interface Static3, Router2
Routing:  IP route default 192.168.100.1 inside NAT interface Static3
Default Gateway = 192.168.100.1

Home Net router has NAT inside and DHCP inside, so default gateway for systems plugged into home network would be 192.168.1.1 (static3)

Edited to clarify and touch up some bad mistakes...

--ETA: If you have another midpoint, just put it in with a 192.168.101.1-2/28 Static addy and add the routing tables to point 192.168.xxx.xxx/16 towards your home net, and all other IP's (default gateway, 0.0.0.0/0) towards the "upstream" net, which would be router2

/16 = netmask of 255.255.0.0
/24 = netmask of 255.255.255.0
/28 = netmask of 255.255.252.0

Posted: 1/8/2006 11:25:56 AM EDT

[#11]

The problem with static IPs is you have to configure every machine manually. Most OSes are set up so that DHCP "just works." Double for laptops - if you don't want to fiddle with settings every time you hook it up to a different network you need DHCP.

(I just configure my DHCP server to give out fixed IPs keyed on the MAC address... avoids configuration headaches and still has the flexibility of pre-defined addresses.)

Posted: 1/8/2006 11:27:06 AM EDT

[#12]

excellent, my saboteur ferrets completed their mission, took the damn things long enough

Posted: 1/8/2006 1:16:41 PM EDT

[#13]

Quoted:
excellent, my saboteur ferrets completed their mission, took the damn things long enough

They were gerbils, and they smelled like shit. Where had you been keeping them?

Posted: 1/8/2006 1:37:41 PM EDT

[#14]

Quoted:
Quoted:
excellent, my saboteur ferrets completed their mission, took the damn things long enough

They were gerbils, and they smelled like shit. Where had you been keeping them?

Posted: 1/8/2006 2:19:33 PM EDT

[#15]

Quoted:
Baseline,

I have a wireless set up with a router with one device off it via ethernet, one computer pulls off it wireless.

On my end the signal goes through a bridge then to an AP. Picking up off the AP is a laptop with a wireless card also another device coming through a wireless gaming adapter.

I am having constant problems with the devices losing their IP address. The device off the gaming adapter does not seem to have a problem. This does this until the entire system locks up and needs to be rebooted approx every other day.

I am sure you guys are going to need more info but, I have been pulling my hair out.

A little more back story

Do you have more than one midpoint wireless router, or is what I ASCII'd out above the basic diagram for what you are doing?

Posted: 1/8/2006 8:37:32 PM EDT

[#16]

Quoted:
Quoted:
excellent, my saboteur ferrets completed their mission, took the damn things long enough

They were gerbils, and they smelled like shit. Where had you been keeping them?

the gerbils were MarkM and Lotboy's backup squad.

uhh if you see any ferrets, just ignore them

Posted: 1/8/2006 9:03:12 PM EDT

[#17]

Edited my post to be more clear, should be easy to change to that setup.

Posted: 1/8/2006 10:38:25 PM EDT

[#18]

Only problem is my VOIP phone must be assigned an IP. Brass I will call you this week.

Posted: 1/9/2006 3:54:15 AM EDT

[#19]

so when the internet stops working can you type the default gateway addres to to each device, and still connect to it?

Posted: 1/9/2006 4:20:53 AM EDT

[#20]

Would you be open to turning on remote management and remote desktop?

As a side note this is a 2.4 Ghz router , running b/g?
Do you have a 2.4 Ghz cordless phone in your house?

Posted: 1/9/2006 4:28:52 AM EDT

[#21]

my simple answer- I had similar teouble with my dsl connection when I added a 4 port "router" to my cable modem to get 4 poorts instead of 1. If I recall I had to give both different internal addresses as they bothe wanted 192.168.1.1 I think I just set one to 2 and let dhcp do the rest. Probably not this simple for your mess

Posted: 1/9/2006 7:11:52 AM EDT

[#22]

Quoted:
Only problem is my VOIP phone must be assigned an IP. Brass I will call you this week.

Home router (router2), turn on DHCP on the inside to hand out addresses in the 192.168.1.100-200 range, and give your phone the IP of 192.168.1.50, with the default gateway of 192.168.1.1, all of it plugging into the router. That way your phone is "set up", and the rest of your network gets an IP addy when you turn on a system.

Posted: 1/10/2006 7:10:19 AM EDT

[#23]

Any IP device, including phones, should have a label somewhere with the MAC address printed on it. Any good DHCP server will allow you to assign a specific IP to a specific MAC address.

[ARCHIVED THREAD] - Well it's an IP problem.

General » General Discussion

Warning

Confirm Action

About AR15.COM

Stay Connected

Newsletter

Contact Us