Hello, What sort of box is your default gateway? (Possibilities for running tcpdump on the gateway?) If you do, you could check the interfaces on the gateway, that the packets get routed to another interface on the gateway. There could be a number of configuration options on the gateway producing the problems you see, including : 1. Firewall allowing only certain addresses. 2. Network Address Translation mapping only to certain addresses.
You could try to use an unused address from the dhcp pool and assign this statically for testing. Presumably when you say you can ssh into the box, your ssh client is on the same subnet? Name resolution could be proxied at the gateway, explaining why that works. I would take a close look at your gateway configuration. You could also check that the routing table selects the right outgoing gateway. Check with route get 1.2.3.4 This should produce something like : route to: 1.2.3.4 destination: default mask: default gateway: x.x.x.x interface: vlan10 This would test that the routing table not only looks right, but that the right routing decision is made. Cheers, Simon. On Fri Feb 27 10:20 , Ruan Kendall sent: I've come across a strange problem whereby configuring an interface with DHCP lets my system run absolutely fine, but assigning a static IP to the nic results in a system that can only speak to the local subnet. I can ssh into it, but cannot connect to any machines on the internet. The computer and internet connection are otherwise quite functional. In both cases, the adresses are in the same subnet, have the same subnet mask and default gateway. Output of ifconfig and route -rn look all but identical. In both cases, name resolution works just fine also. Tcpdump shows that when I ping a machine external to my subnet, outgoing packets are sent to the MAC address of my router. Only in the case of the statically configured adress, I never get any response. Handful of diagnostic information shown below. Evidently, I'm doing something stupid and wrong, but I seem to be quite unable to recognise what on earth it is. Does anyone have any suggestions? When dhclient is used to configure interface (by doing dhclient sis0): ifconfig sis0 sis0: flags=8843 mtu 1500 lladdr 00:00:24:c3:d6:cc groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::200:24ff:fec3:d6cc%sis0 prefixlen 64 scopeid 0x1 inet 192.168.1.34 netmask 0xffffff00 broadcast 192.168.1.255 netstat -rn, minus ipv6 stuff Destination Gateway Flags Refs Use Mtu Prio Iface default 192.168.1.1 UGS 0 2 - 48 sis0 127/8 127.0.0.1 UGRS 0 0 33204 48 lo0 127.0.0.1 127.0.0.1 UH 2 0 33204 48 lo0 192.168.1/24 link#1 UC 1 0 - 48 sis0 192.168.1.1 00:13:49:b0:cb:91 UHLc 1 1 - 48 sis0 192.168.1.34 127.0.0.1 UGHS 0 0 33204 48 lo0 224/4 127.0.0.1 URS 0 0 33204 48 lo0 When adress is configured using following hostname.if file (either by rebooting the box, or running /etc/netstart): inet 192.168.1.200 255.255.255.0 NONE ifconfig sis0 sis0: flags=8843 mtu 1500 lladdr 00:00:24:c3:d6:cc groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::200:24ff:fec3:d6cc%sis0 prefixlen 64 scopeid 0x1 netstat -rn, minus ipv6 stuff Destination Gateway Flags Refs Use Mtu Prio Iface default 192.168.1.1 UGS 0 3 - 48 sis0 127/8 127.0.0.1 UGRS 0 0 33204 48 lo0 127.0.0.1 127.0.0.1 UH 1 0 33204 48 lo0 192.168.1/24 link#1 UC 1 0 - 48 sis0 192.168.1.1 00:13:49:b0:cb:91 UHLc 1 1 - 48 sis0 224/4 127.0.0.1 URS 0 0 33204 48 lo0 Adding !route add default 192.168.1.1 to the end of the hostname.if file has no effect. Adding in a route from 192.168.1.200 to 127.0.0.1 mimicking the extra route dhclient sets up has no effect. ------------------------------------------------------------------------- Fe din egen, gratis e-postadresse pe Start.no
