Reserved LAN port changing
in [UK Linux]
|
Prev: Stoke-on-Trent LUG
Next: [ANN] Free event: In The Brain of Simon Wardley, Situation Normal, Everything must change, Oct 27 18:30-20:00
From: Andy Cap on 22 Oct 2009 05:05 Hi I have a 4 port wireless NETGEAR DG843GTrouter. 192.168.0.2 > 6 are the only available ports. 2 is reserved for my Windows PC 3 " Centos 5.3 running Asterisk 4 " Centos 5.3 DT 5 " Linksys SPA3000 ATA 6 " Dell laptop (wireless) Occasionally (usually overnight) the Asterisk turns up on port 6 producing a similar log output to that below. Last night, I noticed the same sequence was produced but it happened to end up back on 3, so it would normally have gone unnoticed. Once the port is changed I can not make my calls. I do not understand enough to explain why this sequence is being initiated. I do know that NETGEAR have had problems with this router and are playing with the FW versions. Can anyone just confirm it is likely to be a router problem or is the process started within Asterisk and if so, what should I be looking for? TIA Andy C Oct 22 03:37:00 Asterisk dhclient: DHCPREQUEST on eth0 to 192.168.0.1 port 67 Oct 22 03:37:00 Asterisk dhclient: DHCPNAK from 192.168.0.1 Oct 22 03:37:00 Asterisk NET[6874]: /sbin/dhclient-script : updated /etc/resolv.conf Oct 22 03:37:00 Asterisk avahi-daemon[2497]: Withdrawing address record for 192.168.0.3 on eth0. Oct 22 03:37:00 Asterisk avahi-daemon[2497]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.3. Oct 22 03:37:00 Asterisk avahi-daemon[2497]: iface.c: interface_mdns_mcast_join() called but no local address available. Oct 22 03:37:00 Asterisk avahi-daemon[2497]: Interface eth0.IPv4 no longer relevant for mDNS. Oct 22 03:37:00 Asterisk avahi-daemon[2497]: Interface eth0.IPv6 no longer relevant for mDNS. Oct 22 03:37:00 Asterisk avahi-daemon[2497]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::2b0:d0ff:fed4:a3f. Oct 22 03:37:00 Asterisk avahi-daemon[2497]: Withdrawing address record for fe80::2b0:d0ff:fed4:a3f on eth0. Oct 22 03:37:00 Asterisk kernel: eth0: setting half-duplex. Oct 22 03:37:00 Asterisk dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Oct 22 03:37:00 Asterisk dhclient: send_packet: Network is down Oct 22 03:37:01 Asterisk avahi-daemon[2497]: New relevant interface eth0.IPv6 for mDNS. Oct 22 03:37:01 Asterisk avahi-daemon[2497]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::2b0:d0ff:fed4:a3f. Oct 22 03:37:01 Asterisk avahi-daemon[2497]: Registering new address record for fe80::2b0:d0ff:fed4:a3f on eth0. Oct 22 03:37:08 Asterisk dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Oct 22 03:37:10 Asterisk dhclient: DHCPOFFER from 192.168.0.1 Oct 22 03:37:10 Asterisk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Oct 22 03:37:10 Asterisk dhclient: DHCPACK from 192.168.0.1 Oct 22 03:37:10 Asterisk avahi-daemon[2497]: New relevant interface eth0.IPv4 for mDNS. Oct 22 03:37:10 Asterisk avahi-daemon[2497]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.3. Oct 22 03:37:10 Asterisk avahi-daemon[2497]: Registering new address record for 192.168.0.3 on eth0. Oct 22 03:37:10 Asterisk NET[6963]: /sbin/dhclient-script : updated /etc/resolv.conf Oct 22 03:37:10 Asterisk dhclient: bound to 192.168.0.3 -- renewal in 126124 seconds.
From: Gordon Henderson on 22 Oct 2009 06:31 In article <4r70e59ansrotpssibktkubfr3k3avj41g(a)4ax.com>, Andy Cap <Andy_Cap(a)nosuch.co.uk> wrote: >Hi > >I have a 4 port wireless NETGEAR DG843GTrouter. > >192.168.0.2 > 6 are the only available ports. >2 is reserved for my Windows PC >3 " Centos 5.3 running Asterisk >4 " Centos 5.3 DT >5 " Linksys SPA3000 ATA >6 " Dell laptop (wireless) > >Occasionally (usually overnight) the Asterisk turns up on port 6 >producing a similar log output to that below. Last night, I noticed the same >sequence was produced but it happened to end up back on 3, so it would normally >have gone unnoticed. Once the port is changed I can not make my calls. I wonder if you're confusing the word "port" with "IP Address"? However I can see what's going on here & what you mean, but it sounds like the Linksys may be "broken" or misbehaving. DHCP devices will periodically renew their "lease" - and they should tell the server their current IP as part of the negotiation and the server should let them keep it unless programmed not to. Here is what I would do (and it's similar to what I do do!) Set the DHCP range in the Linksys to something else - something you're not currently using - e.g. 192.168.0.100 through 192.168.0.199. Give your Asterisk box a fixed IP address - e.g. 192.168.0.10. Re-program the ATA to use that fixed IP address of 192.168.0.10 for the registrar server/proxy, etc. You may also wish to give your Desktop a fixed IP address too - e.g. 192.168.0.11. Everything else (ie. the laptop, ATA, etc.) is OK with dynamically allocated IP addresses. They'll come from .100 through .199. (Update any port-forwarding in the Linksys for SIP/IAX, etc.) Enjoy! Gordon
From: Andy Cap on 22 Oct 2009 10:08 On Thu, 22 Oct 2009 10:31:14 +0000 (UTC), Gordon Henderson <gordon+usenet(a)drogon.net> wrote: >I wonder if you're confusing the word "port" with "IP Address"? However >I can see what's going on here & what you mean, but it sounds like the >Linksys may be "broken" or misbehaving. Yes. IP addresses indeed. >DHCP devices will periodically renew their "lease" - and they should >tell the server their current IP as part of the negotiation and the >server should let them keep it unless programmed not to. > >Here is what I would do (and it's similar to what I do do!) > >Set the DHCP range in the Linksys to something else - something you're >not currently using - e.g. 192.168.0.100 through 192.168.0.199. > >Give your Asterisk box a fixed IP address - e.g. 192.168.0.10. > >Re-program the ATA to use that fixed IP address of 192.168.0.10 for the >registrar server/proxy, etc. > >You may also wish to give your Desktop a fixed IP address too - >e.g. 192.168.0.11. > >Everything else (ie. the laptop, ATA, etc.) is OK with dynamically >allocated IP addresses. They'll come from .100 through .199. > >(Update any port-forwarding in the Linksys for SIP/IAX, etc.) > >Enjoy! > >Gordon I'm confused by your labelling as well. ;-) By Linksys do you mean the Netgear router ? The Linksys IS the ATA How often does this negotiation take place. Why do you think changing the IP range might correct the negotiation ? Thanks for the suggestion. Andy C
From: Ian Northeast on 22 Oct 2009 11:21 On Thu, 22 Oct 2009 15:08:37 +0100, Andy Cap wrote: > On Thu, 22 Oct 2009 10:31:14 +0000 (UTC), Gordon Henderson > <gordon+usenet(a)drogon.net> wrote: > > >>I wonder if you're confusing the word "port" with "IP Address"? However I >>can see what's going on here & what you mean, but it sounds like the >>Linksys may be "broken" or misbehaving. > > Yes. IP addresses indeed. > >>DHCP devices will periodically renew their "lease" - and they should tell >>the server their current IP as part of the negotiation and the server >>should let them keep it unless programmed not to. >> >>Here is what I would do (and it's similar to what I do do!) >> >>Set the DHCP range in the Linksys to something else - something you're >>not currently using - e.g. 192.168.0.100 through 192.168.0.199. >> >>Give your Asterisk box a fixed IP address - e.g. 192.168.0.10. >> >>Re-program the ATA to use that fixed IP address of 192.168.0.10 for the >>registrar server/proxy, etc. >> >>You may also wish to give your Desktop a fixed IP address too - e.g. >>192.168.0.11. >> >>Everything else (ie. the laptop, ATA, etc.) is OK with dynamically >>allocated IP addresses. They'll come from .100 through .199. >> >>(Update any port-forwarding in the Linksys for SIP/IAX, etc.) >> >>Enjoy! >> >>Gordon > > I'm confused by your labelling as well. ;-) > > By Linksys do you mean the Netgear router ? He appears to, Linksys are also well known as manufacturers of routers hence the confusion. > The Linksys IS the ATA > How often does this negotiation take place. When the lease's renewel period expires. From the message in your OP this is every 126124 seconds, i.e. 35 hours. This is some time before the lease actually expires to allow for a temporarily absent DHCP server. It may be configurable in the router. > Why do you think changing the IP range might correct the negotiation ? What he's suggesting is that you restrict the addresses given out by the router's DHCP server to a small range, then locally configure addresses on the devices you need to have a static IP with values outside of this range, but still within the same subnet i.e. 192.168.0.1 - 192.168.0.254 (where .1 is already taken by the router). Then they will not use DHCP at all, and so be unaffected by any fault in the DHCP server. If you do this you will also have to manually set the default route and DNS servers, to the same values as are given out by the DHCP server. Regards, Ian
From: Gordon Henderson on 22 Oct 2009 14:08
In article <cep0e594u38c8eni6lq3js05p0srggfidj(a)4ax.com>, Andy Cap <Andy_Cap(a)nosuch.co.uk> wrote: >On Thu, 22 Oct 2009 10:31:14 +0000 (UTC), Gordon Henderson ><gordon+usenet(a)drogon.net> wrote: > > >>I wonder if you're confusing the word "port" with "IP Address"? However >>I can see what's going on here & what you mean, but it sounds like the >>Linksys may be "broken" or misbehaving. > >Yes. IP addresses indeed. > >>DHCP devices will periodically renew their "lease" - and they should >>tell the server their current IP as part of the negotiation and the >>server should let them keep it unless programmed not to. >> >>Here is what I would do (and it's similar to what I do do!) >> >>Set the DHCP range in the Linksys to something else - something you're >>not currently using - e.g. 192.168.0.100 through 192.168.0.199. >> >>Give your Asterisk box a fixed IP address - e.g. 192.168.0.10. >> >>Re-program the ATA to use that fixed IP address of 192.168.0.10 for the >>registrar server/proxy, etc. >> >>You may also wish to give your Desktop a fixed IP address too - >>e.g. 192.168.0.11. >> >>Everything else (ie. the laptop, ATA, etc.) is OK with dynamically >>allocated IP addresses. They'll come from .100 through .199. >> >>(Update any port-forwarding in the Linksys for SIP/IAX, etc.) >> >>Enjoy! >> >>Gordon > >I'm confused by your labelling as well. ;-) > >By Linksys do you mean the Netgear router ? *thud* Er, yes. My bad. >The Linksys IS the ATA > >How often does this negotiation take place. > >Why do you think changing the IP range might correct the negotiation ? I think the next post answers it, but by the sounds of it, the router (that's the netgear!) is failing in it's duties as a dhcp server in that it's forgetting IP's it's already assigned, so deliberately making some devices have a static IP and leaving those that won't really care to have dynamic ones keeps everything separate. It's considered good practice anyway (well amongst some!) - basically keep the servers and other "known" devices on a known fixed IP address by not using DHCP for them, but do use DHCP for the majority of things that come and go... On my LAN, which is typical of many I've built, I have it more or less the same way - my routers, server and asterisk boxes are on fixed IP addresses - as are test & development servers and my printer. Laptops, VoIP phones are all dynamically assigned via DHCP. Gordon |