Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

daloradius docker not accepting connections #497

Open
matzeeg3 opened this issue Feb 28, 2024 · 4 comments
Open

daloradius docker not accepting connections #497

matzeeg3 opened this issue Feb 28, 2024 · 4 comments

Comments

@matzeeg3
Copy link

hi everybody, i just installed daloradius like it is descripte in the docker-compose.yml. everything started up but the radios server is not accessible.
i just see this in the radisu log:
gnoring request to auth address * port 1812 bound to server default from unknown client x.x.x.x port 9409 proto udp
what am i doing wrong?

@SalehMohammadMusa
Copy link

same issue here. DId you find any solution ?

@SunYvming
Copy link

Same issue here.
It seems to be caused by the skipping of freeradius initialize.
I have 2 solutions:
One is to cancel the volume mount in docker-compose.yml

  radius:
    container_name: radius
    build:
      context: .
      dockerfile: Dockerfile-freeradius
    restart: unless-stopped
    depends_on: 
      - radius-mysql
    ports:
      - '1812:1812/udp'
      - '1813:1813/udp'
    environment:
      - MYSQL_HOST=radius-mysql
      - MYSQL_PORT=3306
      - MYSQL_DATABASE=radius
      - MYSQL_USER=radius
      - MYSQL_PASSWORD=radiusdbpw
      # Optional settings
      - DEFAULT_CLIENT_SECRET=testing123
    # volumes:
    #   - ./data/freeradius:/data
    # If you want to disable debug output, remove the command parameter
    command: -X

It will init db and freeradius each time when the container start.
Although we do not need reinit the db, but i dont get any error.

Two is to change the init-freeradius.sh

# line 66-72
INIT_LOCK=/data/.freeradius_init_done
if test -f "$INIT_LOCK"; then
	echo "Init lock file exists, skipping initial setup."
else
	init_freeradius
	date > $INIT_LOCK
fi

We just need

init_freeradius

@wallacemariadeandrade
Copy link

Nice!

Same issue here. It seems to be caused by the skipping of freeradius initialize. I have 2 solutions: One is to cancel the volume mount in docker-compose.yml

  radius:
    container_name: radius
    build:
      context: .
      dockerfile: Dockerfile-freeradius
    restart: unless-stopped
    depends_on: 
      - radius-mysql
    ports:
      - '1812:1812/udp'
      - '1813:1813/udp'
    environment:
      - MYSQL_HOST=radius-mysql
      - MYSQL_PORT=3306
      - MYSQL_DATABASE=radius
      - MYSQL_USER=radius
      - MYSQL_PASSWORD=radiusdbpw
      # Optional settings
      - DEFAULT_CLIENT_SECRET=testing123
    # volumes:
    #   - ./data/freeradius:/data
    # If you want to disable debug output, remove the command parameter
    command: -X

It will init db and freeradius each time when the container start. Although we do not need reinit the db, but i dont get any error.

Two is to change the init-freeradius.sh

# line 66-72
INIT_LOCK=/data/.freeradius_init_done
if test -f "$INIT_LOCK"; then
	echo "Init lock file exists, skipping initial setup."
else
	init_freeradius
	date > $INIT_LOCK
fi

We just need

init_freeradius

Nice, i was stuck in this problem! Thanks!

@dot-mike
Copy link
Contributor

dot-mike commented Jan 3, 2025

#557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants