Re: D-Link DSL-300T
From: Uriah Heep (adrian)
Date: 02/25/05
- Next message: Anton Chernoff: "Re: FIN_WAIT_2 and apache"
- Previous message: Kris Kennaway: "Re: FreeBSD 5.3 crash (core with debug symbols available)"
- In reply to: Keve Nagy: "Re: D-Link DSL-300T"
- Next in thread: Martin: "Re: D-Link DSL-300T"
- Reply: Martin: "Re: D-Link DSL-300T"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 25 Feb 2005 11:21:04 -0600
On 2005-02-17, Keve Nagy <no_spam@poliod.hu> wrote:
> Martin wrote:
>> Hi Keve,
>> I'm running a DSL-300T as a transparent bridge for my
>> ADSL connection. I've got FreeBSD 4.10 running as a gateway at home.
>> The set up was pretty much as in the FreeBSD Handbook for PPPoe.
>>
>> Regards,
>> Martin.
>
> Hi Martin,
> As far as I know, when you use the DSL-300T in bridge mode then the IP
> address the ISP assigns to you gets passed on to your FreeBSD machine
> connected to the device and does not get used by the modem. So in this
> configuration, how do you access the modem for configuration and
> maintenance?
> 1., Does it still have a private IP and you can connect to the device's
> web based configuration subsystem using that address?
> Or is it not possible to do configurations any more unless you reset the
> modem to the factory defaults somehow?
>
> 2., What do you get when you try to connect via http from outside of
> your network to port 80 of the IP address the ISP assigned to your
> connection? Do you get the configuration interface of the DSL-300T or
> the webserver listening on port 80 of your FreeBSD machine?
>
> Thanks!
>
> Keve
Strangely enough, I've been trying to do the same thing but couldn't get it
to work in bridge mode. While playing with it under Windows, we discovered
that if we set the 300T to normal PPPoA mode, with DHCP server on, then when
we connected a Windows machine to it then Windows got the external IP, and
a traceroute showed outgoing traffic was leaving via the internal IP of the
300T.
Trying this trick with BSD only partly worked - the interface on the BSD box
got the external IP along with the ISPs DNS server, plus a default route which
pointed to itself (external IP). Traffic would not go out or in.
In this instance, the client had paid for a fixed IP address, so I set things
up as follows:
Two NICs on the BSD box (4.11) one with a LAN IP, this IP became the gateway
for the LAN.
Second NIC had the static IP from the ISP, along with an alias on the same
network as the 300T. The 300T IP was set as the default gateway. Natd was set
up to use this interface for outgoing, as was the firewall.
Start it all up, and it works. LAN clients can browse the Internet, I can SSH
in to do admin stuff.
The next trick is to get this to work dynamically - something to override the
gateway set by the ISP and instead use the 300T address. It would be nice to
get it working properly as a bridge, but nothing I tried would work.
-Adrian
- Next message: Anton Chernoff: "Re: FIN_WAIT_2 and apache"
- Previous message: Kris Kennaway: "Re: FreeBSD 5.3 crash (core with debug symbols available)"
- In reply to: Keve Nagy: "Re: D-Link DSL-300T"
- Next in thread: Martin: "Re: D-Link DSL-300T"
- Reply: Martin: "Re: D-Link DSL-300T"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
