Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Problems with au ADSL/network setup
- Date: Sat, 23 Nov 2013 21:47:23 +0900
- From: Jens Oliver John <lists@example.com>
- Subject: Re: [tlug] Problems with au ADSL/network setup
- References: <20131123203917.5b7f04dcef06d75ae0ba99b4@portblue.net>
- User-agent: Mutt/1.5.21 (2010-09-15)
Then can you block/firewall the DHCP UDP ports 67 and 68 in incoming and outgoing directions on the WAN port of the router, so that the modem's DHCP doesn't interfere with the router? That's how it should be anyway. If not, try disabling DHCP on the router. If the router does pick an IP address from the modem's DHCP for itself, the admin interface should be reachable under that IP. If not, just add a new route for the 192.168.11.0/24 network on the network clients so that it will be able to connect to the router's static 192.168.11.*. -Jens. On Sat, Nov 23, 2013 at 08:39:17PM +0900, Stefan A. wrote: > Thanks for the input, Darren and Jens. From what I can gather from my > notes, the Buffalo router allocates IPs within the 192.168.11.* range > (subnet: 255.255.255.0). The modem allocates addresses within > 192.168.0.* (subnet mask: 255.255.255.0). I remember clearly that when > I turned on only the router and connected via wifi, I would get an IP > from within the 192.168.11.* range and access to the router's admin > interface worked as expected. After that however, when I hooked up the > router to the modem (connecting the router's WAN port to the modem's > LAN port), wifi would at first disconnect and then reconnect after a > few seconds, at which point I got an IP from the modem's network range > 192.168.0.* and couldn't connect to the router's admin interface > anymore. > > Just as Jens said, I originally expected the router to handle wifi and > IP address allocation via DHCP and only use the modem to connect, so I > don't understand how something like this can even happen. The same > problem occurs with both the older IOData router and the newer Buffalo > router, even when no other (local or wireless) clients are present. The > modem simply "overwrites" the router's address allocation. My friend > also reports that he is increasingly often unable to connect via wifi. > The network is present, but when he tries to connect, things hang up at > the point where his computer is to receive an IP address. So there is > definitely a conflict here, but I can't make heads or tails of it. > > Generally speaking, do Japanese providers restrict (legally or > technically) the use of wifi-capable routers behind ADSL/Hikari modems? > I'm asking because I remember a recent debate in Germany where > providers forced customers to use their own modems and routers, and > people feared these sorts of restrictions would be the result (e.g. > having providers dictate which hardware you can use on the network and > make you pay extra for stuff like wifi). > > -- > Stefan A. <stefan.a@example.com> > > -- > To unsubscribe from this mailing list, > please see the instructions at http://lists.tlug.jp/list.html > > The TLUG mailing list is hosted by ASAHI Net, provider of mobile and > fixed broadband Internet services to individuals and corporations. > Visit ASAHI Net's English-language Web page: http://asahi-net.jp/en/Attachment: signature.asc
Description: Digital signature
- References:
- Re: [tlug] Problems with au ADSL/network setup
- From: Stefan A.
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Japanese and Android
- Next by Date: Re: [tlug] Japanese Input - Kubuntu 12.04 LTS
- Previous by thread: Re: [tlug] Problems with au ADSL/network setup
- Next by thread: Re: [tlug] Problems with au ADSL/network setup
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links