pppoe oddidies now critical

miahac · January 28, 2008, 4:53pm

My pppoe connections are not able to access local IP’s but can access remote ip’s fine.
Here is my config:

Inside. Ether2

Outside. Ether1
63.xx.125.2/25
Gateway 63.xx.125.1

PPPoE is listening on ether2
There is a hotspot on ether2

PPPoE-pool hands out public IP’s 63.xx.125.65-70 and local address of 63.xx.125.2

The problem is that clients on pppoe cannot access the servers on 63.xx.125.x/25 and sometimes see remnants of the hotspot pages like redirects etc.

Is there something obvious I am missing?

miahac · January 28, 2008, 4:58pm

I have proxy arp enabled on the outside interface.

And something more strange.
If I look in the IP hotspot hosts, I see denied addresses that are from within the linksys router that is the ppppe client.

miahac · January 28, 2008, 7:59pm

sorry for posting in the wrong forum.

miahac · January 29, 2008, 2:38pm

no takers?

EgyCom · January 29, 2008, 5:05pm

If I‘m in your situation I will use separated interfaces for Hotspot and PPPoE server , put both on same switch and don’t assign IP for PPPoE Ethernet interface.

miahac · January 30, 2008, 3:02pm

so should I run two cable to every floor in the building, two switches on each floor and patch in the customer to the phone closet one or the other depending if the have a router/and phone service or not?

Back to reality.

Your idea of separation might work if I were to only logically separate the interfaces. I will try to add a bridge, move put only the inside interface in the bridge, put the hotspot on the bridge interface and leave the PPPoE on the ethernet.

Update:
It seems to only be two client router, and my router that are doing this. Both are linksys but different models. WRT54g version 2 and a BESF8R.

miahac · February 1, 2008, 2:23pm

it seems the problem was with the linksys client routers. I replaced (the besf8r) one with a rb and the other (wrt54g) was fixed with a firmware upgrade.