# [EMAIL PROTECTED] / 2002-11-09 10:37:33 +:
On Sat, Nov 09, 2002 at 11:23:09AM +0100, Roman Neuhauser wrote:
A picture is worth a thousand words...
internet
|
v
eth0/12.34.56.78
linux (NAT)
eth1/10.1.0.200
|
hub 1 - Freepuppy de0/10.1.0.10
|
v
vx0/10.1.0.1
Lilith
ep0/10.0.0.1
|
hub 2
|
v
rl0/10.1.0.25
Ishtar
Lilith, Freepuppy, and that Linux box (called fw) can ping each other
w/o problems. Ishtar can ping (and be pinged by) the windows boxes in
the same hub. The problem is that nothing gets from Lilith to the other
side of hub 2, nor the other way around.
Does ishtar really have 10.1.0.25 as it's rl0 address? If so, that's
where the problem is. lilith is expecting that everything on the
10.1.0.0/24 network can be reached through it's vx0 interface.
no, that was a typo. the address was in fact 10.0.0.25.
turned out it *was* the cable between Lilith and hub 2 after all.
sounds unbelievable (to me at least), but through all the shuffling
of the components, this cable must have remained a constant.
I'm sorry about the wasted time.
Try renumbering everything hanging off hub 2 so that they are on the
10.0.0.0/24 network. Make sure that everything is using a /24
netmask. If you want ishtar and the other machines to be able to
access the internet, you'll need to add a route on fw telling it that
the 10.0.0.0/24 network can be reached via lilith's vx0 interface:
route add -net 10.0.0.0/24 10.1.0.1
(or whatever the exact syntax of the linux route command is).
since Lilith is meant as a replacement for the Linux box, I'm going
to set up ipnat on her instead. it's just a plain bimap ATM.
--
If you cc me or take the list(s) out completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
