Sponsored Content
Operating Systems Solaris Need help configuring Cable Modem on Solaris x86 Post 302210538 by incredible on Tuesday 1st of July 2008 07:16:52 AM
Old 07-01-2008
your ifconfig -a only shows the loopback interface. NO ip is configured or interface plumbed..
If you want to plumb and IP, do the following: (example)
ifconfig hme0 plumb
ifconfig hme0 172.18.6.23 netmask 255.255.255.0 broadcast + up

ifconfig -a (to verify)
 

10 More Discussions You Might Find Interesting

1. IP Networking

unix and the cable modem

If the cable modem that the cable company is using doesn't support unix is there a way around that . Are there drivers I can get online or is there a way to configure redhat lenix (that's what I will be using) to work with the cable modem. Or is there a way to buy a third party cable modem that... (3 Replies)
Discussion started by: gparsons70
3 Replies

2. UNIX for Dummies Questions & Answers

Linux and my cable modem

I recently installed Caldera 2.4 (successfully:p ), but I cannot seem to get my cable modem up and running! My ISP is AT&T and I'm using @home. I've tried using DHCP and that didn't work either. I briefly read the cable modem HOWTO, but the lsmod didn't list my network card (3COM). What do I do now? (4 Replies)
Discussion started by: zorro
4 Replies

3. UNIX for Dummies Questions & Answers

can't get my cable modem up

Caldera eDesktop 2.4 - Cable Modem my NIC card has been detected, but funny scenario: #dmesg eth0: RealTek rtl8139 Fast Ethernet at 0x2400, IRQ 0, 00:50:ba:43:a0:ef /*I noticed that it detected the correct module (rtl8139) but I'm using D-Link and not RealTek, which uses the same module.... (1 Reply)
Discussion started by: zorro
1 Replies

4. UNIX for Dummies Questions & Answers

Is anyone using unix with cable modem

Is anyone using a cable modem with unix and if so does your cable co. support unix or did you get that going on your own and how. Thank you for all your help. (5 Replies)
Discussion started by: gparsons70
5 Replies

5. IP Networking

DHCP Linux and cable modem

I can do all this in windows, but Im trying to run the SuSe 8.0 professional as a gateway. I have the local (private) LAN setup with no problems, but Im having troubles getting it to use DHCP to go out on the external card to the service provider, which only uses Dynamic IP's. WHere, what and how... (3 Replies)
Discussion started by: ftn96
3 Replies

6. UNIX for Dummies Questions & Answers

cable modem to sparc

hi , i have sparc machine , i want to connect my le0 (ethernet interface) directly to cable modem , i have created a file resolv.conf,hosts, dhcp.le0,defaultrouter,nisswitch,hostname.le0. i dont know my cable companies <domain name> and <name server assigned to me> , also they even dont know how... (5 Replies)
Discussion started by: raju
5 Replies

7. BSD

cable modem problem

hi I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system. When I type, I get # ifconfig -a lo0 : .... ... ... rl0 : .... ... ... vr0 : ... ... ... I have two network cards (the machine will be a router). I created... (1 Reply)
Discussion started by: fnoyan
1 Replies

8. Solaris

Is the cable you are using a null modem cable or a modem cable

Hi all, Is there any difference between a null modem cable or a modem cable ? i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup. please correct if i am wrong, thks (2 Replies)
Discussion started by: waterbear
2 Replies

9. Solaris

modem setup solaris 10 x86

I,am trying to configure an external multitech 5656zdx modem for dial in mode on a serial port using a dell 1800 server with solaris 10 for intel as the OS. It answers only once, further attemps fail, I have to reboot system before it will work again. I also used an older model 3334zdx which... (1 Reply)
Discussion started by: albm
1 Replies

10. OS X (Apple)

Cannot access UNIX.com with new cable modem

Hi. I have a very strange problem, so strange I don't even know which sub-forum to post it to. Last week, my cable modem broke, so I took it back and got a new one. The new one doesn't work with my old router so, for now, I have to connect the modem directly to my Mac with an ethernet... (14 Replies)
Discussion started by: Scott
14 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 04:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy