General Questions

I have a SpeedTouch 510v4 ADSL router connected to my ADSL line. I have an old pc with two Lan cards running mono wall. My plan was to use monowall for all the routing and nat work and simply use the Speedtouch as an ADSL modem. 

You can configure the SpeedTouch using special config files in to DHCP spoofing mode. This simply uses DHCP to pass the WAN address to the first client that connects. It then passes all traffic to that machine too, so no NAT is applied.

My problem is when I try this the DHCP info it sends back is very odd. When I hook it up directly to a PC this is the DHCP info it sends back.

IPAddress: 81.178.30.***
Sub Net: 255.255.255.0
Gateway:  62.241.161.***

Of course thats nonsence becuase the gateway should be on the local subnet otherwise it can't send the IP traffic onwards.

When I dial up with an old Speedtouch 330 usb modem on XP the info it gives is:

Clinet Address: 81.178.30.***
Server Address: 62.241.161.***

So its not hard to see where the speedtouch 510 is getting those addresses from. Is there some way to force monowall to route all traffic bound for the WAN interface  to the gateway address.

It is so close to working because the monowall firewall logs show its blocked inbound udp traffic. So its as though data is coming in on the WAN but can't be sent on it.

Any help would be greatly appreaciated.

Charlie

I still haven't solved the DHCP_SPOOFING problem with the SpeedTouch 510v4.

I have found a work around. I managed to set the router in "Bridged Ethernet" mode. This allows me to use PPPoE on MonoWall to connect to the SpeedTouch 510 using PPPoE. As I understand it this requires the ISP / Carrier to support PPPoE. Anyway this solution seems to be working well so I think I will abandon DHCP_SPOOFING for the time being.

Charlie

You won't be able to get it to work if your ISP assigns a default gateway outside your WAN subnet. While Windows, ridiculously, will take anything you throw in as a default gateway and if it answers ARP it'll use it, FreeBSD won't add the default route if you give it a gateway outside your WAN subnet (the way it *should* be, IMO). Unfortunately that means if your ISP doesn't understand how networks are supposed to work and does something stupid like this, it leaves you screwed.

Glad you found a work around though.