Nick Rout wrote:
On Sat, 2005-04-02 at 18:08 -0500, John Lowell wrote:
Nick Rout wrote:
On Sat, 2005-04-02 at 16:26 -0500, John Lowell wrote:
Nick, Kashani, jstubbs and others,
OK, *ifconfig *...
eth0 Link encap:Ethernet HWaddr 00:04:75:DC:B8:4E inet addr:192.168.1.44 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110 errors:0 dropped:0 overruns:1 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 RX bytes:37007 (36.1 Kb) TX bytes:0 (0.0 b)
Interrupt:9 Base address:0xfc00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b
and *route -n *...
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
There is very clearly a problem with the Gateway number and, perhaps, the Destination as well? A kernel problem, perhaps?
user problem I think. Someone pointed out to you at the start of ther thread that you have the broadcast address wrong and you still haven't fixed it.
and then set gateway in the config file.
then restart the net.eth0 service.
Thoughts?
jlowell
-- [email protected] mailing list
Nick,
I've solved the problem but it has nothing to do with the broadcast number and setting the gateway. Initially, changing broadcast to 192.168.1.255 and leaving the gateway setting where it has always been in /etc/conf.d/net, 192.168.1.1, gives no relief. Still can't ping the outside world. But running route add default gw 192.168.1.1 and pinging the web works. I've never had to do this before to get this box to the outside. The gateway address in /etc/conf.d/net has always been right, and frankly, I doubt if changing broadcast would have made any difference either. I can test that if you'd like. The way I read it, somehow the installation program isn't doing what it did the last time I installed gentoo.
I'd appreciate knowing why it was necessary for me to run this command to fix the problem when /etc/conf.d/net was edited properly. Is this a bug?
jlowell
Stuffed if I know, but could you give us the exact gateway line from /etc/conf.d/net?
-- [email protected] mailing list
Hi Nick,
Here's the whole of /etc/conf.d/net. Other than the "1" in broadcast it's been the same since the beginning. But changing the broadcast number hasn't meant a hill of beans of difference.
# /etc/conf.d/net: # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/conf.d/net,v 1.7 2002/11/18 19:39:22 azarah Exp $
# Global config file for net.* rc-scripts
# This is basically the ifconfig argument without the ifconfig $iface # iface_eth0="192.168.1.44 broadcast 192.168.1.255 netmask 255.255.255.0" #iface_eth1="207.170.82.202 broadcast 207.0.255.255 netmask 255.255.0.0"
# For DHCP set iface_eth? to "dhcp" # For passing options to dhcpcd use dhcpcd_eth? # #iface_eth0="dhcp" #dhcpcd_eth0="..."
# For adding aliases to a interface # #alias_eth0="192.168.0.3 192.168.0.4"
# NB: The next is only used for aliases. # # To add a custom netmask/broadcast address to created aliases, # uncomment and change accordingly. Leave commented to assign # defaults for that interface. # #broadcast_eth0="192.168.0.255 192.168.0.255" #netmask_eth0="255.255.255.0 255.255.255.0"
# For setting the default gateway # gateway="192.168.1.1"
As you can see, the gateway number was entered correctly yet it's not being read that way by the system. I mean I'm perfectly happy to take the blame for this problem but I can't see what I've done wrong to justly acknowledge wrong-doing. I've installed gentoo probably 25 times over the last three years on various machines and have never encountered a need to use the route command to fix something. It may help to know that I ran the Feather Linux livecd with boot options set in such a way as to exclude a network configuration, configuring it with their graphical tool once I'd reached their desktop. Feather works using the self same configuration which leads me to conclude what is becoming more and more clear: That the problem is with gentoo, which worries me. One last question, might this be a kernel problem, a failure to check something in menuconfig?
Thanks for your attention to my questions, Nick.
jlowell
-- [email protected] mailing list
