A system on my local network (pvr) has its IP address in /etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the address 192.168.10.2 reserved and assigned to pvr. Worked fine. Today after booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP address has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh 192.168.10.5
Question: where is this (dynamic?) assignment taking place?
On Fri, Feb 3, 2012 at 4:01 PM, Geoffrey Leach geoff@hughes.net wrote:
A system on my local network (pvr) has its IP address in /etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the address 192.168.10.2 reserved and assigned to pvr. Worked fine. Today after booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP address has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh 192.168.10.5
Question: where is this (dynamic?) assignment taking place?
I think the machine is requesting the router a new IP and the router couldn't match the MAC of the request with the MAC associated to the reserved IP 192.168.10.2, so is giving a new IP in the range. Something change at the machine, did you check the MAC AE:5D:BA:91:67:2D against your rule in the router?
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 02/03/2012 01:54:34 PM, j.e.aneiros wrote:
On Fri, Feb 3, 2012 at 4:01 PM, Geoffrey Leach geoff@hughes.net wrote:
A system on my local network (pvr) has its IP address in /etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the address 192.168.10.2 reserved and assigned to pvr. Worked fine. Today
after
booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP
address
has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh
192.168.10.5
Question: where is this (dynamic?) assignment taking place?
I think the machine is requesting the router a new IP and the router couldn't match the MAC of the request with the MAC associated to the reserved IP 192.168.10.2, so is giving a new IP in the range. Something change at the machine, did you check the MAC AE:5D:BA:91:67:2D against your rule in the router?
Your suspicion was correct. I replaced the one in use with the one from ifconfig. Unfortunately that did not fix the problem.
I need a tutorial on assigning MAC addresses, as they are inconsistent on the server and client. Is it correct that the MAC address is the same as HWADDR in the ifcfg file? And why would the value change when the hardware did not?
Thanks.
On 02/03/2012 02:39 PM, Geoffrey Leach wrote:
On 02/03/2012 01:54:34 PM, j.e.aneiros wrote:
On Fri, Feb 3, 2012 at 4:01 PM, Geoffrey Leachgeoff@hughes.net wrote:
A system on my local network (pvr) has its IP address in /etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the address 192.168.10.2 reserved and assigned to pvr. Worked fine. Today
after
booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP
address
has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh
192.168.10.5
Question: where is this (dynamic?) assignment taking place?
I think the machine is requesting the router a new IP and the router couldn't match the MAC of the request with the MAC associated to the reserved IP 192.168.10.2, so is giving a new IP in the range. Something change at the machine, did you check the MAC AE:5D:BA:91:67:2D against your rule in the router?
Your suspicion was correct. I replaced the one in use with the one from ifconfig. Unfortunately that did not fix the problem.
I need a tutorial on assigning MAC addresses, as they are inconsistent on the server and client. Is it correct that the MAC address is the same as HWADDR in the ifcfg file? And why would the value change when the hardware did not?
They're supposed to be the same. The only way to be sure is to actually see what the driver assigned as the MAC address:
$ cat /sys/class/net/wlan0/address
What's returned by that is the MAC address as set up by the driver. That should match the value in the ifcfg file's HWADDR field. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - If you can't beat your computer at chess...try kickboxing! - ----------------------------------------------------------------------
On 2012/02/03 16:52, Rick Stevens wrote:
On 02/03/2012 02:39 PM, Geoffrey Leach wrote:
On 02/03/2012 01:54:34 PM, j.e.aneiros wrote:
On Fri, Feb 3, 2012 at 4:01 PM, Geoffrey Leachgeoff@hughes.net wrote:
A system on my local network (pvr) has its IP address in /etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the address 192.168.10.2 reserved and assigned to pvr. Worked fine. Today
after
booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP
address
has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh
192.168.10.5
Question: where is this (dynamic?) assignment taking place?
I think the machine is requesting the router a new IP and the router couldn't match the MAC of the request with the MAC associated to the reserved IP 192.168.10.2, so is giving a new IP in the range. Something change at the machine, did you check the MAC AE:5D:BA:91:67:2D against your rule in the router?
Your suspicion was correct. I replaced the one in use with the one from ifconfig. Unfortunately that did not fix the problem.
I need a tutorial on assigning MAC addresses, as they are inconsistent on the server and client. Is it correct that the MAC address is the same as HWADDR in the ifcfg file? And why would the value change when the hardware did not?
They're supposed to be the same. The only way to be sure is to actually see what the driver assigned as the MAC address:
$ cat /sys/class/net/wlan0/address
What's returned by that is the MAC address as set up by the driver. That should match the value in the ifcfg file's HWADDR field.
There is also the little pesky detail that the computer remembers the address that it last used and requests that of the DHCP server. Modulo the server involved it will give the requested address regardless of whether it has a formal assignment for that MAC to another address or not. You may have to tell the computer to formally release the current DHCP assignment before going off to request a new one.
{o.o} Been bit by this one before. It's also painful to change a computer's name on a network in which the dhcpd updates the named. Absurdly short TTLs helps.
On 02/03/2012 06:49:30 PM, jdow wrote:
On 2012/02/03 16:52, Rick Stevens wrote:
On 02/03/2012 02:39 PM, Geoffrey Leach wrote:
On 02/03/2012 01:54:34 PM, j.e.aneiros wrote:
On Fri, Feb 3, 2012 at 4:01 PM, Geoffrey Leachgeoff@hughes.net wrote:
A system on my local network (pvr) has its IP address in
/etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the
address
192.168.10.2 reserved and assigned to pvr. Worked fine. Today
after
booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP
address
has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh
192.168.10.5
Question: where is this (dynamic?) assignment taking place?
I think the machine is requesting the router a new IP and the
router
couldn't match the MAC of the request with the MAC associated to
the
reserved IP 192.168.10.2, so is giving a new IP in the range. Something change at the machine, did you check the MAC AE:5D:BA:91:67:2D against your rule in the router?
Your suspicion was correct. I replaced the one in use with the one
from
ifconfig. Unfortunately that did not fix the problem.
I need a tutorial on assigning MAC addresses, as they are
inconsistent
on the server and client. Is it correct that the MAC address is
the
same as HWADDR in the ifcfg file? And why would the value change
when
the hardware did not?
They're supposed to be the same. The only way to be sure is to
actually
see what the driver assigned as the MAC address:
$ cat /sys/class/net/wlan0/address
What's returned by that is the MAC address as set up by the driver. That should match the value in the ifcfg file's HWADDR field.
There is also the little pesky detail that the computer remembers the address that it last used and requests that of the DHCP server. Modulo the server involved it will give the requested address regardless of whether it has a formal assignment for that MAC to another address or not. You may have to tell the computer to formally release the current DHCP assignment before going off to request a new one.
{o.o} Been bit by this one before. It's also painful to change a computer's name on a network in which the dhcpd updates the named. Absurdly short TTLs helps.
OK, I believe I've isolated the source of the problem. The wireless interface on pvr (the client) is a USB device, (Roswell RNX-G) delivers a different MAC address on reboot and whenever its removed and replaced in its USB socket. When the MAC changes, the router delivers a new IP address, and everything I've observed follows.
I presume that the Roswell RNX-G requires replacement, unless someone has a better idea.
Thanks to all who offered advice.
Am 04.02.2012 23:15, schrieb Geoffrey Leach:
OK, I believe I've isolated the source of the problem. The wireless interface on pvr (the client) is a USB device, (Roswell RNX-G) delivers a different MAC address on reboot and whenever its removed and replaced in its USB socket. When the MAC changes, the router delivers a new IP address, and everything I've observed follows.
I presume that the Roswell RNX-G requires replacement, unless someone has a better idea.
Thanks to all who offered advice.
is this a notebook? there is really no need of DHCP if you want to assign a static address why using layers over layers for static data at all?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/04/2012 04:20 PM, Reindl Harald wrote:
is this a notebook? there is really no need of DHCP if you want to
assign a static address why using layers over layers for static data at all?
I can give you a couple of reasons. First of all, if you use the notebook on more then one network, you may need to use DHCP on some of them. It works out better to have your home network use DHCP and get a fixed address.
For myself, I like having all the address assignments in one place. You can change things without having to log into several machines, and WEB interfaces. (I have 2 network printers, an IP camera, a print server, a media server, a media player, and a NAS that are fun to change.)
Mikkel - -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Am 04.02.2012 23:30, schrieb Mikkel L. Ellertson:
On 02/04/2012 04:20 PM, Reindl Harald wrote:
is this a notebook? there is really no need of DHCP if you want to
assign a static address why using layers over layers for static data at all?
I can give you a couple of reasons. First of all, if you use the notebook on more then one network, you may need to use DHCP on some of them. It works out better to have your home network use DHCP and get a fixed address.
and that is why my first question was IS IT A NOTEBOOK!
On 02/04/2012 02:32:33 PM, Reindl Harald wrote:
Am 04.02.2012 23:30, schrieb Mikkel L. Ellertson:
On 02/04/2012 04:20 PM, Reindl Harald wrote:
is this a notebook? there is really no need of DHCP if you want to
assign a static address why using layers over layers for static
data
at all?
I can give you a couple of reasons. First of all, if you use the notebook on more then one network, you may need to use DHCP on some of them. It works out better to have your home network use DHCP and get a fixed address.
and that is why my first question was IS IT A NOTEBOOK!
That depends on what the meaning of "is" is. :-)
The "network" looks like this. A notebook (mtranch, the server) hardwired to a router that in turn is connected to the internet. Said router receives a wireless feed from a standard PC (pvr, the client) whose only function is to receive HDTV via hardwired ethernet. The wireless connection is used by pvr to connect to mtranch for admin and to the internet for updates.
The notebook sits on my desk and does not go walkabout.
I'm clueless about DHCP. Pointers would be appreciated.
On 02/03/2012 04:52:39 PM, Rick Stevens wrote:
On 02/03/2012 02:39 PM, Geoffrey Leach wrote:
On 02/03/2012 01:54:34 PM, j.e.aneiros wrote:
On Fri, Feb 3, 2012 at 4:01 PM, Geoffrey Leachgeoff@hughes.net wrote:
A system on my local network (pvr) has its IP address in
/etc/hosts
geoff@pvr[1]->cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.10.2 pvr.mtranch.com pvr 192.168.10.3 mtranch.mtranch.com mtranch 192.168.10.1 Netgear 198.168.20.5 Homerun
Netgear router accessed from pvr via wireless. It has the address 192.168.10.2 reserved and assigned to pvr. Worked fine. Today
after
booting up the latest kernel, (3.2.2-1.fc16.i686.PAE), the IP
address
has changed to 192.168.10.5:
geoff@pvr[2]->ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr AE:5D:BA:91:67:2D inet addr:192.168.10.5 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::ac5d:baff:fe91:672d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:484 errors:0 dropped:0 overruns:0 frame:0 TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
you'll note that it is 192.168.10.5
Not surprisingly, I can't ssh 192.168.10.2, but I can ssh
192.168.10.5
Question: where is this (dynamic?) assignment taking place?
I think the machine is requesting the router a new IP and the
router
couldn't match the MAC of the request with the MAC associated to
the
reserved IP 192.168.10.2, so is giving a new IP in the range. Something change at the machine, did you check the MAC AE:5D:BA:91:67:2D against your rule in the router?
Your suspicion was correct. I replaced the one in use with the one
from
ifconfig. Unfortunately that did not fix the problem.
I need a tutorial on assigning MAC addresses, as they are
inconsistent
on the server and client. Is it correct that the MAC address is the same as HWADDR in the ifcfg file? And why would the value change
when
the hardware did not?
They're supposed to be the same. The only way to be sure is to actually see what the driver assigned as the MAC address:
$ cat /sys/class/net/wlan0/address
server geoff@mtranch[1]->cat /sys/class/net/wlan0/address 00:19:d2:2d:f2:76 client root@pvr[25]->cat /sys/class/net/wlan0/address ae:f2:65:4b:b2:16
So -- how do I resolve the difference? And how does the driver come up with the data?
On Fri, 2012-02-03 at 20:13 -0800, Geoffrey Leach wrote:
server geoff@mtranch[1]->cat /sys/class/net/wlan0/address 00:19:d2:2d:f2:76 client root@pvr[25]->cat /sys/class/net/wlan0/address ae:f2:65:4b:b2:16
So -- how do I resolve the difference? And how does the driver come up with the data?
Assuming server and client are two different machines, of course they have different MAC addresses.
poc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/03/2012 10:13 PM, Geoffrey Leach wrote:
server geoff@mtranch[1]->cat /sys/class/net/wlan0/address
00:19:d2:2d:f2:76 client root@pvr[25]->cat /sys/class/net/wlan0/address ae:f2:65:4b:b2:16 So -- how do I resolve the difference? And how does the driver come up with the data? Each NIC has its own MAC address assigned when it is made. In theory, you should never run into two NICs with the same MAC address. It is even possible to know what company the NIC is from by its MAC address.
Unless these are from the same machine, they need to be different. duplicating the MAC address on the same network is normally a "BAD THING"!
Mikkel - -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
-
Geoffrey Leach -
j.e.aneiros -
jdow -
Mikkel L. Ellertson -
Patrick O'Callaghan -
Reindl Harald -
Rick Stevens