Re: cannot ping anything



thanks, but the defaultrouter line was already present in my /etc/rc.conf.

On Jan 20, 2006, at 1:32 PM, Derek Ragona wrote:

Check your /etc/rc.conf for this line:
defaultrouter="192.168.1.1"

add it and reboot if it is missing

        -Derek


At 12:26 PM 1/20/2006, Alvaro J. Gurdián wrote:
Yesterday I placed an HD with Freebsd 5.3 release in a Dell Dimension L800CXE. It booted properly. ( since it's running a generic kernel with only a name change)

However I could not ping anything inside or outside the LAN.
Ex:
ping google.com
ping: cannot resolve google.com: Hostname lookup failure

ping 192.168.1.1
ping: sendto: No route to host

I tried several addresses inside the LAN, 127.0.0.1, localhost, 192.168.1.128, and all gave the same result.

I was previously using this HD in another machine to test IPF, with NAT also, and it worked peerfectly there.


So just to be safe I erased the contents of /etc/rc.conf, and then used sysinstall to bring up my NIC. I chose NO for IPv6, and YES for DHCP.


That seemed to work correctly, just to be sure I ran ifconfig:
dc0: flags=108843<UP,BROACAST,RUNNING,SIMPLEX,MULTIPLY> MTU 1500
        options=8<VLAN_MTU>
        inet 192.168.1.128 netmask 0xffffff00 broadcast 192.168.1.255
        ether 00:80:ad:81:1a:9f
        media: Ethernat autoselect (100baseTX)
        status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,SIMPLEX,MULTICAST> mtu 1500
        inet 127.0.0.1 netmask 0xff000000

Still, things are looking good; so, I go to another box, log into my router(192.168.1.1), and I can see the MAC address of the BSD box on my router.


However, I still get the same results when I ping as I did above.

Then I checked the routing tables:

netstat -r
Routing Tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGS 0 6 dc0
localhost localhost UH 1 37 lo0
192.168.1 link#1 UC 0 0 dc0
192.168.1.1 00:0c:41:bd:49:7d UHLW 1 0 dc0 695
192.168.1.128 localhost UGHS 0 0 lo0


The output of netstat and ifconfig aboe are from today. I began having this problem yesterday, and left the box on over night. Yesterday's output was different in that the BSD box had a different IP address, 192.168.1.122. That is fine I understand that the box is communicating with the router and negotiating leases when they expire. However, why has the gateway to 192.168.1.1 changed from link#1 to the MAC address of my router. I am certain that if I restart the computer that same gateway will revert to link#1.

The my questions are:
How do I get the system to see others in the network, and vice-versa?
What should the gateway for 192.168.1.1 be?(which also happens to be my routers address)



I am hoping it is something simple. I could just as have easily reinstalled the system and started from scratch, but I wanted to know how to solve this problem.


Other info that might help:
less /etc/rc.conf
ifconfig_dco="DHCP"
hostname="fw.company.com"
defaultrouter="192.168.1.1"

less /etc/resolv.conf
search carolina.rr.com
nameserver 24.25.5.60
naemserver 24.25.5.61

less /etc/hosts
::1                     localhost.company.com   localhost
127.0.0.1               localhost.company.com   localhost

Thanks in advance

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



_______________________________________________ freebsd-questions@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Browsing Web Pages
    ... ping it with a 1472 byte packet, then ping his machine's gateway ... address with a 1472 byte packet, then ping the next gateway with 1472 byte ... if he pings a router that returns a time out or "Packet needs to be ... Then find the issue with that router as to why it is using a reduced MTU ...
    (microsoft.public.windows.server.dns)
  • Re: Cant connect using network
    ... You now disconnect one device from your network after the other until the ping command reports a timeout. ... Default Gateway: 192.168.1.64 ... The router is defective. ... Neither are working and the message I get from both of them is that there is no or limited connectivity. ...
    (microsoft.public.windowsxp.general)
  • bridge troubles with wi
    ... I'm trying to configure my freebsd machine as an adsl router wifi access ... router) but unable to access internet, or ping the router. ... the lan ip of my router is 10.0.2.1 on rl0 ... rl0: flags=8943mtu 1500 ...
    (freebsd-stable)
  • cannot ping anything
    ... However I could not ping anything inside or outside the LAN. ... dc0: flags=108843MTU 1500 ... That is fine I understand that the box is communicating with the router and negotiating leases when they expire. ... why has the gateway to 192.168.1.1 changed from link#1 to the MAC address of my router. ...
    (freebsd-questions)
  • Re: Server 2003 access the internet
    ... I would first check cables and try to switch ports on router. ... any filtering enabled on router (like MAC filtering). ... your gateway what is the message that you get? ... Ping timeout or something ...
    (microsoft.public.windows.server.networking)