[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: routing problem
mines still not resolved.. Im not running NAT at all.. Using all internet address space.
Let me maybe rephrase my problem and add some more information.. :)
>From the OpenBSD server I can ping 220.127.116.11. If I log into another server on a different vlan I can traceroute and ping 18.104.22.168. If I try this from a external server all I get on tcpdump is:
uplink-rtr-jhb:~# tcpdump -i fxp0 host 22.214.171.124
tcpdump: listening on fxp0
14:54:38.906715 arp who-has 126.96.36.199 tell 188.8.131.52
What I think is happening is the OpenBSD server does not route the packet via the destination and automatically assumes that this address is on the local network.
Here is what my setup looks like:
route add 184.108.40.206/24 220.127.116.11
PF is disabled..
fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
media: Ethernet autoselect (10baseT)
inet 18.104.22.168 netmask 0xfffffffc broadcast 22.214.171.124
inet6 fe80::207:e9ff:fe5a:c5c6%fxp0 prefixlen 64 scopeid 0x6
vlan3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
vlan: 5 parent interface: xl0
inet6 fe80::2a0:24ff:fe4a:84f3%vlan3 prefixlen 64 scopeid 0x17
inet 126.96.36.199 netmask 0xfffffffc broadcast 188.8.131.52
On Feb 19, 2004 05:03 AM, Len Jacobs <firstname.lastname@example.org> wrote:
> The routing problem was resolved... Surprise!
> I guess it might be a helpful listing in the FAQ, should be so obvious,
> but it was not. Unless NAT is setup & running (via pfctl/pf.conf)
> internal (nonroutable) IPs from the LAN cannot effectively reach the
> Internet (WAN). The internal addresses need a route back from the
> outside which is just what NAT provides.
> So running NAT resolved the non-routing problem I had been experiencing.
> Works like a charm now.
> Thansk for everyone's comments and suggestions.