Vou mandar uma postagem em cima da outra, pois no google nao conseui ainda tirar essa duvida... Alguem j'a se deparou com a necessidade de configurar o /etc/resolv.conf com um tal de *verizon third level DNS?* Caso positivo como faco isso para o virtua com dns *201.17.014 (primario)* e *201.17.1.15 (secundario) e rede local em 201.xx.x.xxx?*
sample '/etc/resolv.conf'; search 192.168.1.1 nameserver 207.179.200.2 nameserver 207.179.200.25 nameserver 207.179.200.10 nameserver 4.2.2.1 #verizon third level DNS nameserver 4.2.2.2 nameserver 4.2.2.3 nameserver 4.2.2.4 2011/8/19 Alcir <[email protected]> > Sigo pesquisando esse problema e tenho essa saida para o comando > /etc/rc.d/rc.inet1.conf. Achei estranho a linha com "yes" para o dhpc. No > sistema 13.37 de voces esta assim mesmo, pois perco justamente o nameserver > no resolv.conf apos o reboot? > > *# /etc/rc.d/rc.inet1.conf > *# > # This file contains the configuration settings for network interfaces. > # If USE_DHCP[interface] is set to "yes", this overrides any other > settings. > # If you don't have an interface, leave the settings null (""). > > # You can configure network interfaces other than eth0,eth1... by setting > # IFNAME[interface] to the interface's name. If IFNAME[interface] is unset > # or empty, it is assumed you're configuring eth<interface>. > > # Several other parameters are available, the end of this file contains a > # comprehensive set of examples. > > # > ============================================================================= > # Config information for eth0: > IPADDR[0]="201.37.x.xxx" > NETMASK[0]="255.255.255.0" > USE_DHCP[0]="" > DHCP_HOSTNAME[0]="" > > # Config information for eth1: > IPADDR[1]="" > NETMASK[1]="" > USE_DHCP[1]="" > DHCP_HOSTNAME[1]="" > > # Config information for eth2: > IPADDR[2]="" > ETMASK[2]="" > USE_DHCP[2]="" > DHCP_HOSTNAME[2]="" > > # Config information for eth3: > IPADDR[3]="" > NETMASK[3]="" > USE_DHCP[3]="" > DHCP_HOSTNAME[3]="" > > # Default gateway IP address: > GATEWAY="201.37.x.xxx" > > # Change this to "yes" for debugging output to stdout. Unfortunately, > # /sbin/hotplug seems to disable stdout so you'll only see debugging output > # when rc.inet1 is called directly. > DEBUG_ETH_UP="no" > > ## Example config information for wlan0. Uncomment the lines you need and > fill > ## in your info. (You may not need all of > #DHCP_HOSTNAME[4]="icculus-wireless" > #DHCP_KEEPRESOLV[4]="yes" > #DHCP_KEEPNTP[4]="yes" > #DHCP_KEEPGW[4]="yes" > #DHCP_IPADDR[4]="" > #WLAN_ESSID[4]=BARRIER05 > WLAN_RATE[4]="54M auto" > ##WLAN_CHANNEL[4]="auto" > ##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7" > ##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set > WPAPSK=96389dc66eaf7e6efd5b5523ae43c > 7925ff4df2f8b7099495192d44a774fda16" > #WLAN_WPA[4]="wpa_supplicant" > #WLAN_WPADRIVER[4]="ndiswrapper" > > ## Some examples of additional network parameters that you can use. > ## Config information for wlan0: > #IFNAME[4]="wlan0" # Use a different interface name nstead of > # the default 'eth4' > #HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address > #MTU[4]="" # The default MTU is 1500, but you might need > # 1360 when you use NAT'ed IPSec traffic. > #DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf overwritten > #DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten > #DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change > # your default gateway > #DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP > # server > #WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameterthese for > your wireless network) > #IFNAME[4]="wlan0" > #IPADDR[4]="" > #NETMASK[4]="" > *#USE_DHCP[4]="yes" > *#DHCP_HOSTNAME[4]="icculus-wireless" > #DHCP_KEEPRESOLV[4]="yes" > #DHCP_KEEPNTP[4]="yes"#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP > server to change > # your default gateway > #DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP > # server > #WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter > # defined in rc.wireless.conf, by prepending > # 'WLAN_' to the parameter's name. Useful for > # those with multiple wireless interfaces. > #WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set > WPAPSK=thekey" > # Some drivers require a private ioctl to be > # set through the iwpriv command. If more than > # one is required, you can place them in the > # IWPRIV parameter (separated with the pipe (|) > # character, see the example). > > > > > > > 2011/8/3 LopanRS <[email protected]> > >> Tava olhando o vector 7 RC que tem como base o slack 13.37 e tambem >> tem um arquivo de nome /etc/modpbrobe.d/network.conf que contem: >> alias eth0 via-rhine >> >> >> On 3 ago, 00:06, Alcir <[email protected]> wrote: >> > Abro essa duvida apos diversos testes e em resposta ao amigo Lopan >> > esclareco: >> > >> > *Olá Alcir. >> > Ip voce pode setar editando o arquivo /etc/rc.d/rc.inet1 >> > Como por exemplo pra deixar fixo o IP na interface eth0: >> > >> > DEVICE='eth0'* * >> > DHCP='no' >> > IPADDR='192.168.2.1' >> > NETMASK='255.255.255.0' >> > GATEWAY=''* >> > *PROBE='no' >> > * >> > Tenho um sistema 13.37 instalado numa placa mae Asus A8V-MX. Transportei >> o >> > hd para outra placa de mesmo modelo e editei o * >> > >> > # /etc/udev/rules.d/70-persistent-net.rules* ( name para eth0 ) >> > >> > apos configurar o ip via com as alternativas * >> > >> > # netconfig >> > >> > * ou manualmente com * >> > >> > #ifconfig eth0 201.37.x.xxx netmask 255.255.255.0 up* >> > >> > tenho conex'ao com a internet.* Porem apos o reboot eu perco o ip*. >> > >> > O modulo esta carregado e certifico com: >> > >> > *#depmod -a* ( nehuma saida ) >> > >> > *#lspci* ( mostra-me via_rhine e mii como ethernet ) >> > >> > *#lsmod *( parte da saida ) >> > Module Size Used by >> > vboxnetadp 6727 0 >> > ... >> > via_rhine 17845 0 >> > mii 3334 1 via_rhine >> > ipv6 236629 14 >> > * >> > # dmesg *( onde encontrei coisas que desconheco ) >> > >> > [ 0.235872] pci 0000:00:13.0: PCI bridge to [bus 04-04] >> > [ 0.236004] pci 0000:00:13.0: bridge window [io 0xf000-0x0000] >> (disabled) >> > [ 0.236009] pci 0000:00:13.0: bridge window [mem 0xfbf00000-0xfbffffff] >> > [ 0.236015] pci 0000:00:13.0: bridge window [mem 0xfff00000-0x000fffff >> pref] >> > (disabled) >> > [ 0.236080] pci 0000:00:13.1: PCI bridge to [bus 05-05] (subtractive >> decode) >> > [ 0.236179] pci 0000:00:13.1: bridge window [io 0xf000-0x0000] >> (disabled) >> > [ 0.236184] pci 0000:00:13.1: bridge window [mem 0xfff00000-0x000fffff] >> > (disabled) >> > [ 0.236190] pci 0000:00:13.1: bridge window [mem 0xfff00000-0x000fffff >> pref] >> > (disabled) >> > [ 0.236194] pci 0000:00:13.1: bridge window [io 0x0000-0xffff] >> (subtractive >> > decode) >> > [ 0.236197] pci 0000:00:13.1: bridge window [mem 0x000a0000-0x000bffff] >> > (subtractive decode) >> > [ 0.236201] pci 0000:00:13.1: bridge window [mem 0x20000000-0xffffffff] >> > (subtractive decode) >> > [ 0.236224] pci_bus 0000:00: on NUMA node 0 >> > [ 0.236228] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] >> > [ 0.236382] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT] >> > [ 0.236412] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PA._PRT] >> > [ 0.236498] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] >> > [ 0.236529] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NBPG._PRT] >> > [ 0.236566] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NBP0._PRT] >> > [ 0.249347] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 >> 15) >> > [ 0.250064] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 >> 15) >> > [ 0.250769] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 7 10 11 12 14 >> 15) >> > [ 0.251468] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 >> 15) >> > [ 0.252187] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 >> 15) >> > *0, disabled. >> > [ 0.253043] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 >> 15) >> > *0, disabled. >> > [ 0.253884] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 >> 15) >> > *0, disabled. >> > [ 0.254707] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 11 12 14 >> 15) >> > [ 0.255411] HEST: Table is not found! >> > >> > ... >> > [ 0.310611] RPC: Registered tcp NFSv4.1 backchannel transport module. >> > [ 0.310711] pci 0000:00:00.0: MSI quirk detected; MSI disabled >> > [ 0.310827] pci 0000:00:01.0: disabling DAC on VIA PCI bridge >> > [ 0.310925] pci 0000:00:02.0: MSI quirk detected; subordinate MSI >> disabled >> > >> > ... >> > >> > [ 4.192627] via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald >> Becker >> > [ 4.192784] via-rhine 0000:00:12.0: PCI INT A -> GSI 23 (level, low) -> >> IRQ >> > 23 >> > [ 4.202762] rtc_cmos 00:02: RTC can wake from S4 >> > [ 4.203527] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 >> > [ 4.203661] rtc0: alarms up to one year, y3k, 114 bytes nvram >> > [ 4.204425] eth0: VIA Rhine II at 0xf8fff800, 00:11:d8:01:23:45, IRQ 23. >> > [ 4.205234] eth0: MII PHY found at address 1, status 0x786d advertising >> 01e1 >> > >> > ... >> > >> > [ 11.692128] EXT4-fs (sda6): mounted filesystem with ordered data mode. >> > Opts: (null) >> > [ 13.986540] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 >> > [ 15.200684] NET: Registered protocol family 10 >> > [ 15.200937] lo: Disabled Privacy Extensions >> > [ 25.938014] eth0: no IPv6 routers present >> > [ 46.132279] vboxdrv: Found 1 processor cores. >> > [ 46.135986] vboxdrv: TSC mode is 'synchronous', kernel timer mode is >> > 'normal'. >> > [ 46.135991] vboxdrv: Successfully loaded version 4.0.8_OSE (interface >> > 0x00180000). >> > [ 55.690230] start_kdeinit (2089): /proc/2089/oom_adj is deprecated, >> please >> > use /proc/2089/oom_score_adj instead >> > >> > *Curiosamente, o comando */etc/rc.d/rc.inet1 eth0_start em rc.d/rc.local >> > n'ao funciona logo apos o reboot. Mas no console faz o ping para o >> servidor >> > funcionar.* Alguma ideia? >> > * >> >> -- >> GUS-BR - Grupo de Usuários de Slackware Brasil >> http://www.slackwarebrasil.org/ >> http://groups.google.com/group/slack-users-br >> >> Antes de perguntar: >> http://www.istf.com.br/perguntas/ >> >> Para sair da lista envie um e-mail para: >> [email protected] >> > > -- GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br Antes de perguntar: http://www.istf.com.br/perguntas/ Para sair da lista envie um e-mail para: [email protected]
