Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #1527 > unrolled thread
| Started by | Jim Anderson <jjanderson52000@yahoo.com> |
|---|---|
| First post | 2012-07-27 12:07 -0400 |
| Last post | 2012-08-10 06:13 +0000 |
| Articles | 6 — 6 participants |
Back to article view | Back to comp.os.linux.networking
controlling the 'eth0' device that gets detect by ifconfig Jim Anderson <jjanderson52000@yahoo.com> - 2012-07-27 12:07 -0400
Re: controlling the 'eth0' device that gets detect by ifconfig Alastair Black <abqab.nemo@example.net> - 2012-07-27 11:48 -0600
Re: controlling the 'eth0' device that gets detect by ifconfig Ian Zimmerman <itz@buug.org> - 2012-07-28 10:34 -0700
Re: controlling the 'eth0' device that gets detect by ifconfig Richard Kettlewell <rjk@greenend.org.uk> - 2012-07-28 18:32 +0100
Re: controlling the 'eth0' device that gets detect by ifconfig Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-07-28 21:50 +0000
Re: controlling the 'eth0' device that gets detect by ifconfig Gordon <Gordon@clear.net.nz> - 2012-08-10 06:13 +0000
| From | Jim Anderson <jjanderson52000@yahoo.com> |
|---|---|
| Date | 2012-07-27 12:07 -0400 |
| Subject | controlling the 'eth0' device that gets detect by ifconfig |
| Message-ID | <juuf5f$j2u$1@speranza.aioe.org> |
I used to run Kubuntu linux and my network addresses would be detected properly during startup. I have switched to crunchbang linux and my network runs ok except on one PC the OS is not detecting the correct port for eth0 and I don't know how to fix the problem. The network has two routers, one wireless and one wired using ethernet ports. The wired router is connected to a DSL line so all of the wired PCs should be directed to that router to connect to the world. Unfortunately, the problem PC detects the wireless router for the 'eth0' device. When I run the route command, the default address is 192.168.2.1, the address of the wireless router, not 192.168.0.1, the address of the wired router. If I disconnect the wireless router and reboot, then I think it is detected the correct router, but when I run ifconfig, the ethernet address is in inet6, not an inet4 address. If there a way to force the inet4 address of the wired router to be detected? Jim Anderson
[toc] | [next] | [standalone]
| From | Alastair Black <abqab.nemo@example.net> |
|---|---|
| Date | 2012-07-27 11:48 -0600 |
| Message-ID | <juuk8r$gn7$1@n102.xanadu-bbs.net> |
| In reply to | #1527 |
On 07/27/2012 10:07 AM, Jim Anderson wrote: > > I used to run Kubuntu linux and my network addresses would be detected > properly during startup. I have switched to crunchbang linux and my > network runs ok except on one PC the OS is not detecting the correct > port for eth0 and I don't know how to fix the problem. > > The network has two routers, one wireless and one wired using ethernet > ports. The wired router is connected to a DSL line so all of the wired > PCs should be directed to that router to connect to the world. > Unfortunately, the problem PC detects the wireless router for the > 'eth0' device. > > When I run the route command, the default address is 192.168.2.1, the > address of the wireless router, not 192.168.0.1, the address of the > wired router. If I disconnect the wireless router and reboot, then I > think it is detected the correct router, but when I run ifconfig, the > ethernet address is in inet6, not an inet4 address. > > If there a way to force the inet4 address of the wired router to be > detected? > > Jim Anderson gksu ifconfig wlan0 down Alastair
[toc] | [prev] | [next] | [standalone]
| From | Ian Zimmerman <itz@buug.org> |
|---|---|
| Date | 2012-07-28 10:34 -0700 |
| Message-ID | <878ve3pz5o.fsf@foolinux.dyndns.org> |
| In reply to | #1528 |
The following message is a courtesy copy of an article that has been posted to comp.os.linux.networking as well. Jim> If there a way to force the inet4 address of the wired router to be Jim> detected? Alastair> gksu ifconfig wlan0 down A more permanent fix would be to blacklist the wifi driver in a file such as /etc/modprobe/local-blacklist.conf. -- Ian Zimmerman gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD http://www.gravatar.com/avatar/c66875cda51109f76c6312f4d4743d1e.png Rule 420: All persons more than eight miles high to leave the court.
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <rjk@greenend.org.uk> |
|---|---|
| Date | 2012-07-28 18:32 +0100 |
| Message-ID | <87obmz7pw6.fsf@araminta.anjou.terraraq.org.uk> |
| In reply to | #1527 |
Jim Anderson <jjanderson52000@yahoo.com> writes: > I used to run Kubuntu linux and my network addresses would be detected > properly during startup. I have switched to crunchbang linux and my > network runs ok except on one PC the OS is not detecting the correct > port for eth0 and I don't know how to fix the problem. > > The network has two routers, one wireless and one wired using ethernet > ports. The wired router is connected to a DSL line so all of the wired > PCs should be directed to that router to connect to the > world. Unfortunately, the problem PC detects the wireless router for > the > 'eth0' device. > > When I run the route command, the default address is 192.168.2.1, the > address of the wireless router, not 192.168.0.1, the address of the > wired router. It sounds like you've got both routers acting as a DHCP server for the same bit of network. There's no way that's going to be reliable. > If I disconnect the wireless router and reboot, then I think it is > detected the correct router, but when I run ifconfig, the ethernet > address is in inet6, not an inet4 address. IPv6 addresses often contain modified forms of the MAC address; that's normal. -- http://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2012-07-28 21:50 +0000 |
| Message-ID | <slrnk18nls.ph6.grahn+nntp@frailea.sa.invalid> |
| In reply to | #1529 |
On Sat, 2012-07-28, Richard Kettlewell wrote: > Jim Anderson <jjanderson52000@yahoo.com> writes: ... >> If I disconnect the wireless router and reboot, then I think it is >> detected the correct router, but when I run ifconfig, the ethernet >> address is in inet6, not an inet4 address. > > IPv6 addresses often contain modified forms of the MAC address; that's > normal. Well, the thing is, if you have IPv6 enabled, each interface will have at least a "Scope:Link" IPv6 address. It's not the presence of that one but the absence of the IPv4 one that's important. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | Gordon <Gordon@clear.net.nz> |
|---|---|
| Date | 2012-08-10 06:13 +0000 |
| Message-ID | <a8jn3tFfdcU5@mid.individual.net> |
| In reply to | #1527 |
On 2012-07-27, Jim Anderson <jjanderson52000@yahoo.com> wrote: > > I used to run Kubuntu linux and my network addresses would be detected > properly during startup. I have switched to crunchbang linux and my > network runs ok except on one PC the OS is not detecting the correct > port for eth0 and I don't know how to fix the problem. > > The network has two routers, one wireless and one wired using ethernet > ports. The wired router is connected to a DSL line so all of the wired > PCs should be directed to that router to connect to the world. > Unfortunately, the problem PC detects the wireless router for the > 'eth0' device. > > When I run the route command, the default address is 192.168.2.1, the > address of the wireless router, not 192.168.0.1, the address of the > wired router. If I disconnect the wireless router and reboot, then I > think it is detected the correct router, but when I run ifconfig, the > ethernet address is in inet6, not an inet4 address. > > If there a way to force the inet4 address of the wired router to be > detected? > Sure, make the address of your network card on the PC, static. Say 192.168.2.103, which is outside the DHCP range of the router. If you have only one LAN. Then as another poster has hinted at drop the second DHCP. Having two DCHPs battle it out is not really the way to go.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.networking
csiph-web