Amiga Future






Last Magazine

The Amiga Future 161 was released on the March 5th.

The Amiga Future 161 was released on the March 5th.
The Amiga Future 161 was released on the March 5th.

The Amiga Future 161 was released on the March 5th.
More informations





Advanced search

Unanswered topics
Active topics

Social Media

Twitter Amigafuture Facebook Amigafuture RSS-Feed [german] Amigafuture RSS-Feed [english] Instagram YouTube Patreon






no internet with FritzBox 7530/M-Net provider IP4

Support Roadshow

Moderators: AndreasM, olsen

Post Reply
Grade reingestolpert
Grade reingestolpert
Posts: 3
Joined: 14.09.2011 - 21:22
Location: Todenbüttel

no internet with FritzBox 7530/M-Net provider IP4

Post by mbergmann-sh »

I've connected my A500+/piStorm/Emu68 (latest build) to my FritzBox 7530 using a plipbox. PlipBox is using an external power supply. Since Amiga can't handle IPv6, I've ordered IP4 support from my provider (M-NET), that usually just gives you IP4 only over DS-Lite tunneling. IP4 is activated in my FritzBox (pic 1).
My Plipbox is configured for static IP, since DHCP can't find anything working on the FritzBox:

config files:

# local address of my router:


On my FritzBox, I've added a new statical device, configured to open all ports by itsself (pic 2)
The Amiga is sometimes seen by FritzBox, but has no internet connection - and sometimes it is NOT seen.

I can't neither ping from the Amiga to my other local machines, nor from any local machine to the Amiga.
Roadshow doesn't find any nameservers when pinging to the internet or running a browser.

Please help!

CygnusEd Developer
Posts: 166
Joined: 06.06.2006 - 16:27

Re: no internet with FritzBox 7530/M-Net provider IP4

Post by olsen »

Hallo Michael, ich hatte Dir am 9. Januar Folgendes dazu auf Deine Anfrage per E-Mail geschrieben (vielleicht ist die Antwort bei Dir noch in der Warteschlange):

Hallo Michael, ich vermute, dass in der Fritzbox der DHCP-Server nicht aktiviert ist. Die Einstellungsseite, deren Bild Du im Forum eingetragen hast, legt meiner Einschätzung nach nahe, dass das Gerät in erster Linie für IPv6-Nutzung eingerichtet ist.

Etwas gebuddelt: ... en-lassen/

Falls es sich damit lösen lässt, wäre das wohl die beste Lösung. Anderenfalls müssten wir "ein wenig" mit den bei Roadshow verfügbaren Mitteln nachbohren, z.B. "debug=yes" in die Konfigurationsdatei für die Plipbox eintragen.

Das würde dann z.B. so aussehen:
# $VER: Plipbox 1.1 (13.12.2022)
# Configuration for Christian Vogelgsang's "plipbox" device,
# using the "plipbox.device" driver.
# See and
# for more information.

# The device name is mandatory

# If you are using multiple plipbox devices in your local
# network, then every single one needs to report a unique
# MAC address. The following address is a sample to get
# you started. If you need a new address to be used in your
# local network, change only the last three numbers, e.g.
# from "a0:00:01" for the first plipbox, then "a0:00:02",
# "a0:00:03", etc.

# If not provided, unit number 0 will be used. You may
# have to change this if there are multiple cards of the
# same type installed in your machine, or if your network
# hardware supports several independent connections

# You must either pick a fixed (static) IPv4 address and
# a corresponding subnet mask, or request DHCP (dynamic)
# network address configuration.
# You can combine address/netmask/dhcp, which has the effect
# of asking the DHCP server to assign the requested IPv4
# address and subnet mask to this interface, if possible.

# If no DHCP server is present in your network, you can
# use automatic interface IPv4 address assignment through
# the ZeroConf protocol. Note that this will not set up
# default route and DNS servers for you, only the interface
# address is configured.

# This variant of automatic IPv4 address assignment should
# be used in a wireless network instead of 'configure=auto'

# You can enable diagnostic messages which can be helpful in
# tracking down configuration errors.

# You can choose how much memory will be used when handling
# incoming and outgoing network traffic for this device.
# The default is to reserve 32 buffers of 1500 byte each, both
# inbound and outbound traffic. Larger values may provide
# better performance.

# For diagnostic and monitoring purposes it can be helpful to
# capture network traffic that flows through this interface.
# To enable this option, select one of filter=local,
# filter=ipandarp or filter=everything

# This option disables a workaround required for the Ariadne
# network hardware, which, if enabled, would otherwise cause
# the interface setup procedure to take longer than really
# necessary.
Beim Anwerfen der Adresszuweisung über DHCP wird bei "debug=yes" das Protokollfenster geöffnet und dort dann ausgegeben, was Roadshow beim Rufen in der Wüste von sich gibt, bis hoffentlich ein DHCP-Server zuhört, usw.
Post Reply