[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bridging



hi
 
> > rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
> > 1500
> [...]
> >         inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
> 
> and:
> 
> > rl1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
> > 1500
> [...]
> >         inet 192.168.1.4 netmask 0xffffff00 broadcast 192.168.1.255
> 
> you only need an ip on one of the bridging interfaces to be accessable
> through both.
> if you really need the two ips for the pc, add an alias to rl0.
> 
> > rl0 is connected to my network with a ethernet cable.
> > on rl1 i connected a laptop with a crossover cable, and i let it ping
> > loads of times, however, a 
> >   tcpdump -n -i rl1
> > just shows me arp requests, not arp replies!
> > Why does rl1 not answer and learn??
> 
> try removing the ip of rl1 (just put 'up' into the hostname.rl1) and
> ping the ip of rl0. 

Ok, i have removed the ip of rl1.
Then i pinged the ip of rl0.

>as it is bridged, you'll be able to ping it.
> 
ping what? rl1 which has no ip, or rl0 which i could already ping before?

-- 
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl



Visit your host, monkey.org