Date: Thu, 08 Jun 2000 00:11:10 -0400 From: lenny <huppe@mailtag.com> To: questions@freebsd.org Subject: tun0 not showing up on 4.0-Release Message-ID: <393F1CDD.3F36AF1A@mailtag.com>
next in thread | raw e-mail | index | archive | help
I'm trying to use FreeBSD 4.0 Release to build an NAT proxy for use with my cable modem, and I can't get the tunnel driver to work. I did this on version 3.3 and it was a snap. I have the following in my kernel config file: options IPFIREWALL options IPDIVERT options IPFIREWALL_DEFAULT_TO_ACCEPT pseudo-device tun device miibus device xl0 device xl1 I have the following in my /etc/rc.conf file: ifconfig_xl0="DHCP" ifconfig_xl1="inet 10.2.1.2 netmask 255.255.255.0" firewall_enable="YES" firewall_type="OPEN" natd_enable="YES" natd_interface="tun0" natd_flags="-dynamic" gateway_enable="YES" At bootup, I get the message "unknown interface tun0" when rc.conf is processed, and again when rc.firewall is processed. I've done a "MAKEDEV tun0" repeatedly, but I keep getting "interface tun0 does not exist" when I try running "ifconfig tun0". Since I'm not using IPv6 or dial-up, I tried remming out the following in my kernel config, but with no improvement: options INET6 pseudo-device sl pseudo-device ppp pseudo-device gif 4 pseudo-device faith 1 I did notice that a lot of documentation shows the divert service as being located on port 6668, but my /etc/services file has it at port 8668. Is this a change or a bug? Can anyone see what I missed? Is there a change to the way we use the tunnel driver in 4.0 that I need to know about? Any help will be appreciated. Please respond to huppe@mailtag.com as well as the mailing list. thanks a bunch, Len Huppe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?393F1CDD.3F36AF1A>