[ previous ] [ next ] [ threads ]
 
 From:  ubi de feo <ubi at twodotone dot com>
 To:  Fred Wright <fw at well dot com>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] WAN as DHCP and unreachable gateway
 Date:  Fri, 23 Jul 2004 09:51:31 +0200
hi fred.

this is the working configuration
the 10.0.0.138 is my modem IP.
the process is called DHCP spoofing and works forwarding to the first 
interface connected on the wan side of the modem
all the dhcp data from the ISP
this way your machine uses the modem as a dumb modem (more or less)

it's not a transient state.
i'm not in my ISP mind to know why they send me a gateway that is not 
in the same subnet.
but i can assure you it works.

if i run apache on my powerbook or IIS on my xp when this configuration 
is on, everything works fine.
the machine is publicly accessible.

only mono refuses to get the gateway.

i just need to know why and how to solve this

:)

ciao.ubi



On Jul 23, 2004, at 9:17 AM, Fred Wright wrote:

>
> On Thu, 22 Jul 2004, ubi de feo wrote:
>
>> now, here's the situation i face after setting the WAN interface as 
>> DHCP
>> i think the only thing i'm actually missing is the right RULE for the
>> firewall.
>>
>> i went through many steps.
>> first tried getting everything working on XP.
>> it does
>>
>> here it is
>>
>> Ethernet adapter Local Area Connection 3:
>>
>>          Connection-specific DNS Suffix  . : lan
>>          Description . . . . . . . . . . . : Realtek RTL8139 Family 
>> PCI
>> Fast Eth
>> rnet NIC #3
>>          Physical Address. . . . . . . . . : 00-10-A7-2A-7F-B4
>>          Dhcp Enabled. . . . . . . . . . . : Yes
>>          Autoconfiguration Enabled . . . . : Yes
>>          IP Address. . . . . . . . . . . . : 213.84.18.xxx
>>          Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>          Default Gateway . . . . . . . . . : 195.190.249.11
>>          DHCP Server . . . . . . . . . . . : 10.0.0.138
>>          DNS Servers . . . . . . . . . . . : 10.0.0.138
>>                                              194.109.104.104
>>                                              194.109.6.66
>>          Lease Obtained. . . . . . . . . . : Thursday, July 22, 2004
>> 10:43:35 PM
>>          Lease Expires . . . . . . . . . . : Thursday, July 22, 2004
>> 10:44:05 PM
>
> Are you sure this is really the configuration at the time it's working,
> and not some transient state?  Or are you using PPTP to the modem?  Or 
> do
> you have an additional static route?  Having a gateway in a different
> subnet than your IP is useless unless it's a point-to-point link.  What
> does "netstat -rn" (or the XP equivalent) show?
>
> The 10.0.0.138 is your *modem*.  How does your *modem* know to come up
> with that 213.xxx address?  Are some of these addresses configured into
> the modem?  And note that your modem is listed as one of the DNS 
> servers
> as well.  What happens if you turn off the DHCP and DNS server 
> features in
> the modem?
>
>> then i checked the m0n0 logs
>>
>> here they are
>>
>> Jul 22 20:46:20 dhclient: bound to 213.84.18.234 -- renewal in 12
>> seconds.
>> Jul 22 20:46:16 dhcpd: For info, please visit
>> http://www.isc.org/products/DHCP
>> Jul 22 20:46:16 dhcpd: All rights reserved.
>> Jul 22 20:46:16 dhcpd: Copyright 1995-2003 Internet Software 
>> Consortium.
>> Jul 22 20:46:16 dhcpd: Internet Software Consortium DHCP Server
>> V3.0.1rc11
>> Jul 22 20:46:16 dhclient: New Routers: 195.190.249.11
>> Jul 22 20:46:16 dhclient: New Broadcast Address (sis1): 213.84.18.255
>> Jul 22 20:46:16 dhclient: New Subnet Mask (sis1): 255.255.255.0
>> Jul 22 20:46:16 dhclient: New IP Address (sis1): 213.84.18.234
>> Jul 22 20:46:16 dhclient: New Broadcast Address: 213.84.18.255
>> Jul 22 20:46:16 dhclient: New Network Number: 213.84.18.0
>> Jul 22 20:46:16 dhclient: DHCPACK from 10.0.0.138
>> Jul 22 20:46:16 dhclient: DHCPREQUEST on sis1 to 255.255.255.255 port 
>> 67
>> Jul 22 20:46:16 dhclient: DHCPOFFER from 10.0.0.138
>> Jul 22 20:46:15 dnsmasq[2838]: using nameserver 10.0.0.138#53
>> Jul 22 20:46:15 dnsmasq[2838]: using nameserver 194.109.104.104#53
>> Jul 22 20:46:15 dnsmasq[2838]: using nameserver 194.109.6.66#53
>> Jul 22 20:46:15 dnsmasq[2838]: reading /etc/resolv.conf
>> Jul 22 20:46:15 dnsmasq[2838]: read /etc/hosts - 4 addresses
>> Jul 22 20:46:15 dnsmasq[2838]: started, version 1.18 cachesize 150
>> Jul 22 20:46:14 dhclient: DHCPDISCOVER on sis1 to 255.255.255.255 port
>> 67 interval 3
>> Jul 22 20:46:11 dhclient: Sending on Socket/fallback
>> Jul 22 20:46:11 dhclient: Sending on BPF/sis1/00:00:24:c2:42:4d
>> Jul 22 20:46:11 dhclient: Listening on BPF/sis1/00:00:24:c2:42:4d
>>
>> am i wroong saying there's everything needed???
>>
>> but, when i ping from the m0n0 web-gui
>>
>> ping: sendto: No route to host
>> ping: sendto: No route to host
>> ping: sendto: No route to host
>> PING 212.239.41.2 (212.239.41.2): 56 data bytes
>>
>> --- 212.239.41.2 ping statistics ---
>> 3 packets transmitted, 0 packets received, 100% packet loss
>>
>>
>> and on the interfaces page of the web-gui
>> this is the WAN interface
>>
>> Status up
>> MAC address 00:00:24:c2:42:4d
>> IP address 213.84.18.234
>> Subnet mask 255.255.255.0
>> Media 100baseTX <full-duplex>
>> In/out packets 845/892 (102 KB/110 KB)
>>
>> it gets everything but no gateway, which i think is the reason why it
>> can't ping.
>
> It gets a gateway, its just not a *useful* gateway. :-)
>
>> is there a way to have m0n0 work on this configuration?
>> i tried several times to make PPTP but no way.
>> it refuses to work on both my speedtouch modems
>
> What does your *ISP* say the configuration should be?  Any competent 
> ISP
> should provide a standard list of all the correct non-customer-specific
> settings.
>
> 					Fred Wright
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>