On Tue, May 08, 2007 at 07:30:07AM -0700, Dan Nicholson wrote:
> On 5/8/07, Roland Puntaier <[EMAIL PROTECTED]> wrote:
> >
> > After making an LFS system according the instructions I have the following
> > networking problem.
>
> So, it'll be good to narrow down the problem since there are lots of
> ways networking could go wrong.
>
> > ping 10.43.70.1:
> > PING 10.43.70.1 (10.43.70.1): 56 data bytes
> > 64 bytes from LFS.br-automation.com (10.43.70.207): Destination Host
> > Unreachable
>
> This host (10.43.70.1) is external, right? Since you're not using DNS,
> then something must be with your gateway settings.
I'm sure Dan will spot that the ping was _to_ the gateway when he
looks at this- easily done, I'm sure I've made similar assumptions
myself ;)
>
> > cat /etc/udev/rules.d/26-network.rules:
> > ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:60:08:73:6d:19",
> > NAME="ethcard1"
>
> This seems fine, although I'm not sure why you'd change it to ethcard1.
>
Agreed. For a single eth port, persistent naming shouldn't be
necessary (of course, for a machine with two ports built in, it's
probably a good idea for consistency across kernel upgrades). But,
it is another point of failure - is the sysfs address correct ?
If in doubt, '/sbin/ip link' show should show the interfaces
(ethernet, lo). If the hardware address is correct, and the
interface is up, probably a cable problem. If the address is
correct but interface is not up, probably a kernel config problem
(wrong nic driver).
> > cat /etc/sysconfig/network-devices/ifconfig.ethcard1/ipv4:
> > ONBOOT=yes
> > SERVICE=ipv4-static
> > IP=10.43.70.207
> > GATEWAY=10.43.70.1
> > PREFIX=24
> > BROADCAST=10.43.70.255
>
> This is where any problem would be. You're sure gateway is correct? Do
> you normally use DHCP on this network? Maybe it would be better to
> install one of the DHCP clients from BLFS.
>
I disagree - the only reasons to use dhcp on an inital build are
if you can't identify an available ip address, or if you don't have
a dhcp server. So, provided 10.43.70.207 isn't available for
offers from *any* dhcp server, and isn't already assigned to another
box, a static address is one less thing to go wrong.
Of course, if the rest of the local network uses dhcp, changing to
a dhcp client after the current issue is sorted will be a good idea.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
