[nsp] Bridging?

Thu Apr 29 04:03:10 EDT 2004

... ok, found the "mac-address" command on the Serial interface:

2621#sh ru int s0/1:0
Building configuration...

Current configuration : 149 bytes
!
interface Serial0/1:0
 mac-address 0001.4255.8f40
 ip address 10.159.159.201 255.255.255.252
 encapsulation ppp
 no cdp enable
 ppp bridge ip
end

But, although the Ethernet host at the other end sees the MAC address, the
router does not seem to install the MAC address in its own arp table!...

2621#sh arp | i 10.159.159.20
Internet  10.159.159.202          3   0006.d6ca.4800  ARPA   Serial0/1:0
2621#

I only see the remote!

Looks like a bug, right? Or am I missing some magic piece of config?

Vincent

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of 
> Vincent De Keyzer
> Sent: jeudi 29 avril 2004 9:52
> To: cisco-nsp at puck.nether.net
> Subject: RE: [nsp] Bridging?
> 
> 
> Bruce,
> 
> thank you so much! PPP half-bridging is exactly what I am 
> trying to achieve.
> 
> Now Serial0/0:0 is up (ppp neg complete), but there is a MAC address
> problem: when I am trying to ping from the Ethernet host, 
> here is what I see on the E1 router:
> 
> *Mar  1 23:54:03.006 CET: IP ARP: rcvd req src 10.159.159.202 
> 0006.d6ca.4800, dst 10.159.159.201 Serial0/1:0 *Mar  1 
> 23:54:03.010 CET: IP ARP: creating entry for IP address: 
> 10.159.159.202, hw: 0006.d6ca.4800 *Mar  1 23:54:03.010 CET: 
> %IP-4-ZERO_ADDR: Zero MAC address for 10.159.159.201 in ARP 
> cache 2621#sh arp | i 10.159.159.20
> Internet  10.159.159.202          2   0006.d6ca.4800  ARPA   
> Serial0/1:0
> 2621#
> 
> Config is as follows:
> 
> 2621#sh ru int s0/1:0
> Building configuration...
> 
> Current configuration : 121 bytes
> !
> interface Serial0/1:0
>  ip address 10.159.159.201 255.255.255.252
>  encapsulation ppp
>  no cdp enable
>  ppp bridge ip
> end
> 
> 2621#
> 
> So it seems that it does not work because there is no MAC 
> address assigned to this serial interface.
> 
> How can I assign one?...
> 
> Vincent
> 
> 
> > -----Original Message-----
> > From: Bruce Pinsky [mailto:bep at whack.org]
> > Sent: mercredi 28 avril 2004 23:09
> > To: Vincent De Keyzer
> > Cc: cisco-nsp at puck.nether.net; 'Todd, Douglas M.'
> > Subject: Re: [nsp] Bridging?
> > 
> > 
> > Vincent De Keyzer wrote:
> > 
> > > Douglas,
> > > 
> > > your efforts to understand my problem are remarkable and I highly
> > > appreciate them.
> > > 
> > > But I haven't been clear enough once again (I could say
> > it's because
> > > english is not my mother language, but I am not sure I
> > could do better
> > > in french... :) so let me
> > > try another way.
> > > 
> > > IP ranges:
> > > A.B.1.0/24: backbone ranges
> > > A.B.2.0/24: PtP (/30) ranges
> > > A.B.3.0/24: customer X range
> > > A.B.4.0/24: customer Y range
> > > 
> > > Current situation:
> > > * a 2621 with
> > > Fa0/0 = A.B.1.2/28
> > > Serial 0/0:0 = A.B.2.1/30 for customer X
> > > Serial 0/1:0 = A.B.2.5/30 for customer Y
> > > * customer X has a 1600+CSU/DSU with
> > > Serial0 = A.B.2.2/30
> > > Ethernet0 = A.B.3.1/24
> > > * customer X has a firewall with
> > > WAN = A.B.3.2/24
> > > * customer Y has a 1600+CSU/DSU with
> > > Serial0 = A.B.2.6/30
> > > Ethernet0 = A.B.4.1/24
> > > * customer Y has a firewall with
> > > WAN = A.B.4.2/24
> > > 
> > > The 2621 is routing IP packets between customer ranges
> > A.B.3.0/24 and
> > > A.B.4.0/24 and the core network behind Fa0/0.
> > > 
> > > And, after replacing the (1600+CSU/DSU) by a E1/Eth 
> bridge, I would
> > > like it to become:
> > > * a 2621 with
> > > Fa0/0 = A.B.1.2/28
> > > Whatever0 = A.B.3.1/24
> > > Whatever1 = A.B.4.1/24
> > > * customers X&Y have an E1/Eth bridge and their FWs keep the same 
> > > config
> > > 
> > > ... where "Whatever" interfaces are whatever kind of interface it
> > > takes to have this working...
> > > 
> > > Now maybe this is now even called bridging... but is it possible?
> > > 
> > > The goal is of all this is to replace 1600+CSU/DSU by less
> > expensive
> > > equipment where it's not required.
> > > 
> > 
> > Sounds like you want PPP half-bridging.   See: 
> > http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1831
> /products_configuration_guide_chapter09186a00800d9845.html#1001479
> 
> So at the customer site, you need an E1/Eth bridge that does 
> PPP on the E1 
> side.
> 
> -- 
> =========
> bep
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.670 / Virus Database: 432 - Release Date: 27/04/2004
>  
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.670 / Virus Database: 432 - Release Date: 27/04/2004
>  
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco> -nsp
> archive at 
> http://puck.nether.net/pipermail/cisco-nsp/
> 
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.670 / Virus Database: 432 - Release Date: 27/04/2004
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.670 / Virus Database: 432 - Release Date: 27/04/2004